This blog post will learn the best way to uninstall SCCM clients in different ways. You have several options to remove the ConfigMgr client from Windows 11 or Windows 10 PCs.
Let’s understand the best way to uninstall the SCCM client (How to Remove ConfigMgr Client) from a Windows 10 or Windows 11 device.
SCCM Client agent removal and cleanup is the most challenging part for many ConfigMgr Admins because there are different ways to uninstall or remove the ConfigMgr client. We will also see how to remove device records from the SQL database.
The following is one of the top viewed posts – How to Uninstall Remove SCCM Client using CCMClean exe | ConfigMgr. Microsoft anymore supports the CCMCean tool, but I could see it still works.
I don’t recommend uninstalling the ConfigMgr client using the CCMClean tool even though it will work (shh – I still believe this tool removes the client more cleanly).
Don’t worry about the source files of ConfigMgr Client software. I will share the details of source file locations in the following section of this post. The client agent source files can be obtained from both the server and the client-side.
Remove ConfigMgr Client from Database
Before getting into the client software removal process, let’s understand how to remove the ConfigMgr client from SCCM SQL Database?.
Removing the ConfigMgr client software from Windows 10 computers does not remove the clients from the site database. The clients that are not updated are automatically purged from the site database after a while, depending on maintenance tasks /clean-up activities.
When you want to remove these clients immediately from the SMS site database, use the SCCM Administrator console to delete them.
- Navigate to \Assets and Compliance\Overview\Devices.
- Select the device record you want to delete.
- Click on the Delete button.
Click the DELETE button from Confirm Deletion Window.
Source File Location to Remove SCCM Client (Uninstall SCCM Client)
As I mentioned above, The client agent source files can be obtained from both the server and the client-side. The following is the location of the client source files C:\Windows\ccmsetup.
You can use the CCMSetup.exe file from the Windows 10 devices. You can also get the latest Configuration Manager source files from the primary server share folder.
- Client Side (Windows 10) – C:\Windows\ccmsetup
- Server Side – \\ServerName\sms_COD\Client
- Replace Servername with your primary server FQDN.
- Replace COD with ConfigMgr site code.
Uninstall SCCM Client using CCMSetup.exe Command Line
You can use the command-line option to remove the SCCM client from Windows PCs. Let’s understand uninstall SCCM Client using CCMSetup.exe the command-Line.
The deletion of a device record from the Configuration Manager console won’t remove the client agent software from Windows 10 devices.
To remove or clean up the end-to-end configurations of client software using the following command-line tool.
- Open a Windows command prompt with the administrator’s permission.
- Change the folder to the location as mentioned above
- Run the following command cd %windir%\ccmsetup
- Run the following command: CCMSetup.exe /uninstall
Logs Best Way to Uninstall SCCM Client | Remove ConfigMgr Client
The SCCM client uninstallation process using CCMSetup.exe displays no results on the screen. However, you can watch the progress of the uninstall by reading the CCMSetup.log file using the CMTrace tool.
- Location of the log file: %windir%\ccmsetup\logs\CCMSetup.log
CCMClean to Remove SCCM client – Uninstall SCCM Client using CCMClean
You can try to uninstall or remove ConfigMgr Client using the CCMClean.exe tool. This is also a command-line tool. I have a more detailed explanation of the CCMClean tool in the following post. How to Uninstall Remove SCCM Client using CCMClean exe | ConfigMgr.
Well, CCMClean is not tested (extensively) and certified by Microsoft for the products ConfigMgr 2007/2012/CB. However, it may or may not work.
In my experience, the CCMClean.exe can successfully remove/uninstall ConfigMgr/SCCM 2007, 2012, and CB client components. More details are below……
Download – > CCMClean.exe
NOTE! – Microsoft does not support CCMClean.
- The command-line parameters can be used with CCMClean.exe.
- Try and check out using “CCMClean.exe /?”
- Silent install –> ccmclean.exe /q
Verify SCCM Client Agent Uninstall
Let’s check Verify SCCM Client Agent Uninstall using the log files and WMI. I’ve tested CCMClean.exe on SCCM / ConfigMgr 2012 client and it did work perfectly !!!
- a) Verify the CCMClean.log file to get more details.
CCMCleanup Logfile location = “C:\Users\administrator\appdata\local\temp” OR %temp%
- b) Check the event log for some more details or confirmation about the SCCM Client Agent Uninstall.
Check whether the registry entry has been REMOVED from the SCCM client agent as part of the SCCM client agent uninstall process.
You can also confirm whether the SMS Agent Host service has been REMOVED as a part of the SCCM client agent uninstall process.
You can use WBEMTEST to check whether SCCM client-related WMI namespaces (root\ccm and root\cimv2\SMS) have been REMOVED or not, as shown in the below screenshot. Once the SCCM client agent is removed or uninstalled, these WMI namespaces should also get removed.
Automation Option to Remove SCCM Client from Multiple Windows PCs
You will have some options to remove the SCCM client automatically using PSExec or another scripting method. We can run the CCMSetup.exe or CCMClean.exe on multiple remote machines using PSEXEC.exe. You should have administrative privileges on that remote machine.
- How to Uninstall Remove SCCM Client using CCMClean exe | ConfigMgr
- SCCM OneTrace Log Viewer to Replace CMTrace
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.