Article ID: 288129 - Last Review: October 31, 2006 - Revision: 4.4 How to grant users rights to manage services in Windows 2000This article was previously published under Q288129 On This PageSUMMARY
This article describes several methods for granting users the rights to manage services in Windows 2000.
By default in Windows 2000, only Administrators and Power Users can start, stop, or pause services. This article describes techniques for granting these rights to other users and groups. Method 1: Grant rights using Group PolicyIt is possible to give these rights to users by applying Group Policy. For additional information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:256345
(http://support.microsoft.com/kb/256345/
)
Configuring Group Policies to set security for system services
The article gives detailed step-by step instructions. However, the article does not explicitly state that there are no corresponding settings in Local Group Policy.Method 2: Grant rights using Security templatesThis method is very similar to Method 1, but it uses Security templates to change the permissions on system services. To do this, follow these steps:
It is also possible to export your modified settings from the MMC and apply these to multiple machines using the SECEDIT command-line tool that ships with Windows 2000. For more information on using SECEDIT type the following at the command prompt: secedit /? NOTE: Applying the settings in this way will re-apply all of the settings in the template and so may override other file, registry, or service permissions set by other means.Method 3: Grant rights using Subinacl.exeThe final method for assigning rights to manage services is to use the Subinacl.exe utility from the Windows 2000 Resource Kit. The syntax for this is:
SUBINACL /SERVICE \\MachineName\ServiceName /GRANT=[DomainName\]UserName[=Access]
Notes
Automating Multiple ChangesWith Subinacl there is no option you can specify that will set the required access for all services on a given computer. However, the following sample script demonstrates one way the above method could be extended to automate the task:
strDomain = Wscript.Arguments.Item(0)'domain where computer account is held
strComputer = Wscript.Arguments.Item(1)'computer netbios name
strSecPrinc = Wscript.Arguments.Item(2)'user's login name as in: DomainName\UserName
strAccess = Wscript.Arguments.Item(3)'access granted, as per the list in the KB
'bind to the specified computer
set objTarget = GetObject("WinNT://" & strDomain & "/" & strComputer & ",computer")
'create a shell object. Needed to call subinacl later
set objCMD = CreateObject("Wscript.Shell")
'retrieve a list of services
objTarget.filter = Array("Service")
For each Service in objTarget
'call subinacl to se the permissions
command = "subinacl /service " & Service.name & " /grant=" & strSecPrinc & "=" & strAccess
objCMD.Run command, 0
'report the services that have been changed
Wscript.Echo "User rights changed for " & Service.name & " service"
next
Notes
REFERENCES
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
269875
(http://support.microsoft.com/kb/269875/
)
SVCACLS.EXE is not included with the Windows 2000 resource kits
| Article Translations
|
Back to the top
