This property is only used when wrapper.ntservice.account property is set and when its value is not one of the built-in accounts (LocalService, NetworkService, LocalSystem). It makes it possible to control whether or not the Wrapper should automatically add the 'Log on as a service' privilege to the configured account. This is done during the installation of the Wrapper as a Windows Service.
If the installation of the service fails for any reason, and the permission was not set before the installation started, the Wrapper will revert any change so that the account doesn't have unnecessary rights until the service is reinstalled correctly.
Possible values for this property are:
to allow the Wrapper to automatically set the permission during installation.
to leave the permission unchanged.
The default value is ALLOW to let the Wrapper do the job of adding the permission. If the property is set to UNCHANGED, the user should manually edit the security policy of the system (see below) as the permission is required for services running with specific accounts.
To set the "Log on as Service" right,
Go to the "Administrative Tools" folder in your control panel.
Open the "Local Security Policy" applet.
Expand "Local Policy" and then click on "User Rights Assignment".
On the right side, you will find a "Log on as service" policy.
Right click or double click to access its properties dialog,
and then add the user that you wish to allow to run the service.
Note that the "Local Security Policy" applet does not appear to be available
on Home Editions of Windows.
Removing Access Right on the system:
The Wrapper doesn't remove the 'Log on as a service' permission when uninstalling a service. This is intentional because other services on the machine might run with the same user, and removing the permission would prevent them from running.
If the account should not have this right anymore, it can be removed by following the same steps as for adding the permission (select the account and click the "Remove" button in properties dialog).
Windows doesn't always refresh the list of users in the dialogs of the Local Security Policy. Closing completely the 'Local Security Policy' window and reopening it will solve the problem.