General discussion

Locked

Securing Windows services

By chuck.beach ·
Does anyone know of any techniques for restricting which services a logged in person can stop/start?

We're working toward locking down our production servers. One products solution to a frequent printing problem is to stop and start two services.We'd like to give the application support person and a consultant the ability to stop/start the services without opening up other admin functions.

On our drawing board: An app that runs as a service for stopping/starting others services. User would 'request' starting/stopping a service and the app would check authorization in a restricted file or registry entry, and only perform the request if authorized.

Other ideas?

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Securing Windows services

by abubin In reply to Securing Windows services

I am not sure if there is other easier method but here is my suggestion.

Try creating a script/program that checks the user who requested for the authorization. If the user is one of the authorize person (perhaps in a authorize group), just use acommand to stop/start the service with administrator rights.

Collapse -

Securing Windows services

by chuck.beach In reply to Securing Windows services

Poster rated this answer

Collapse -

Securing Windows services

by chuck.beach In reply to Securing Windows services

This question was closed by the author

Back to Windows Forum
3 total posts (Page 1 of 1)  

Related Forums