Services have a display name and then their real name. It seems like net.exe is fine with either one. Like, I think that the service that we all know and love and call the server service has an actual internal name of lanmanserver, which should make the older folks on this list think of simpler times that have past. :) You can see the real service name in services.msc if you look at the properties. Just look once and memorize it. I guess in this case, the real service name is popfile. Nice guess. :] -----Original Message----- From: Sorin Srbu Ray Costanzo <> scribbled on Tuesday, April 01, 2008 1:57 PM: Excellent! Just tried it and it seems to work, except for the fact it doesn't recognise the full service name for some reason... Example: I want to check on a spamfilter running on a remote server as a service. This service has the habitual habit to die for no apparent reason on a irregular basis. Normally I'd use a psexec command such as: psexec \\server -u username -p nottellingyou net start Which would run a net start on Server and you'd get back the whole list of running services, which is not really feasible at all times. I then used sc according to your sample: sc \\server query "POPFile Automatic Email Classifier" "POPFile Automatic Email Classifier" is the service name. The result from the sc command is that the service is not found which is kinda' weird... Doing a sc \\server query popfile Returns a "running" status. If I stop the service manually and rerun sc \\server query popfile It says it's stopped as expected, although flakey, unless I'm missing something here. ***************************** New Site from The Kenzig Group! Windows Vista Links, list options and info are available at: http://www.VistaPop.com ***************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm