locked
Upgraded client not being installed after CU4 upgrade RRS feed

  • Question

  • I upgraded our SCCM 2012 R2 environment to CU4 yesterday.

    If I use the auto-created packages to upgrade existing clients, it works just fine.

    However - when I do a client push to a new machine, it installs the old version of the client.

    I see this at the start of the ccmsetup log:   'CcmSetup version: 5.0.7958.1501' - which is encouraging, but then a few lines later, I get this:  'Retrieved site version '5.00.7958.1000' from AD for site 'PS1'' - and it then proceeds to install the lower version of the client.

    If I look at the record for the MP in the System area of AD, sure enough, it's still listed as 5.00.7958.1000 in the object attributes.

    <ClientOperationalSettings><Version>5.00.7958.1000</Version>

    How do i get AD to recognise that I've upgraded so that the newer version of the client is used during client push?

    Friday, April 24, 2015 8:21 AM

Answers

  • The default install will always be the latest full version. After that the client still has to be upgraded to the latest CU.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Friday, April 24, 2015 9:37 AM
  • If you are referring to the ccmsetup version, that's not the client version, that's simply the ccmsetup bootstrap version and is not specifically indicative of the actual client version being deployed.

    '5.00.7958.1000' is correct for the MP as that corresponds to 2012 R2 and is the client version pushed by the site. Changing this in no way would affect the client agent version installed by ccmsetup. ccmsetup does not try to install the CU, as mentioned, that's simply the version of ccmsetup, not the client agent.

    This is semantics for sure, but CUs aren't upgrades, they are updates.

    If you want to avoid all of this, use a startup script to deploy your client agent instead so that you can use the PATCH property and include msp for the CU during client install.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by Hackmuss Friday, April 24, 2015 2:24 PM
    Friday, April 24, 2015 2:22 PM

All replies

  • The default install will always be the latest full version. After that the client still has to be upgraded to the latest CU.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Friday, April 24, 2015 9:37 AM
  • If that's true it seems a little crazy....

    Friday, April 24, 2015 9:48 AM
  • It is completely true. I wouldn't characterize it as crazy though -- you've got an enterprise class software distribution system at your disposal, simply deploy the packages the CU4 installer created for you or use SCUP.

    This is something that many have complained about though and is on the radar of the product team. For now though, it's really not a huge deal, just an annoyance.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, April 24, 2015 1:37 PM
  • Thank you both.

    It does seem a little crazy to upgrade your environment and then not be able to push out the latest version of the client - it's just doubling up on work. Every new client now has to be upgraded straight away.

    What about the MP record in AD though? Should that have changed to the new version? I don't get why the ccmsetup appears to TRY and install the newer client, only to be re-buffed by what it finds in AD...

    It looks as though if the AD record was changed, that the newer version of the client would then be pushed?

    Friday, April 24, 2015 1:42 PM
  • If you are referring to the ccmsetup version, that's not the client version, that's simply the ccmsetup bootstrap version and is not specifically indicative of the actual client version being deployed.

    '5.00.7958.1000' is correct for the MP as that corresponds to 2012 R2 and is the client version pushed by the site. Changing this in no way would affect the client agent version installed by ccmsetup. ccmsetup does not try to install the CU, as mentioned, that's simply the version of ccmsetup, not the client agent.

    This is semantics for sure, but CUs aren't upgrades, they are updates.

    If you want to avoid all of this, use a startup script to deploy your client agent instead so that you can use the PATCH property and include msp for the CU during client install.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by Hackmuss Friday, April 24, 2015 2:24 PM
    Friday, April 24, 2015 2:22 PM
  • OK, got it.

    Thanks again both of you for your help.

    Friday, April 24, 2015 2:24 PM