View RSS Feed


Upgrading the SCCM 2012 client to SP1

Rate this Entry
by , 23rd December 2012 at 07:00 PM (49204 Views)
For those who have just upgraded to the final release of SP1 you will have found the client needs an upgrade. You can do this my one if these methods:

1. Auto upgrade SCCM 2012 Clients
2. Use the client upgrade package

Step 1 would be easier, but for devices that go offline for long periods will not upgrade as well. If you use the deployment package and let the software install outside of maintenance windows it will get to all your machines better. Also step 1 will not give to the reporting step 2 will allow you.

This query will allow you to create a collection for devices that do not have the new updated client. You can then deploy the upgrade package to this collection.

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion < "5.00.7804.1000"
You may find that deploying the package returns as failed and reporting "unexpected restart" but the application has installed just fine. This is because the package the stops the ccmexec service which kills the execution manager making it think it got rebooted or interrupted.

Updated 23rd December 2012 at 09:11 PM by FN-GM



  1. RabbieBurns's Avatar
    Is there a SP1 standalone installer for this or do we need to download the full 2012+SP1 ISO?

    Im trying to upgrade SCVMM for example using the full ISO and its saying i need to do an uninstall then reinstall the new version.

    Is it the same for SCCM?
  2. sonofsanta's Avatar
    What file should I be pushing out for the manual upgrade? (I'd like to keep an eye on it with the reporting)

    I'm guessing [SCCMinstallDir]\Client\x64\client.msi - or should I be doing ccmsetup.exe from the level above that, and if so, any flags I should know of?

    EDIT: scratch that, finally found the relevant TechNet page - you can never get the answer to these things until you've already opened your mouth and looked stupid, can you...
    Updated 30th September 2013 at 04:44 PM by sonofsanta
  3. FN-GM's Avatar
    @sonofsanta i used the package that is already in SCCM to upgrade the client. I didn't use an MSI or anything.
  4. sonofsanta's Avatar
    SP1 itself didn't seem to create an upgrade client - the cumulative update patches did, but not SP1 itself - so I've just set the heirarchy to auto-update and created some Device Collections based on your query above to monitor it.

    I did manage to create a package for an SP1 upgrade, using the package definition and the CCMSETUP.exe file from [programDir]\ClientUpgrade, but it didn't install automatically, only if I manually went to a machine and clicked retry.

    System Center, always fun and games, huh? Been on a wild goose chase this already morning as somehow, SCCMAdmin had been removed from the SMS Admin group, so I couldn't open the console anymore - cue lots of rooting around in WMI thinking that was the cause. Oh what fun.


Total Trackbacks 0
Trackback URL: