Forum Discussion
Solved
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...
I just encountered exactly this issue i.e. MicrosoftPolicyPlatformSetup.msi fails to install when trying to install a ConfigMgr 2303 client on a Win10 laptop that previously had a ConfigMgr 2012 R2 client on it. I found this thread but time has moved on so the oldest baseline version I can download now is 2303 and thus I can't use the workaround dicussed here because I can't get access to the 2207 ISO.
I have tried everything I can think of to get rid of the 2012 R2 client, delete WMI namespaces, registry info etc. but nothing I have found will allow me to install a supported ConfigMgr client.
I have tried the client with and without the hotfixes for 2303, same fault in each case.
Haven't tried 2309 yet as I think it's still in the "early release" ring.
Does anyone have any thoughts on how to get our many Win10 devices with ConfigMgr 2012 R2 client upgraded with a supported version of the client?
It's starting to look like we have to re-image all the laptops which would be quite disruptive etc.
I have tried everything I can think of to get rid of the 2012 R2 client, delete WMI namespaces, registry info etc. but nothing I have found will allow me to install a supported ConfigMgr client.
I have tried the client with and without the hotfixes for 2303, same fault in each case.
Haven't tried 2309 yet as I think it's still in the "early release" ring.
Does anyone have any thoughts on how to get our many Win10 devices with ConfigMgr 2012 R2 client upgraded with a supported version of the client?
It's starting to look like we have to re-image all the laptops which would be quite disruptive etc.
matthewj718 I've attached a .zip file containing the older version of the MicrosoftPolicyPlatformSetup.msi that we've installed on client PCs running SCCM 2012 R2, to then allow them to upgrade to newer versions of ECM. I hope it helps!