Forum Discussion
After upgrade to Configuration Manager 2211, MicrosoftPolicyPlatformSetup.msi won't install
After upgrading to Configuration Manager 2211, manual client installations invoked from <servername>\c$\Microsoft Configuration Manager\Client\CCMSetup.exe fail at the point of installing the Microso...
- We did not encounter the issue when installing the ConfigMgr 2211 client on a new PC. So it appears that it's only an issue when upgrading in place from ConfigMgr 2012 R2 to ConfMgr 2211.
SuperMJT I haven’t seen this issue yet. However, you can try capturing the verbose log by using /l*v during manual installation and look for value 3 in the msi log. That should give you the reason for the fatal error code 1603.
rahuljindal-MVP Please see my response below. This is not an isolated incident.
- Perhaps you can use your existing environment to push out MicrosoftPolicyPlatformSetup.msi to each PC from the 2207 ISO, then roll out the client upgrade.
- SuperMJT - your workaround works! I'm deploying the baseline 2203 platform msi using the old site server and then pushing clients from the new MP. Thank you for your help! Now, Let's hope that A: Someone in the same situation finds this helpful and B: MS will correct the faulty msi in the next CB version. 🙂
- I'm glad to hear that the workaround is effective. Today, I'm going to try upgrading the ECM client on some PCs that have a slightly older client version and see which ones upgrade successfully. From your experience, it sounds like at least 2203 and 2207 clients can upgrade in place without first manually installing MicrosoftPolicyPlatformSetup.msi.
SuperMJT Yes, that seems like a workable path. Is that how you did it or did you simply reinstall the computers?
- We were performing a number of software updates on all PCs, by accessing each PC directly. It was near the end of this migration that we updated to 2211 and run into the issue, so we just added the manual install of MicrosoftPolicyPlatformSetup.msi at the front of manually upgrading the ECM client.
