I've seen this come up on older posts but it never gets a far as a solution that work for me. so here goes....

I have several machines which are only showing two actions and not acknowledging that packages are being advertised to them and the repair within the client is not correcting the issue or is unavaible(greyed out).

I'm trying to uninstall the client, so i can push a fresh install, using 'ccmsetup /uninstall' which in normal situations works for me but on these machines that are only showing two actions the client isnt uninstalling infact the uninstall doesnt seem to do anything...

the ccmsetup.log isn't showing that i've done anything at all... in fact there are no entries for over a week which is when the system was originally imaged using SCCM.

I have also tried the 'client.msi /uninstall' but it is throwing an error... 'This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor............................' 

Thoughts?

Try copying the entire SMSClient folder from the server to somewhere on the workstation, say into c:\Windows\temp\SMSClient, and then run CCMSetup.exe /uninstall from there.

I have seen a couple of cases where I was not able to de-install the client, where it would give me an error somewhere in the \windows\system32\ccmsetup logs complaining about not being able to find ccmsetup\{35BE0386-E1B9-4F59-8DBD-E5B390AA8A09}\client.msi.  This happens to be the SP1-version of the SCCM client, but I have the SP2 client installed.  Why is it looking for the SP1 client.msi when I'm trying to de-install the SP2 client?  I happened to have a copy of the SP1 .msi kicking around, placed it there manually, and then was able to successfully de-install the client.

Nick.

Hi KPRDave,

First of all, from your description your clients with two actions was having problem about client assignment, so try to fix it first.

Read this technet blog about Troubleshooting sccm client not reporting

Finally if upon blog can't help to fix the client assignment problem, try to reinstall it.

ccmsetup.exe /uninstall is the only supported methord to uninstall sccm 2007 client.

I have met this problem, ccmsetup.exe /uninstall command did not work and sccm applet is still in control panel. Then I google it, find msiexec /x client.msi is a workaround to uninstall the sccm client.

You can find client.msi in ccmsetup folder.

Hope this will help.

Thanks

• Marked as answer by Sabrina Shen Monday, April 02, 2012 8:58 AM

I've seen this come up on older posts but it never gets a far as a solution that work for me. so here goes....

I have several machines which are only showing two actions and not acknowledging that packages are being advertised to them and the repair within the client is not correcting the issue or is unavaible(greyed out).

I'm trying to uninstall the client, so i can push a fresh install, using 'ccmsetup /uninstall' which in normal situations works for me but on these machines that are only showing two actions the client isnt uninstalling infact the uninstall doesnt seem to do anything...

the ccmsetup.log isn't showing that i've done anything at all... in fact there are no entries for over a week which is when the system was originally imaged using SCCM.

I have also tried the 'client.msi /uninstall' but it is throwing an error... 'This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor............................' 

Thoughts?

Not read below maybe it has already been answered, this sounded a lot like using an older version of CCMSETUP to uninstall with ... I've had this in the past where CCMSETUP from 2.50 (SMS2003) was being used to uninstall the 4.00 (ConfigMgr) Client. Maybe clean your CCMSETUP out and replace with the copy from the Site server ...

You could go all out and nuke it with CCMCLEAN /ALL, although it is unsupported it does work (SMS2003 Toolkit tool) and is used daily by us ConfigMgr admins :-) (Maybe not daily for me, but for some maybe ... !)

• Marked as answer by Sabrina Shen Monday, April 02, 2012 8:58 AM

Look for a process on that client called "CcmExec.exe" and end process, then rerun your ccmsetup.exe /uninistall as administrator.  This worked for me on all problem machines.  

Thank you Quan Xu, the msiexec /x client.msi did the trick for me. 

In my instance, I have found that my WinPE deployment task with is somehow pointing the SCCMClient install to the D:\ drive (which doesn't exist).  The symptoms on the deployed computer showed the client was installed but not attached to the site, could not pull policies, etc.  

Another thread details this:https://social.technet.microsoft.com/Forums/en-US/403d987b-4ea3-48fc-890f-5ae37805342b/config-manager-client-is-not-working-right-after-osd-sccm2012-sp1-cu3?forum=configmanagerosd