About DeviceLock License Types
DeviceLock is licensed on a per-endpoint basis. The license specifies the number of endpoints on which it entitles you to set and enforce DeviceLock policies. From a license perspective, “endpoint” refers to any of the following:
•A laptop, desktop, or server
•A virtual machine
•A virtual desktop or application session
In the latter case, each session is considered a separate endpoint. The number of endpoints in your DeviceLock license should match the number of sessions hosted on your virtualization server. For example, when deploying DeviceLock on Remote Desktop Server, ensure that the number of endpoints in your DeviceLock license matches the number of remote desktop sessions hosted on the server.
As DeviceLock has a number of optional components, there are several license types:
License Type | License File Name |
Core | devicelock.lic |
ContentLock | dlcl.lic |
NetworkLock | dlnl.lic |
UAM (User Activity Monitor) | dluam.lic |
Search Server | dlss.lic |
Discovery Server | dlds.lic |
The Core license is mandatory, the others relate to optional components. To use an optional component, its license must be activated in addition to the Core license. Without the Core license, the other licenses have no effect (except for the Discovery Server license).
If the Core license is missing, corrupt or has expired, then all DeviceLock components (except Discovery Server) operate in trial mode. Discovery Server does not require the Core license.
The number of ContentLock, NetworkLock and/or UAM licenses must match the number of Core licenses; otherwise, the respective components are deemed not licensed.
Example
Suppose you have the following number of licenses activated on a computer running DeviceLock Management Console:
Core - 1,000; ContentLock - 1,000; NetworkLock - 1,000; UAM - 1,000.
Then, you activate 100 additional Core licenses on that computer, so the total number of Core licenses exceeds the number of ContentLock, NetworkLock, and UAM licenses:
Core - 1,100; ContentLock - 1,000; NetworkLock - 1,000; UAM - 1,000.
As a result, ContentLock, NetworkLock, and UAM switch into trial mode, so these components are no longer available for configuration and use.
The issue in this example can be resolved by activating 100 additional ContentLock, NetworkLock, and UAM licenses on the DeviceLock Management Console computer where 1,100 Core licenses are activated. Another option is to remove the 100 Core licenses from that computer and activate them on a different computer running the DeviceLock Management Console that has no ContentLock, NetworkLock, and UAM licenses. This DeviceLock Management Console will be able to control 100 computers, but without ContentLock, NetworkLock, and UAM features.