Question: Now that you’ve updated the server, how do you get this update to deploy to upgrade your SCEP clients to the latest version?
The purpose of this blog post is to hopefully clear up some of the common misconceptions of this feature, and also show you how you can use it to keep your SCEP client version updated – not the definitions, but the actual version of the client itself.
You may already be familiar with the Automatic Client Upgrade option.
One of the most common misconceptions is that this checkbox will “Upgrade” your clients with the latest Cumulative “Update”.
This is designed to help stagger out client upgrades across the desired number of days and the specific date can be determined the specific client’s CCMSETUP.log: So now that the scheduled task exists on your clients, what happens when task scheduler kicks it off following the SCEP update being applied to the site server(s)?
In a client’s CCMSETUP.log, you’ll see the following: Ccmsetup command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice "/Auto Upgrade" "/Upgrade Package Version:4" "/Upgrade Win Task" "/usepkicert" "CCMHTTPPORT=80" "CCMHTTPSPORT=443" "CCMFIRSTCERT=1" SMSSITECODE="PRI" "/mp: So, has been spun up by the scheduled task, and has created a temporary CCMSETUP service with the pertinent switches to check for upgrades.