I’ve performed a number of Windows 10 Deployment projects, and have compiled this handy list of must-have customizations that I deploy at build time using SCCM, or that I bake into the image when capturing it.
Hope it helps, and I’ll keep updating it as I find more good things to tweak.
With the Advent of client activity indicators in SCCM 1606:
We can now see which machines are online at a given time. I love these green checkboxes.
I thought it would be cool to try to make a collection of only currently online machines. So, into the query editor we go! We’ll add a new query rule, and then use the wizard to add a new value. This is all that you need to grab only the currently online systems.
This collection works VERY well for Incremental Updates. However, Scheduled Updates don’t make much sense
This was a bit tricky! We completed an SCCM upgrade for one customer from SCCM 1511 to 1602, and made use of the nice pre-production client validation feature.
This allows you to specify a collection of test systems to receive the new SCCM client, for you to validate in your environment.
After a few days of validation, we were ready to pull the trigger and upgrade everyone. This is done under Administration \ Cloud Services \ Updates and Servicing \ Client Update Options. However, when we tried to do this, it was grayed out!
Before trying to upgrade the client, I thought we should un-check the pre-production Collection box in Hierarchy Settings. This is done in Administration \ Sites\ Hierarchy Settings.
Don’t do this! If you uncheck this box, the SCCM ui will detect it, and gray out the SCCM won’t display the UX we need to promote the SCCM client to production.
Make sure that you check the Pre-production client box. If this isn’t checked, SCCM doesn’t know to show you the UI for upgrading the client across production!
Once this is done, you can go to Updates and Servicing, and click Client Update Options.
Complete this UI and SCCM will automatically uncheck the pre-production client for you as well. Thanks SCCM!
Recently for a customer, we ran into an issue in which the SCCM 1511 upgrade was hanging at the following screen.
If we open the SCCM install log file on the primary site, found at C:\ConfigMgrSetup.log, we will see the following message:
This step should only take a few minutes to complete, if you’ve waited a while, like 20 minutes for us–then go ahead and help SCCM out.
It’s trying to kill the SMS Component Manager service, and the SMS Exec service. If you’ve got a complex environment, it can take a long time to complete this step. Go ahead and stop the services manually using the task manager.
If this doesn’t work (it didn’t work for me, the services hung at ‘stopping’), you can use powershell to kill the service instead.
From the Task manager, look at the process ID for your SMS component manager service, and then run