Greetings,I somehow deployed the sccm client to all pc's in my domain, i was only supposed to test this. currently its not causing any issues on the pc's that it did deploy to but i need to know the best and fastest way to remove the client since there isnt a feature in SCCM to remove the client. I suck at VBscripting, i know i know but any help is appriciated.

Create a package with no source files and a program with the command-line ccmsetup /uninstall then advertise this to all of the clients you don't want the agent on. You won't get success code back from the clients because there won't be a client there anymore to report back. Or you could use psexec and run the same command-line: ccmsetup /uninstall. psexec will take a list of systems from a text file and run the specified command on all of them.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Hi,If you are going to deploy the clients at a later time then you don't need to remove them now. Just remove any boundaries you have on the server. This will leave the clients unmanaged. This will save you a new client deployment later thus saving some bandwidth.Kent Agerlund | http://agerlund.spaces.live.com/blog/

Just remove any boundaries you have on the server. This will leave the clients unmanaged That's not true. A ConfigMgr site without any boundaries defined will work absolutely fine (except for limited roaming capabilities and content location requests).Another possibility would be (if you're planning to use ConfigMgr later): set up a GPO that sets the startup type for the "SMS Agent Host" to disabled.

Hi,Torsten, you are right :-) Best solution is to disable the service (if the client is to deployed later).Kent Agerlund | http://agerlund.spaces.live.com/blog/

Would either of you have a vbscript handy that would disable this service as i said i suck a vbscript. In the GPO the only place to realy do this is by creating a startup script that disables the service.

How about using psexec and "net stop ccmexec". No vbscript necessary.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

The only problem with using psexec in this manner is that if the pc restarts the service will start again. I dont want it running unless we decide to use it and i dont want to have to issue this command all the time. unless this will allow me to disalbe the startup type for the service it will only work temporarily and it does work :).

Your right, my bad. Use psexec (or a package) and the following two commands then (or combine them into a batch file which will increase the complexity a tad bit though): sc stop ccmexec sc config ccmexec start=disabled Here's the reference for sc: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sc.mspx?mfr=true Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

There is an extension for configmgr console that will give you an option to right click the client and say "Uninstall client". You can find it on other websites.Mayur

Jason's answer is one of the easiest compared to pushing out GPOs w/ VBscript, etc. And this will be unnoticed, if you'd rather people not be aware. Create the package, then set up an advertisement to all systems. Conversely, if you're preparing to go live, you could just leave them on there and not approve them yet. I've seen a few people do that, seems to work well. Good luck.

I agree i did have a chance to play with the sc commands and it is very easy, another thing is how do i put this in a package and advertise it the way Jason recommends or using sc to pull from a text file the list of pc's that need this disabled. Both seem like sound solutions, but I am kind of learning on the fly.

but I am kind of learning on the fly. That can be very dangerous in production environments. I highly recommend "learning" in a testlab first! You'll have to create a package without source files and "cmd /c sc bla" as the command line.

Create a batch file for ccmsetup.exe / uninstall ,run this as a startup script(computer configuration,windows setting,script,startup) in the appropriate GPO.This will uninstall the clients fast.sanka

So the way I understand this is: For the command line you would have ccmsetup.exe /uninstall and the Start in would be: C:\windows\system32\ccmsetup

That would work for a 32-bit OS only.http://www.enhansoft.com/

Garth is right, for 64-bit client us c:\windows\syswow64\ccmsetup There are many ways to do this and most of them are already mentioned in this thread. Follow me through my blog and Twitter!