Start Stop service rights to non administrators


LIke any other object in the Windows world, services are objects, you can therefore give users rights on them. Let’s see for example how to allow start stop service rights to non-administrators.

In order to change the permissions to a service, you’ll need an account who has rights to change permissions on that service obviously. This means being local administrator of the box or already having that “Full control” right on the service.
You’ll also need to retrieve the SID of the users or groups you want grant access.
There are a few ways to achieve this. You could use a runas command to launch a “whoami /all” command for example. For a domain user, you can use a simple “Get-ADUser” / “Get-ADGroup” cmdlet

You also need the short name of the service. In the full example below, I’ll take “Windows Update” service. To retrieve its short name, I can use either

or in Powershell

Once we get that short name also called «keyname » (Because it is the name of the key in the registry under which the parameters for the service are stored), we can dump its current security settings. Since we can easily mess up, we’ll save the current settings for future retrieval. In order to accomplish this, you do:

And you’ll get something as ugly as:

This is a security descriptor in SDDL format which is stored in the Security value of the Security registry key under the keyname in HKLM\CurrentControlSet\Services.

Let’s split in parts:

The <Something> after the D: is what we are interested in, these are the security permissions.
The <SomethingElse> after the S: are the audit permissions, we are not interested in here. Notice how letters are counter intuitive
After the D:, you’ve got a set of blocks between parenthesis. Each represent a security right and must be read as follows:
The first letter is A for Allow or D for Deny (you remember we can deny people, don’t you?)
The second part after the 2 semicolons is the permission set and the letters depend on the object you’re working on. You must read them by pair.
For a service, you’ve got:

  • CC – SERVICE_QUERY_CONFIG – read the configuration of the service
  • LC – SERVICE_QUERY_STATUS – read the status of the service from the Service Control Manager
  • SW – SERVICE_ENUMERATE_DEPENDENTS – list dependencies
  • LO – SERVICE_INTERROGATE – ask the service its current status
  • CR – SERVICE_USER_DEFINED_CONTROL – send a service control command which only make sense service by service (like the custom attributes for an Exchange object for example)
  • RC – READ_CONTROL – read the security permissions
  • RP – SERVICE_START – start the service
  • WP – SERVICE_STOP – stop the service
  • DT – SERVICE_PAUSE_CONTINUE – pause / continue the service

The last part, just before the end parenthesis is the user or group the permission applies to. As we have the default set of permissions here, we only have “well-known“ groups which may be abbreviated by 2 letters (Otherwise you would have for each domain to know the full SID even the RID wouldn’t change)
Often you’ll encounter

  • SY – System
  • BA – Administrators (think “Built-in administrators”)
  • DA – Domain administrators
  • DU – Domain Users
  • AU – Authenticated Users
  • WD – Everyone (sounds like ‘World’, unix roots of the NT native subsystem)

So we can now build the security descriptor to add to grant the start and stop rights we want:

  • my user SID is S-1-5-21-1111111111-4444444444-2000000000-1158
  • Grant means A
  • Start and Stop are RP and WP respectively
  • Therefore our part of the SDDL will be: (A;;RPWP;;S-1-5-21-1111111111-4444444444-2000000000-1158)

Since we don’t want to remove permissions for other users we must reassemble the full string:

Do not forget we must put this in the “D:” part of the SDDL!
Once we’ve built that string, we can use

The return should be

You may get errors such as

In that case, check you have a valid SID and there is no space in all the string.

You can now check that your regular user can issue command like ‘sc start wuauserv’ or ‘sc stop wuauserv’

You can also verify that the registry value “Security” under HKLM\CurrentControlSet\Services\wuauserv\Security had its contents changed.
Once you’ve made the change on a server, you can replicate the setting to other machines using your preferred method (script, GPP, …)

Leave a comment

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.