Link to home
Start Free TrialLog in
Avatar of NIS_RULE
NIS_RULEFlag for United States of America

asked on

Is it possible to replace a corrupt SCCM server with a new server while retaining data?

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.

Avatar of Adam Leinss
Adam Leinss
Flag of United States of America image

Why salvage? What data are you trying to save?  Just build a new SCCM, then re-push the client with a new site code.  It should pull back in all of the client inventory using WMI.

Adam is right. Just get latest Current Branch and install it. Use Server 2016 and SQL 2016 if possible too to avoid the pain later. If you ONLY have clients talking to service now there is NO data to save. You can just export collections if you want those. Job done.

+1 for what the other guys have said to an extent, they are right - especially based on your final line - if SCCM isn't actually being used for applications, task sequences etc - there doesn't sound like there is any information that needs saving - unless were all missing something ?

"If so, is there any documentation from MS or anyone else that shows what needs to be done?"

There isn't - as far as I'm aware - but it basically looks like this
- Install your new SCCM hierarchy
- Either
- start from scratch - given the state of the existing environment, you may save yourself time and money by just re-creating everything. Its also often a good opportunity to get rid of old stuff and implement good naming standards etc.
- you could try and run a site restore (given your DB is still health by the sounds of the original post) then migrate your applications, packages, collections etc. (as you wouldn't want to keep using your old site - even if a site restore somewhat "fixes it")
- With either solution, you will need to redeploy your clients to point to the new hierarchy... you can do this many ways, client push, a startup script such as, your own script etc.

A 1/2 decent SCCM person should be able to help you get back up and running in 2-3 days + time to either "fix and migrate" or "start from scratch" on your packages etc.
Avatar of NIS_RULE
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial