Services question

  • Thread starter Thread starter fangorn.mail
  • Start date Start date
F

fangorn.mail

I have written a .NET service and it runs great. But my company uses
domain user accounts and not local user accounts, so I logged onto a
test machine with my account and installed this .NET service. I set it
to run under the LocalSystem account and Start type is manual. If
another user logs in (domain account also) to this machine, he can see
the service, but when he tries to start it an error message says
"Access is denied". Any ideas as to why only 1 user can start and stop
even though it's a domain account? How does the LocalSystem fit into
who has permissions to start and stop the service?
 
Why not you configure the account type to 'USER'. So that the service can run
in a dedicated user account within the domain.
 
Domain accounts don't automatically have the right to start and stop
Services on a system. The issue is basically whether the domain account has
admin privileges to start Services on that particular box. LocalSystem
doesn't really fit anywhere special into what you're asking - it's just a
built-in account that Services can run under.
 
So you're saying that at the domain level, the account has to be given
permission to start and stop services? That would make sense. But even
though it was installed via a domain account, it still runs under
LocalSystem on the local machine, right?
 
Back
Top