Re: Access to stop/start services.

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

net stop "Full service name goes here"
net start "full service name oes here"

do in notpead, and save as a .bat file.


"Lars Petersson" <FlpeterssonA@xxxxxxxxxxxxx> wrote in message
news:3998DEC7-13A1-4520-B2BA-2B645D2694D4@xxxxxxxxxxxxxxxx
That is a fantastic idea!!!

I would love to see an example of a the command file you would use for
this.

--
Cheerio,
Lars Petersson
MCSA: Messaging


"Paul AOL" wrote:

One way I've used is to create a scheduled task on the server that looks
in
a folder that the user has access to for the presence of specific files
(e.g. start.txt, stop.txt, and restart.txt). The user creates the
appropriate file in the folder that the scheduled task looks in. The
scheduled task runs a command file that then starts/stops/restarts the
service if any of the three files exist in the folder.

If the task runs every 5 minutes (or faster), then at most the user has
to
wait 5 minutes for the start/stop/restart. You can also create three
shortcuts for the user that create the correct files in the appropriate
directory. Once the scheduled task does the start/stop/restart it
deletes
the file. The next time the user needs to have the service
start/stop/restart they just run the appropriate shortcut again.

I can post the shortcuts and command file if desired.

Paul

"Lars Petersson" <FlpeterssonA@xxxxxxxxxxxxx> wrote in message
news:3A20446F-E88C-407D-8132-063C5D628C1C@xxxxxxxxxxxxxxxx
Thanks for that :)

I can see from the time that you had probably already started typing
when
I
posted about that solution.

But thanks again, it's certainly one to bear in mind...
--
Cheerio,
Lars Petersson
MCSA: Messaging


"David" wrote:

This should help, let me know if you are able to follow this:

In order to Start, Stop, and Pause a service, users need the following
permissions:

Read

Stop, Start, and Pause

These permissions are only exposed in Group Policy.

You can create OUs that contain the workstations that you want the
policy
applied to.

To assign service permissions to the computers in an OU:

01. Open the Active Directory Users and Computers snap-in.

02. Right-click a domain and press New and Organizational Unit.

03. Name the OU and press OK.

04. Right-click this new OU and press Properties.

05. Select the Group Policy tab.

06. Press New and name the policy.

07. Highlight the new policy and press Edit.

08. Navigate to Computer Configuration / Windows Settings / Security
Settings /System Services.

09. Double-click the service you want users to manage.

10. Check the Define this Policy Setting box.

11. Remove the Everyone group.

12. Add the System account, Domain Admins and any user or groups you
desire.

13. Grant the System account and Domain Admins Full Control. Grant the
other
users and groups both Read and Stop, Start, and Pause permissions.

14. Press OK.

15. Change the startup mode from Disabled to Automatic or Manual.

16. Press Apply and OK.

17. Close the policy and press OK.

18. Move the computer accounts that you want effected into the OU.

Thanks

David Whicker, MCSE

"Lars Petersson" wrote:

I have a user that needs to be able to stop and start a particular
service on
a 2003 Server.
He can log on to the server using MSTSC but doesn't have Admin or
power
user
rights.

Ideally I'd like him to be able to just stop/start this one service
(Which
runs under a network service account) but if he has to have access
to
all of
them, so be it...

Is there a way to achieve this without giving the user admin rights?
I'm currently looking at SC.EXE
(http://technet2.microsoft.com/WindowsServer/en/library/0a658e97-51d5-4109-b461-a474c799964e1033.mspx?mfr=true)
but it doesn't look promising...
--
Cheerio,
Lars Petersson
MCSA: Messaging





.

Relevant Pages

  • Re: Active directory Group Policy (Win2k)
    ... When I enforce the policy onto the computers in the new OU, ... Domain Admins so the Domain Admins cannot view ... workstations, to access Microsoft Office. ...
    (microsoft.public.security)
  • RE: Access to stop/start services.
    ... These permissions are only exposed in Group Policy. ... Add the System account, Domain Admins and any user or groups you desire. ...
    (microsoft.public.windows.server.general)
  • Re: Group Policy not updating on Win2K Pro desktop
    ... Run gpresult or rsop on the client to see if the policy is applied. ... the past there was a policy set that allowed only domain admins to ... it has been working OK for most Win2K computers and all XP computers. ...
    (microsoft.public.win2000.group_policy)
  • Re: Reinstall everytime assigned applications through GPO on start
    ... Software installation extension has been called for background policy refresh ... Stations - R&D Software (EMEA computers). ... Stations - R&D Software (EMEA computers) is set for installation because it ... The assignment of application Remote Administrator v2.1 from policy Software ...
    (microsoft.public.windows.group_policy)
  • Re: better way to limit users/group to logon to specific workstati
    ... You can still do it in policy, ... logon locally setting, and apply it to all computers except the ones you ... Workstations" attribute - applying to the user accounts ...
    (microsoft.public.windows.group_policy)