Comments on: SCCM Client Complete Uninstall / Remove + Powershell Script

By: Core Optimizer

Core Optimizer — Sun, 07 Sep 2025 19:33:48 +0000

In reply to Anonymous. You're welcome

By: Anonymous

Anonymous — Wed, 14 May 2025 18:31:03 +0000

Thanks!!!

By: Core Optimizer

Core Optimizer — Mon, 02 Sep 2024 11:34:41 +0000

In reply to Anonymous. Thank you!

By: Anonymous

Anonymous — Mon, 26 Aug 2024 21:13:41 +0000

Great instructions. Thanks!

By: Anonymous

Anonymous — Fri, 18 Mar 2022 17:49:03 +0000

Thank you. Worked a treat for resolving an issue. I had duplicate GUIs from clones. Uninstalling the agent from the master image was not enough.

By: coreoptimizer

coreoptimizer — Sat, 31 Oct 2020 14:52:31 +0000

In reply to Martin Tylich.

Hello Martin,
Possible issues could be:
* Some process holds the folder – Try to find it and kill
* You don’t have enough permissions on this host
* Try running the script as Administrator

By: Martin Tylich

Martin Tylich — Tue, 13 Oct 2020 19:01:45 +0000

Hi please how can I solve problem that I cannot remove entire content of C:\Windows\CCM?

Access denied

By: coreoptimizer

coreoptimizer — Mon, 14 Oct 2019 13:21:39 +0000

In reply to George Jenkins. You're right it will be much easier to monitor the process and then send the restart by powershell. You can add many checks during the run to hide the red lines. This script was published for SCCM professionals to get rid of all the leftovers of the client for the maintenance purposes. It just takes more time to add these checks and for the script to run. This script should be as simple as possible without too much code as it is a maintenance tool and related for experienced users. I believe that the more code you add the more error there could be during the runs. So I don't think all the checks are necessary, but off course you can do as you think best suits your needs. From my experience with the SCCM client removal it is best to restart after the regular /uninstall command as there are still services, registry and WMI entries that can be locked and this script simply won't be able to remove them all. Too bad Microsoft makes it THIS hard to do something that simple. I'm glad this is worked for you!

By: George Jenkins

George Jenkins — Thu, 12 Sep 2019 16:53:11 +0000

I noticed most of the files and keys were removed during the ccmsetup.exe /uninstall command. Why not monitor win32_process for ccmsetup then execute the rest of the script after ccmsetup is gone from win32_process. Also, place test-path for each of the lines so there’s not so much red text while running the script. I don’t think there’s a restart required until all the script components have been removed (but I haven’t tested this much yet). Thanks for posting this information. Worked like a charm and the SCCM server has pushed out an updated ccmsetup client to my workstation that had a corrupt installation.