Delete failed SCCM site server (SCCM 2012)

Today I came across an issue with SCCM that I have never had to deal with. One of our AD controllers at a remote site took a dive, this system was also our site system for this location. I was able to remove the Distribution Point and Software Update Point Roles from the server but when I tried to delete the Component Server Role I had a greyed out remove. Trying to delete the whole system returned an error:




If you would delete the system from AD and wait 24 hours the clean up process would detect the change and allow you to delete it the next day. This wasnt good enough because I needed a quick turn around. To get around this timer, head into the registry: HKLM\Software\Microsoft\SMS\Components\SMS_SITE_COMPONENT_MANAGER\Component Servers\SERVERNAME

In each subkey but also including the root, there will be a key called “Deinstallation Start Time”, set this value to 1.


Once this is done for each subkey, restart the Site Component Manager Service. At this point you should be able to delete your failed Site Server from SCCM!

14 comments… add one
  • Satisfied User Link Reply

    I spent a good two hours looking for ways to do this, including what was initially mentioned. Using that registry hack was what did the trick for me! Removed successfully. Thanks man!


    Thanks so much for this!!! I have been spending hours trying to find a way to force delete the new MP/DP and well… nothing work. This was teh first useful information I ran across that actually helped me remove this from ConfigMgr! Thanks

  • Mike S Link Reply

    Nice work, helped me out 4 years later.


  • LFrederick Link Reply

    This did not work for me either. Any other ideas? I have SCCM Console version 5.00.8577.1100.

  • LFrederick Link Reply

    Ok it finally worked. Not sure why I had to wait 15 minutes then stop then start the service a couple times, close and reopen the console but it finally let me delete the component services role and then the DP.

  • Holden Link Reply

    I have the 1806 release and this still worked. I’m happy I found your post after almost an hour of searching. This needs to be published more! Thank you!

  • Marc Link Reply

    Thank you so much ! You saved me hours of researches 🙂

  • Derek Mabon Link Reply

    Hey Dylan, I just thought you should know that in 2019 this post is still being referenced as “the fix”. Thought you would get a kick out of that. 🙂

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.