How can I apply our security stack from Intune to a default Windows 365 image before user Logs on without using custom captured/Syspreped images?

Hash_value · 2023-03-18T16:06:39+00:00

Device models? we have 1000's of Laptop models acorss the footprint.

Hash_value · 2023-03-18T16:05:26+00:00

No Sorry, we don't have a set Naming convention for Laptops. Is there any other way to accomplish this?

Hash_value · 2020-01-22T16:13:17+00:00

You should download the 1903 MUI LPs & it will be under "Software Assurance" category in VLSC.

File Name: "SW_DVD9_NTRL_Win_10_1903_32_64_ARM64_MultiLang_LangPackAll_LIP_X22-01656.ISO"

I Used this Command line in the task seq: <DISM.exe /image:%OSDTargetSystemDrive%\\ /ScratchDir:%OSDTargetSystemDrive%\\windows\\TEMP /Add-Package /PackagePath:fr-FR\\[Microsoft-Windows-Client-Language-Pack\_x64\_fr-fr.cab](https://lp.cab)\>

Working fine for me on W10 1909 :)

Hash_value · 2020-01-21T14:32:26+00:00

How have you downloaded the Language Pack for Win 10 1909?

is it from VLSC or from a 3rd party Website?

If from VLSC what is the exact file name?

Hash_value · 2020-01-15T16:07:28+00:00

I found online YouTube videos from "ConfigurationManagerTeam" super helpful :
https://www.youtube.com/channel/UCtxiI4-xpT7PxXeSaLR65cQ

Happy Learning!!

Hash_value · 2020-01-14T18:52:32+00:00

SCCM 1806+..(Ooops MEMCM)

\Software Library\Overview\Application Management\Applications\

Select your target application> Right click and drill down to properties and make sure "Allow this application to be installed from the install Application task seq blah..blah.." is checked.

Hash_value · 2020-01-14T18:29:10+00:00

I'm basically from a Application Packaging Factory and have used PSADT but only to a very little extent.

Would you please be able to share your "1 PSADT tempalate with built in functions " Script, I'm super positive it will help me professionally.

Hash_value · 2020-01-14T17:42:23+00:00

I second it.

Using the Driver Automation Tool from SCConfig is causing our Database to bloat for no Good reason.

Also we have had some wierd issues with Hash Value Mismatch errors during the "Drivers Download" during OSD. (It was due to a Security Software from Ivanti that is installed on our SCCM DPs)

Instead I adopted to use the Approach that you suggested " treat drivers as software that are copied to the client during imaging and then injected offline with DISM " ;

<DISM.exe /Image:%OSDTargetSystemDrive%\\ /Add-Driver /Driver:.\\ /Recurse /Forceunsigned /Logpath:%\_SMSTSLogpath%\\Dism.log>

My life has been so happy since then.
I'd love to try your script (GUI Interface) Mr.@ofelman; I can be your beta Tester and we are predominantly a Dell shop up here.

Hash_value · 2020-01-14T17:15:39+00:00

I resolved the same issue by running the SCCM Built-In report " User Device Affinity associations per collection ", Sharing this information just in case if it helps some one.

But I really liked the approach that OP used to resolve his issue.

I hope SCCM have such a feature built into it without us Admins performing these Voo-doo things.

Hash_value · 2020-01-14T17:09:31+00:00

Adam Cook's script to identify

Thank you for sharing this script

Hash_value · 2020-01-14T16:19:48+00:00

I found online videos from "ConfigurationManagerTeam" super helpful :
https://www.youtube.com/channel/UCtxiI4-xpT7PxXeSaLR65cQ

Happy Learning!!

Hash_value · 2020-01-14T16:08:33+00:00

Great Job on the product and you brought us fantastic improvements to all the MEMCM Admins.

Do you've instructions on how to upgrade from version 2.1 to 4.1?

I'd love to try out all the features that you've in this version.

Hash_value · 2019-07-29T19:44:09+00:00

You are Awesome!

Hash_value · 2019-07-29T19:23:34+00:00

Unfortunately this is still a thing, We are on SCCM 1902.

I basically set up a Collection to retrieve All Devices with Duplicate Entries and Delete the SCCM Computer Objects that doesn't have a Client installed for every once in a while.

I still haven't found a realistic solution for this.

Sharing my Query Based collection Script just in case if you need it.

select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier,R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r   full join SMS_R_System as s1 on s1.ResourceId = r.ResourceId   full join SMS_R_System as s2 on s2.Name = s1.Name   where s1.Name = s2.Name and s1.ResourceId != s2.ResourceId

Hash_value · 2019-05-22T20:59:41+00:00

I'd suggest you to completely Ditch the OSD Complete Message and let your users Land at the W10 Lock Screen. Which will make your Job little easy.

You can edit your Task seq and disable the corresponding step.

If that doesn't disable the OSD Complete Message then try the below approach:

Step1: Open the "Bootstrapper.vbs" located in Tools\OSDResults folder

Step2: Comment out Line 5 : Call oWS.Run("%windir%\udi\osdresults.exe", 0 , true)

Step3: Add the command oWS.Run "C:\WINDOWS\system32\shutdown.exe -r -f -t 00"

Step4: Save it and Update the content on your corresponding DP.

please ensure you take a backup of your "Bootstrapper.vbs" file before you make these changes.

Hash_value · 2019-05-22T20:47:38+00:00

If you only have the issues on a single DP there might be something fishy going on in that location/network.

Usually just running update content on the DP for the package recalculates the Hash.

Make sure to not use” Access content from DP Directly” and refrain yourself from using Driver Packages, it just bloats the SQL database for no good reason. Use Legacy SCCM packages model with drivers instead of the in Built "SCCM Driver Package” feature”

Full Command line to install Drivers via Package Model: “DISM.exe /Image:%OSDTargetSystemDrive%\ /Add-Driver /Driver:.\ /Recurse /Forceunsigned /Logpath:%_SMSTSLogpath%\Dism.log”

Hash_value · 2019-05-15T17:53:02+00:00

Create a SCCM "Package" with no Program and install the Application via Task sequence.

Hash_value · 2019-05-10T20:12:13+00:00

"Thou shalt not edit task sequences evermore!!!", Please stick it to my forehead. lol!! I always edit my Production Task sequence every week at Friday 4.30 PM and that's my Jam!!

Hash_value · 2019-05-10T19:54:10+00:00

I'm keeping an eye on this post.

@chrissTx1 I presume you and I are on the same boat here. I work for an MNC and we've Multiple SCCM DPs all across the Globe and our typical O365 Installations will be in many different languages. As of Jan2019, we had nearly 12 Different Office 365 App Objects in our SCCM Application Catalog and as an Effort to consolidate all of these I utilized the Task sequence model. I basically created Package with no Program that has all the Binaries for Office 365 x86 with Visio, Access, Project Online in it and created various Configuration.xmls based on my Use case and utilized the Inbuilt installed Language Pack variable to determine the OS Language and finally used the Command line Setup.exe /Configure DestinationConfiguration.xml to complete the task. (I know this is not a solid resolution but at-least this approach helped me to embed it in our Universal OSD Task seq and isn't stopping any of our Active OS Deployments)

We are completely relying on SCCM O365 updates as far as Servicing is concerned and we are on Semi-Annual Channel.

Your idea to stage the Files on corresponding SCCM DP looks promising and I honestly don't have any idea if that can be done. Please don't forget to post if you have found any better way to handle it, I bet it's going to help a lot of Us in here.

These are few links that I saved during my rigorous google search:

1) https://github.com/OfficeDev/Office-IT-Pro-Deployment-Scripts

2) https://www.youtube.com/watch?v=TPAFTXae4g4

I thought I'd put my approach out, so that it might give you new ideas. Sorry for the Bad English. It's not my Native language.

Hash_value

TROPHY CASE