I open a DOS window and browse to c:\windows\system32\ccmsetup\{6A438387-0FF9-4620-947E-39470FB1E2E5}

The number will be different

type in msiexec /x client.msi

Not sure if that is the right way or not

• Proposed as answer by Mahmoud M. Omar Tuesday, July 10, 2012 8:43 AM

I open a DOS window and browse to c:\windows\system32\ccmsetup\{6A438387-0FF9-4620-947E-39470FB1E2E5}

The number will be different

type in msiexec /x client.msi

Not sure if that is the right way or not

• Proposed as answer by Mahmoud M. Omar Tuesday, July 10, 2012 8:43 AM

hallo,

how can i uninstall the SCCM Client ? I cannot see a option in ADD/Remove Programs.

thx

Oliver

I open a DOS window and browse to c:\windows\system32\ccmsetup\{6A438387-0FF9-4620-947E-39470FB1E2E5}

The number will be different

type in msiexec /x client.msi

Not sure if that is the right way or not

• Proposed as answer by Mahmoud M. Omar Tuesday, July 10, 2012 8:43 AM

msiexec /x is one way of uninstalling the other way is to use ccmclean from the sms 2003 toolkit 2.

Run ccmclean /client (/removehistory is optional)

You can also use "ccmsetup.exe /uninstall" - new to Configuration Manager.

-Jon

• Proposed as answer by elstbvander Friday, June 01, 2012 12:54 PM

You can also use "ccmsetup.exe /uninstall" - new to Configuration Manager.

-Jon

• Proposed as answer by elstbvander Friday, June 01, 2012 12:54 PM

You can also use "ccmsetup.exe /uninstall" - new to Configuration Manager.

-Jon

• Proposed as answer by elstbvander Friday, June 01, 2012 12:54 PM

Yes, please note that ccmclean is not supported with Configuration Manager clients (don't thinkit works) - ccmsetup.exe /uninstall is the only supported method.

From "What's New in Client Deployment for Configuration Manager" (http://technet.microsoft.com/en-us/library/bb693939.aspx):

Uninstalling the Configuration Manager Client Software

The ccmclean.exe utility provided with SMS 2003 Toolkit 2 cannot be used to uninstall the Configuration Manager 2007 client software. To successfully uninstall the Configuration Manager 2007 client software you must use the CCMSetup.exe executable together with the /uninstall property.

For more information, see How to Uninstall the Configuration Manager Client.

- Carol

This posting is provided AS IS with no warranties and confers no rights.

• Proposed as answer by DaninIT Friday, April 15, 2011 7:13 PM

Yes, please note that ccmclean is not supported with Configuration Manager clients (don't thinkit works) - ccmsetup.exe /uninstall is the only supported method.

From "What's New in Client Deployment for Configuration Manager" (http://technet.microsoft.com/en-us/library/bb693939.aspx):

Uninstalling the Configuration Manager Client Software

The ccmclean.exe utility provided with SMS 2003 Toolkit 2 cannot be used to uninstall the Configuration Manager 2007 client software. To successfully uninstall the Configuration Manager 2007 client software you must use the CCMSetup.exe executable together with the /uninstall property.

For more information, see How to Uninstall the Configuration Manager Client.

- Carol

This posting is provided AS IS with no warranties and confers no rights.

• Proposed as answer by DaninIT Friday, April 15, 2011 7:13 PM

Yes, please note that ccmclean is not supported with Configuration Manager clients (don't thinkit works) - ccmsetup.exe /uninstall is the only supported method.

From "What's New in Client Deployment for Configuration Manager" (http://technet.microsoft.com/en-us/library/bb693939.aspx):

Uninstalling the Configuration Manager Client Software

The ccmclean.exe utility provided with SMS 2003 Toolkit 2 cannot be used to uninstall the Configuration Manager 2007 client software. To successfully uninstall the Configuration Manager 2007 client software you must use the CCMSetup.exe executable together with the /uninstall property.

For more information, see How to Uninstall the Configuration Manager Client.

- Carol

This posting is provided AS IS with no warranties and confers no rights.

• Proposed as answer by DaninIT Friday, April 15, 2011 7:13 PM

Hi to all,

One additional Question in this case, does anybody know, how can i prevent a SCCM DP to get a SCCM Client.

Would it be helpful when i exclude the Server IPs from the Site Boundaries?!? Backgroud is, we have at the moment

one extra WSUS Server for Servers. When a SCCM DP get the SCCM Client, the Registry Entry for Windows Update will change to the SCCM SUP Server.

Best Regards

Hi

You can exclude the server from push installations by adding the server name to the registrykey ExcludeServers under HKEY_LOCAL_MACHINE/Software/Microsoft/SMS/Components/SMS_DISCOVERY_DATA_MANAGER on you site server. You find more information about this here:

http://technet.microsoft.com/en-us/library/bb693996.aspx

You know, I have seen this posted all over the place and I just have to let you know it didn't work for me. It worked under SMS 2003, but under SCCM it completely ignored it and installed on all my servers including my citrix servers. The interesting thing was that the client wouldn't install on hardly any of the PCs with the 2003 client on them until I enabled the Software Update install method which made even more of a mess since many of the PCs would basically lock up when rebooting because it had an update to install. The PC would just hang there for an hour or more until we physically powered off the PC or Damewared into the process and killed ccmsetup.exe.

Oh, and ccmsetup /uninstall on mine only brings up the window were it is installed, it does not uninstall it.

• Proposed as answer by Tubs74 Thursday, November 28, 2013 7:56 PM

You know, I have seen this posted all over the place and I just have to let you know it didn't work for me. It worked under SMS 2003, but under SCCM it completely ignored it and installed on all my servers including my citrix servers. The interesting thing was that the client wouldn't install on hardly any of the PCs with the 2003 client on them until I enabled the Software Update install method which made even more of a mess since many of the PCs would basically lock up when rebooting because it had an update to install. The PC would just hang there for an hour or more until we physically powered off the PC or Damewared into the process and killed ccmsetup.exe.

Oh, and ccmsetup /uninstall on mine only brings up the window were it is installed, it does not uninstall it.

• Proposed as answer by Tubs74 Thursday, November 28, 2013 7:56 PM

You know, I have seen this posted all over the place and I just have to let you know it didn't work for me. It worked under SMS 2003, but under SCCM it completely ignored it and installed on all my servers including my citrix servers. The interesting thing was that the client wouldn't install on hardly any of the PCs with the 2003 client on them until I enabled the Software Update install method which made even more of a mess since many of the PCs would basically lock up when rebooting because it had an update to install. The PC would just hang there for an hour or more until we physically powered off the PC or Damewared into the process and killed ccmsetup.exe.

Oh, and ccmsetup /uninstall on mine only brings up the window were it is installed, it does not uninstall it.

• Proposed as answer by Tubs74 Thursday, November 28, 2013 7:56 PM

ccmsetup.exe /uninstall /forcereboot

Why just not to kill the SMS service and remove CCM and CCMsetup directories? I don't have the ccmsetup.exe in SCCM client and WIN7 workstation.

Hi,

For those who (had to) use(d) the .msi installler and not the .exe there is another .msi installed in %windir%\ccmsetup\<msi uid>\client.msi

If you uninstall this client.msi the two sccm 2007 client services and registry entries will be uninstalled. You must still manually delete the ccmsetup dir from %windir%

I see this error on few clients while using ccmsetup /uninstall command:

"The description for Event ID ( 1040 ) in Source ( MsiInstaller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description "

and client dont get removed. Please help.

I have tried the commond line in cmd. but It siad " 'ccmsetup.exe' is not recognized as an internal or external command".

I don't know what location I should stand and type this command.

Please, help

Thanks

Is there a methode to centraly uninstall installed agents on multiple machines? Hopefully from the SCCM console...

Agents are unexpected deployed to a set of machines, so we want to remove them.

• Edited by Arjen Furster Tuesday, October 18, 2011 7:26 PM

Is there a methode to centraly uninstall installed agents on multiple machines? Hopefully from the SCCM console...

Agents are unexpected deployed to a set of machines, so we want to remove them.

• Edited by Arjen Furster Tuesday, October 18, 2011 7:26 PM

Is there a methode to centraly uninstall installed agents on multiple machines? Hopefully from the SCCM console...

Agents are unexpected deployed to a set of machines, so we want to remove them.

• Edited by Hardinxcore Tuesday, October 18, 2011 7:26 PM

There's nothing built into the console but you can use this nice tool that adds extensions to right click menu: http://myitforum.com/cs2/blogs/direland/pages/sccm-console-extensions.aspx 

I've done this and on some computers it works, but on several more it does not work. When I check the log it says it unistalled, but after the reboot the Configuration Manager is still there. How do I uninstall if the ccmsetup.exe /uninstall /forcereboot command doesn't work?

I've done this and on some computers it works, but on several more it does not work. When I check the log it says it unistalled, but after the reboot the Configuration Manager is still there. How do I uninstall if the ccmsetup.exe /uninstall /forcereboot command doesn't work?

Just a reminder to those out there with 64bit windows 7 - I found this in c:\Windows\ccmsetup

not c:\windows\system32\ccmsetup

can then run

ccmsetup.exe /uninstall

or

cd to the {43647-... dir and execute

msiexec /uninstall client.msi

worked a charm.

• Proposed as answer by Spam filter Tuesday, January 22, 2013 1:41 PM

Just a reminder to those out there with 64bit windows 7 - I found this in c:\Windows\ccmsetup

not c:\windows\system32\ccmsetup

can then run

ccmsetup.exe /uninstall

or

cd to the {43647-... dir and execute

msiexec /uninstall client.msi

worked a charm.

• Proposed as answer by Spam filter Tuesday, January 22, 2013 1:41 PM

Hi Heldesk and All

I'm quite surprised you guys keep mixing two methods of removing SCCM Client (Configuration Manager) instead of simply following up on MS advice that can be found on the same site called System Center. It's simply placed in their library: http://technet.microsoft.com/en-us/library/bb694276.aspx

Dspite all that it should be also the latest information alligned to current OSes in use and IT infrastructures.

Hope this helps in the future answering the question "which one shall I use?".

Greetings!

Muzzy

That is all you need and the only right way recommended by Microsoft

Hi,,

1- map the sccm share (SMS_???) with a drive letter for example z:

2- click windows + R and type msiexeci.exe /x z:\client\x86\client.msi ( if you have a 64 bit client you must type z:\client\x64\client.msi)

3-Follow instructions to uninstall client and reboot your client

Great this worked as expected.

Thanks

• Edited by AINAMDAR Monday, November 11, 2013 8:23 AM

Great this worked as expected.

Thanks

• Edited by AINAMDAR Monday, November 11, 2013 8:23 AM

Great this worked as expected.

Thanks

• Edited by AINAMDAR Monday, November 11, 2013 8:23 AM

While the /uninstall switch does indeed uninstall the SCCM client 2012 R2 SP1, it does NOT remove it fully.

smscfg.ini stays behind.

Plenty of registry entries are also left behind:

HKEY_LOCAL_MACHINE\softtware\Microsoft\SMS

HKEY_LOCAL_MACHINE\software\Microsoft\SystemCertificates\SMS

I find it simply unacceptable!

Uninstall should be full, not partial

Seb

• Edited by scerazy 23 hours 46 minutes ago

While the /uninstall switch does indeed uninstall the SCCM client 2012 R2 SP1, it does NOT remove it fully.

smscfg.ini stays behind.

Plenty of registry entries are also left behind:

HKEY_LOCAL_MACHINE\softtware\Microsoft\SMS

HKEY_LOCAL_MACHINE\software\Microsoft\SystemCertificates\SMS

I find it simply unacceptable!

Uninstall should be full, not partial

Seb

• Edited by scerazy Monday, August 24, 2015 7:53 AM

While the /uninstall switch does indeed uninstall the SCCM client 2012 R2 SP1, it does NOT remove it fully.

smscfg.ini stays behind.

Plenty of registry entries are also left behind:

HKEY_LOCAL_MACHINE\softtware\Microsoft\SMS

HKEY_LOCAL_MACHINE\software\Microsoft\SystemCertificates\SMS

I find it simply unacceptable!

Uninstall should be full, not partial

Seb

• Edited by scerazy Monday, August 24, 2015 7:53 AM