RE: ServiceController - Requied User Permissions

I guess they are using the token from the current thread - which is your
logged on user.

If you need different credentials you would have to impersonate that user
before using ServiceController.

that said -

every service has ACLs that control who is allowed to start, stop etc.

see here: http://www.pluralsight.com/blogs/kei...0/04/2636.aspx

-----
Dominick Baier (http://www.leastprivilege.com)

Developing More Secure Microsoft ASP.NET 2.0 Applications (http://www.microsoft.com/mspress/books/9989.asp)

This is a very good question since I need an answer as well.
ServiceControl supports MachineName but doesn't support anything
related to actually authenticating to the computer mentioned in
MachineName. What's that about? At least I have not been able to
find a working example of how to connect to another computer and
perform service related functions.

I'm working on an application to monitor the state of services on
other computers. Everything work except the ability to check other
computers on the network. None of computers are part of Active
Directory so if anyone knows how to accomplish this by showing me some
demonstration code that they have actually seen work - I'd appreciate
it.

"Coy" wrote:

I want to use a ServiceController instance to control a service on
another machine. I find I can only do so by making myself an
Administrator on that machine. I need to know the specific set of
user permission that I can add to a common user to make it possible
for them to manage services remotely within a domain. An ordinary
domain user does not have these permissions. "Log on as a Service" is
not enough. Where is the entire list of required permissions, for
this purpose, documented?

Thanks