Installing DeviceLock : Installing DeviceLock Content Security Server : Perform Configuration and Complete Installation : Service account and connection settings : Starting the Service
  
Starting the Service
If the current user does not have full administrative access to DeviceLock Content Security Server (in case it already exists and you’re installing an upgrade), the configuration wizard will not be able to install the service and apply changes. The following message will appear: “Access is denied.” Also, a similar error may occur when the current user does not have local administrative privileges on the computer where DeviceLock Content Security Server is installing.
If you have specified an incorrect user name for the This account option or the wrong user password, DeviceLock Content Security Server will not be able to start. The following message will appear: “The account name is invalid or does not exist, or the password is invalid for the account name specified.”
You will be notified if the user’s account specified for the This account option is not a member of the Domain Admins group. The following message will appear: “The account <name> does not belong to the Domain Admins group. Do you want to continue?”
You may continue by clicking Yes. However, make sure that either of the following is true.
For Search Server:
The specified user has administrative access to all remotely running DeviceLock Enterprise Servers
- OR -
DeviceLock Certificate (private key) is installed on every computer running DeviceLock Enterprise Server
For DeviceLock Discovery Server:
The specified user has administrative access to all computers scanned by DeviceLock Discovery Server. This includes computers running DeviceLock Services, DeviceLock Discovery Agents, as well as any computers not having the Agent installed.
- OR -
DeviceLock Certificate (public key) is installed on every computer (with DeviceLock Service) scanned by DeviceLock Discovery Server
- OR -
Credentials for accessing remote computers are specified in the scanning settings.
If the user’s account specified for the This account option does not have the “Log On As A Service” system privilege, the wizard automatically assigns it. This privilege is needed to start the service on behalf of the user. The following message will appear: “The account <name> has been granted the Log On As A Service right.”
If all of the service’s startup parameters were specified correctly, the wizard starts DeviceLock Content Security Server. The following message will appear: “Please wait while the program is interacting with a service. Starting service DLCSS on Local Computer…”
It takes some time (up to a minute) before the DeviceLock Content Security Server service is started and the next page of the wizard is displayed.