![microsoft sccm 2012 r2 evaluation download microsoft sccm 2012 r2 evaluation download](https://3.bp.blogspot.com/-HzYv_vCR-_g/Um-kgHg56aI/AAAAAAAADTs/qZxodf-v0c8/s1600/15.png)
Run the ‘Configuration Manager Health Evaluation’ scheduled task (ccmeval.exe) a couple of times.Stop any ccmrepair.exe or ccmsetup.exe process so they don’t hinder step 3.Compile the mof file %program files%\Microsoft Policy Platform\ExtendedStatus.mof.To fix the broken ConfigMgr client I did the following:
#Microsoft sccm 2012 r2 evaluation download update
They also wouldn’t update the Docs as they couldn’t reproduce the issues internally even though I’m not the only one to report them.Īnyway, I’m documenting here what I did to fix it and the scripts I used. When I contacted Microsoft support they suggested to perform a site reset, but when you have many servers to upgrade that isn’t viable. It’s quite possible something on the servers contributed to these issues happening, but they were actually fairly clean boxes – physical HP servers running only the ConfigMgr client, some HP software, antivirus and a few agents such as MMA and Azure agents. This essentially breaks the distribution point role as no packages can be updated or distributed to it and content validation will fail The root\SCCMDP namespace was missing from WMI.MSI: Setup was unable to compile the file DiscoveryStatus.mof. Digging in the logs, I could see that ccmrepair.exe was running and attempting to fix the client, however it was repeatedly failing with the following error: The SMS Agent host (ccmexec) service was not running and would not start. The ConfigMgr client was broken – specifically WMI.However, after the upgrade I found two big issues on each server: I scripted the process to automate it and deployed it via MEMCM and the servers upgraded in around 1-1.5 hours.
![microsoft sccm 2012 r2 evaluation download microsoft sccm 2012 r2 evaluation download](https://i2.wp.com/eskonr.com/wp-content/uploads/2012/09/SCCM2012-Installation-CAS-19.jpg)
After reading the MS Docs, I concluded this is a supported scenario and things would go smoothly.
![microsoft sccm 2012 r2 evaluation download microsoft sccm 2012 r2 evaluation download](https://www.betaarchive.com/imageupload/2013-06/1372133598.or.18500.png)
In my MEMCM primary site I had several distribution points that were still running Windows Server 2012 R2, so I decided to run an in-place OS upgrade on them to bring them up to Server 2019.