Installing DeviceLock : Deploying DeviceLock Service for Windows : Installation via DeviceLock Management Console
  
Installation via DeviceLock Management Console
DeviceLock Management Console (the MMC snap-in) supports remote installation to help system administrators set up a service on remote machines without ever having to physically go to them.
 
Note: Only the built-in administrator account can be used to perform a remote installation of DeviceLock Service on computers running Windows Vista or a later version of Windows. In a Windows Active Directory environment, only members of the Domain Admins group can perform a remote installation of DeviceLock Service. Administrator privileges are required to connect to DeviceLock Service via DeviceLock Management Console. For more information, refer to Microsoft’s article at support.microsoft.com/kb/951016.
When you’re trying to connect to a computer where DeviceLock Service is not installed or is outdated, the management console prompts you to install or update it. The following message appears: “Device Lock service does not exist on <computer name> Do you want to install it?”
Select the folder that contains all of the files needed for installation (such as DeviceLock Service.msi, DeviceLock Service x64.msi, DLRemoteInstaller.exe, and InstMsiW.exe). These files are located in the DeviceLock installation folder (%ProgramFiles%\DeviceLock by default).
By default, the DeviceLock Service installation files will be copied to the folder %ProgramFiles%\DeviceLock Agent if this service doesn’t exist on this system. If the service exists on the system but its version is lower than 7.0, the management console will also copy the installation files to the default folder %ProgramFiles%\DeviceLock Agent. If the service exists on the system but its version is 7.0 or higher, the management console will copy the installation files to the folder containing the old files and the old files will be replaced.