Jump to content


Inherited sabotaged SCCM 2012r2

Recommended Posts

Issue: Current SCCM 2012r2 has not been able to provide Windows updates since 01/07/2015.

History: On 01/07/2015 a predecessor, apparently, installed KB 2734608 and promptly started updates to all the enterprise servers. Of course, they all tried to reboot during business hours. He was instructed to “Stop the process immediately” which he did, and the system has never worked since. There is no documentation as to what he did, what his successors did, or a backup of the application/ server prior to the event.

Current configuration:

Platform: Windows server 2008 r2 (Updates on this server are current)

IIS version 7.0

WSUS is version 3.0 with SP2 (3.2.7600.226)

SCCM for manual deployment of 3rd party applications and endpoint protection currently works.

Windows Update Services do not synchronize.

SQL version 2008r2 (64bit)

Endpoint protection, system imaging, 3rd party application deployments/updates work OK. Just WSUS does not work.

Hierarchy demands previous content files and packages be retained.

Currently have a 2007 SCCM that was updated to 2012, then r2 running on a 2008 server.

Since migration to server 2012r2 requires a fully functional SCCM at start, this is not an option.

Bottom line is I am faced with a sabotaged system, 18 months of ‘well meaning database programmers’ trying to “fix the WSUS system” and no documentation of who did what. If the entire system had failed this would be easy, but everything works BUT the WSUS.

End result should have same site code, content database, and program folder.

All comments appreciated.


Share this post

Link to post
Share on other sites

My first thought is to bring up a brand new server and start from scratch. It would be much easier to install a new, fully functional system that it would be to reverse engineer someone elses mistakes and try to correct them. You can use the came content database and import the TS/Apps from the other system (although if you aren't using the PS App Deploy Toolkit for your apps I would suggest changing over). Install a new WSUS and sync that up and start moving the clients over.


Will it have the same site code if you do this? No, it wont. You will need to create a different site code for the new system but in the end that isn't the worst thing that could happen.


If you must keep the same infrastructure I would remove WSUS completely, delete the DB, remove everything and reinstall WSUS and create a new DB. Again, too hard to fix especially when its not documented.

Share this post

Link to post
Share on other sites

also use windows server 2012r2 in order to support Windows 10 servicing going forward,

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...