Plug-ins
DeviceLock Enterprise Manager has a flexible plug-in based architecture that allows you to plug in the necessary module on demand. DeviceLock Enterprise Manager loads the plug-ins on startup from the Plugins folder, located in the main DeviceLock Enterprise Manager directory.
DeviceLock Enterprise Manager ships with standard plug-ins that require some network ports to be opened on remote computers, as described in the table below:
Required ports | Plug-ins affected |
TCP 139 or TCP 445 UDP 137 - This port must be opened only when a connection is established by the computer name. If an IP address is used, this port is not required. | |
TCP 139 or TCP 445 UDP 137 - This port must be opened only when a connection is established by the computer name. If an IP address is used, this port is not required. | |
TCP 139 or TCP 445 TCP 135 - This port is required only when the Dynamic ports connection is used. TCP <all ports above 1024> - These ports are required only when the Dynamic ports connection is used. TCP <custom port> - This port is required only when the Fixed port connection is used. UDP 137 - This port must be opened only when a connection is established by computer name. If an IP address is used, this port is not required. | |
For information on how to use either the
Dynamic ports or
Fixed port connection in DeviceLock Enterprise Manager, see
Setting Port.
When a plug-in is connected to a remote computer it may receive some of these error messages:
•The product version on the client and server machines does not match (7049) - You are trying to connect to a computer where an old version of DeviceLock Service is installed. You should upgrade DeviceLock Service first using the
Install Service plug-in.
•The network path was not found (53) - You are trying to connect to a computer that either does not exist (the wrong name or IP address) or is not accessible. Make sure that the computer name you have specified is correct. Try to access this computer with Windows Explorer and connect to it using any standard Windows administrative tool (such as Computer Management, Services and so on).
This error also occurs when the standard Windows Server service is not running on the remote computer. Check the Server service status and start it if it is stopped.
More connection errors are described in the
Possible connection errors section of this manual.
From a report produced by any plug-in, you can open DeviceLock Management Console connected to DeviceLock Service on a given computer: right-click the computer name, and then click Connect to DeviceLock Service.