ConfigMgr Client failing to install on Management Point

In ConfigMgr Current Branch, version 1511/1602 you have a new pre-production client upgrade feature that allows you to test the new client install on a pre-preproduction collection. The feature works like a charm and allows you to gain control over the upgrade process by testing first. However, while testing the new client, you might run into client installation issues if you are installing a new client on a Management Point.

In ccmsetup.log on the management point you will see errors stating that “The client version 5.00.8325.1000 does not match the MP version 5.00.8355.1000.  The client will not be installed.”

image

The fix is easy, the only question is – if you are ready. Configure you the client install options to deploy to production instead of the pre-production collection. That can be done from Cloud Services, Updates and Servicing. You’ll notice in the illustration below that Client Update Options is still in pre-production (if it was not, the option would be grayed out).

image

Click Client Update options and enable I’m ready……

image

After that, time to spend a few seconds in cmtrace reading hman.log (on the site server). Notice that both the preproduction and production packages are impacted by your recent change. Look for the line Loaded client upgrade settings from DB successfully. FullClientPackageID=PS100002, StagingClientPackageID=PS100007, ClientUpgradePackageID=PS100003, PilotingUpgradePackageID=PS100008, ClientUpgradeAdvertisementID=PS120000, ClientPilotingAdvertisementID=PS120003

image

After the upgrade, your management point will successfully install.

By | 2016-03-22T11:30:53+00:00 March 22nd, 2016|Configuration Manager (SCCM)|3 Comments

About the Author:

Kent Agerlund
Microsoft Regional Director, Enterprise Mobility MVP. Microsoft Certified Trainer and Principal consultant. I have been working with Enterprise client management since 1992. Co-founder of System Center User Group Denmark in 2009. Certified MCITP: Enterprise Administrator, MCSA+Messaing, and much more. Member of: Microsoft Denmark System Center Partner Expert Team The Danish Technet Influencers program System Center Influencers Program.

3 Comments

  1. Bongani August 29, 2016 at 10:40 - Reply

    Good day Kent
    I am busy designing for a client and I am wandering – is it possible to install the client as a first install?
    In other words :
    1 can I complete the CAS install on base 1511 and upgrade and
    2 then do the database move to a SQL always on and
    3 Primary Site install on 1602 then
    4 deploy the clients?

    Or do I have to do the 1511 completely (meaning must I first do a full install of CAS then Primary site then ) including clients, and then only after that do the upgrade?

  2. Kent August 29, 2016 at 10:41 - Reply

    No, you can wait with the client upgrade until 1602/1606

    • Bongani August 29, 2016 at 14:30 - Reply

      Thanks a million for clearing this for me.

Leave A Comment