If you see a folder called ccmcache the uninstallation is definitely still running.
After this, reboot your PC, and you should finally be free of the System Center 2012 Endpoint Protection client (assuming you haven’t set it up to reinstall by Group Policy or an Active System Center server).
If computers are combined into groups and the optimal updating procedure is different for various groups, you can create a customized update task for each group.
Please keep in mind that if both parent and child groups have tasks of the same type, the computers of the child group will run both tasks.
Even after removing all traces of System Center 2012 from our AD network, when I uninstalled the client software from each user system, within a few hours (or post a reboot) the software would mysterious regenerate and come back. Uninstall: System Center 2012 Endpoint Protection Client.
Working on the assumption you are using Windows 7, go in to control panel and select Programs and Features.
I found it took up to 10 minutes for the uninstall to release a lock on the setup files (and presumably possibly this long to actually carry out the uninstall).
So after 10 mins, close the command line window, and do a search for %windir%.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119 [RFC2119].
Windows Firewall Configuration Provider Having done this, load up the command line (cmd) with administrative priviledges (search for and right click to get this option).
Then type in the following commands at the prompt: cd c:\windows\ccmsetup ccmsetup /uninstall The cursor will just return without any confirmation of completion.
Clients MUST send all JSON API data in request documents with the header .
JSON API documents are defined in Java Script Object Notation (JSON) [RFC7159].