You don't restore the CM Server using any snapshots. (At least not officially) You using the built-in task to back up or SQL backups. Then you restore using those methods which are documented. Afterwards you clean up the mess. Or to start net new and avoid most of the mess but lots of extra work as you need to recreate everything.Thanks Garth for replying. Unfortunately that is only way we take backup hence why it was the only way we could restore it the VM.
Which other way would you suggest to restoring a VM?
I just checked we do not have Microsoft Support plan so this is on us to figure out how to resolve the issue.
Alternatively, It might be worth having new 2016 VM server built and setting up a new SCCM on it. Any guidelines you can provide me please?
Hi AhmedLS, thanks for your reply - If we had known we could have checked this before restoring back. But we plan on upgrading it again and this time we will check the WMIas far as the upgrade part, i did an upgrade from 2012R2 to 2019 few months ago and the first try went bad so a restored the snapshot. all worked fine after that with no issues.
i did another try after couple of weeks and had the same issues as you described (Sccm was not able to load). the issue was with WMI. after the uppgrade the SCCM WMI disappeared from WMI managment. i just added them and all worked. i dont remember which ones were missing after the upgrade but SMS was one of them. you can take a screenshot to what you have before the upgrade then update wmi afterwords.
View attachment 4854
Thanks Garth. Noted!You don't restore the CM Server using any snapshots. (At least not officially) You using the built-in task to back up or SQL backups. Then you restore using those methods which are documented. Afterwards you clean up the mess. Or to start net new and avoid most of the mess but lots of extra work as you need to recreate everything.