Manual removal of SCCM client

If you need to remove the client you can do so fairly easily by running ccmsetup.exe /uninstall.  Ccmsetup should exist on all clients, usually under the windows folder.  In the event that the command line doesn’t work here is a list of things I usually check and remove to manually clean-up all the traces of the client so I can try a fresh install.


1. SMS Agent Host Service

2. CCMSetup service (if present)

3. \windows\ccm directory

4. \windows\ccmsetup directory

5. \windows\ccmcache directory

6. \windows\smscfg.ini

7. \windows\sms*.mif (if present)

8. HKLM\software\Microsoft\ccm registry keys

9. HKLM\software\Microsoft\CCMSETUP registry keys

10. HKLM\software\Microsoft\SMS registry keys

11. root\cimv2\sms WMI namespace

12. root\ccm WMI namespace

13.  In Task Scheduler library, under “Microsoft” delete the “Configuration Manager” folder and any tasks within it.

14. In the Machine Certificate store delete any certs under the SMS\certificates folder


Repair Windows server 2016 Install

We recently had problems with a development server not installing Windows Updates. The fix was to repair the installation using the Deployment Image Servicing and Management (DISM) tool.

All commands should be run from an elevated command prompt.

  1. Run dism /online /cleanup-image /scanhealth
  2. Run dism /online /cleanup-image /checkhealth
  3. Run dism /online /cleanup-image /restorehealth
  4. Mount the Windows Server 2016 ISO as a drive (E: in this case)
  5. Run dism /online /cleanup-image /restorehealth
    /source:WIM:E:\sources\install.wim:1 /limitaccess
  6. Run sfc /scannow
  7. Run Windows Update

“Access Denied” in Runbook Designer when connecting to the System Center Orchestrator Management Server

When setting up a new Scorch server (yes even 2016) you get the message ‘access denied’ when anyone but the person who set up the server tries to access the runbook designer.