We have a SCCM server (single site) that has stopped working after Microsoft has been trying to get it to install patches beyond 1710 build. It started out with the system refusing to install updates, then MS support got involved, got it to install the 1706 and 1710 update after weeks of messing around. but then it wouldn't install the 1802 update. Then after several months of working with MS support, something they did killed the SCCM server so the console wouldn't even start. Opened another ticket with MS support, and after two weeks they said the console won't start because WMI is corrupt on the server. They installed the console on a test machine and was able to start it, however it looks like none of the clients has connected with the server in weeks if not longer. Anyway, MS stopped spending any time/resources trying to fix what they messed up.
Now what we're asking is, if it's possible to build a new server from scratch, using the latest version of SCCM, and then migrate all the data from the old (now dead) SCCM server and maintain all the client connectivity? If so, is there any documentation from MS or anyone else that shows what needs to be done?
We're trying to salvage as much as we can. The only thing we use SCCM for is to report clients to Service Now (for Configuration Item assignment). We do not use SCCM to push out patches or manage the clients in any other way.