NetKey License Server

NetKey License Server (NKLS) is a service application for the network licensing solution. Through the IP network, the NKLS allows the application on the clients to access a pool of network licenses on a centralized server. The solution supports both floating licenses and roaming licenses. With floating licenses, the NKLS functions to allocate available licenses from the pool, allowing concurrent users within the network to use the application. With roaming licenses, the NKLS functions to administer licenses, allowing the user to check out (or borrow) a license from the pool and temporarily use the application while disconnected from the network. The NKLS is typically deployed to a customer site as a local license server, which can be on an intranet, a virtual private network, or the Internet. It also supports network licenses for the application running on a Windows or Citrix Terminal Server.


Besides the main functions, the NKLS includes several license management features. The NKLS supports fault tolerance, up to 4 redundant servers. The NKLS provides user authorization that can allow the clients based on physical (MAC) address, IP address, and NAT IP address. The NKLS monitors and displays the active clients running the application with the details, including username, IP address, start time, usage duration, etc. The NKLS saves the activity and connection information to the history log for 7 days.


NetKey License Server (NKLS) is a TCP/IP based service application for the network licensing solution. The NKLS can be installed on a Windows server (or computer), intended as a centralized license server for the clients running the application. In addition, the server must have the Network Key installed, which can be on the hard drive (Machine License) or the USB dongle (USB License) attached to the server. The NKLS provides the communication via the IP network, allowing the application running on the clients to connect and access the network license on the server. With the max-user property defined in the Network Key, the NKLS also functions to manage a pool of network licenses and administer available licenses to the clients. The NKLS provides the network licensing support for both floating licenses and roaming licenses.

Floating License

Floating licenses are also known as concurrent licenses. The NKLS functions to allocate available network licenses from the pool to the clients. In this approach, the application does not need a license on the local machine. Instead, when a client runs the application, it requests a network license on-demand automatically from the NKLS. Hence, the network licenses can be floating within the network. They can be shared among a larger number of users, but not more than the maximum number of concurrent users allowed. While the application is running, it periodically connects to the NKLS (e.g. every 20 seconds) in background process to maintain its active license. In case the connection is lost, the license will be released and the application will terminate itself. Similarly, closing the application will release the license and make it available for other users.

Roaming License

With floating licenses, the clients must be within the network accessing to the NKLS in order to maintain the activate license. Roaming licenses provide greater flexibility and convenience, allowing the user to check out a license from the pool, disconnect from the network, and temporarily use the application off-site (e.g. for 15 days). Using the provided Roam utility, the user can check out (or borrow) a license from and return it to the NKLS. The NKLS functions to administer the roaming licenses, which are deducted from the pool of available network licenses. At the end of the borrowing period, the roaming license is automatically returned to the pool, even if the user is still disconnected from the NKLS. During the borrowing period, if the user runs the application and has access to the NKLS, the roaming license is restarted automatically. In other words, a new borrowing period is extended. This helps to facilitate commuter users who often use the application between on/off-site, home/office, etc. So they donít need to check out the license frequently


See Also

         NKLS Command Usage

         NKLS Graphical User Interface