Re: How do I restrict access from starting/stopping services?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Then you need to change your design to gracefully shut down your services
even if they're stopped by the control applet. The service itself should
store state data, not an application that starts/stops them.

"nickdu" <nicknospamdu@xxxxxxxxxxxxxxxx> wrote in message
news:8FDA0A7C-FC36-4684-8EE2-998D905AAE37@xxxxxxxxxxxxxxxx
Not sure if this is the correct alias for this question.

I would like to be able to restrict an account from starting and stopping
services though I still would like this account to be able to connect to
the
$ shares (c$, d$, etc). Is there a way to do this?

What has happened recently is that we moved to a clustered environment and
sometimes the support people still stop/start our application services via
the services applet as opposed to bringing them offline/online via the
cluster service. Since our services make use of registry keys to store
state
we have them setup for registry replication in the cluster. So when they
get
stopped or started outside of the cluster service bad things happen.
--
Thanks,
Nick

nicknospamdu@xxxxxxxxxxxxxxxx
remove "nospam" change community. to msn.com


.