To use a low-privileged account as the service account for ServiceControl, the following should be considered:
The transport connection string used by ServiceControl must enable access to the following ServicControl queues:
particular.(ServiceControl version 1.6 and above)
In addition, the connection string must enable access to the configured audit and error queues and the corresponding forwarding queues. These are typical:
If the connection string does not provide appropriate rights, the service will fail to start.
The account under which the ServiceControl instance is running requires URL namespace reservations for the hostname and ports used by the instance. The reservations can be managed using the ServiceControl Powershell commands or from the command line using netsh.exe. For example, to add url reservation for
LocalService account the following command can be used
netsh http add urlacl url=http:/.
For instructions on how to review and change the urls used by ServiceControl instance, refer to Changing the ServiceControl URI.
The service account running ServiceControl instance requires following filesystem level access rights:
|Executables (e.g. ||Read|
|Logs (e.g. ||Write|
|Database (e.g ||Write|
|Database volume (e.g. ||Read Attributes|
Read attributesaccess right is needed by ServiceControl to query for total and total free space on the volume.
ServiceControl requires access to Windows performance counter infrastructure. As a result the service account needs to be a member of Performance Monitor Users group.
These methods confirm that the service account has sufficient rights:
- Configure the ServiceControl Windows service to run under the custom service account, start it and check the log files.
- Interactively run ServiceControl under the custom service account.
ServiceControl.exefrom the command line, it is important to use the same command line switches that are used when running the Windows service. The command line is visible from within the standard Windows Services user interface.
- Open Computer Management.
- Change the service account to the custom user, provide the password and apply the change. The account will be given "logon as a service" privilege.
- Start the service and confirm that it started.
- Examine the log file to ensure that the service is operating as expected. If the service does not start and the log file does not indicate the issue, try Method 2.
To run the service this way, the custom service account must have rights to log on interactively on the computer.
- Log on to the computer with admin privileges.
- Switch to the appropriate domain and username.
- Issue the following command, entering the password when prompted:
runas /user:MyDomain\MyTestUser cmd.exe
If the command returns the error below, then the user account cannot be tested this way without adjusting the login rights. Normally this only occurs if the computer is configured as a domain controller or the system administrator has restricted login access using group policies.
1385: Logon failure: the user has not been granted the requested logon type at this computer.
Once login rights are granted:
- Ensure that the service is stopped.
- From the command prompt running as the service account, change to the ServiceControl installation directory and run
--serviceNameparameter. In the following example, the default name has been used. Check ServiceControl Management if unsure of the service name
- Examine the output and confirm that there are no critical errors.
- Shut down the console session.
- Start the service.