Deploying a Standalone License Server

Installing the License Server

The ProfileUnity host includes a dedicated license server which endpoint devices with the ProfileUnity client installed can report to. Typically, the ProfileUnity host has direct communication with client endpoints within an internal network but there are instances where this communication is not possible, such as client endpoints that reside outside of the internal network and connect over a VPN within a secure DMZ.

To allow for communication between separated hosts and client endpoints, an installer for a standalone license server is included within the ProfileUnity install directory on the host server. Follow the steps below to deploy a standalone license server:

  1. Locate the ProfileUnity_LicenseServer_Setup.exe installer within the ProfileUnity installation directory on the host server.
  2. Copy it to a new or existing server that has both external and internal communication capability.
  3. Launch the installer and follow the prompts to proceed through the setup.
  4. The license server communicates over port 443 by default but can be changed to use an alternate port.

  5. Note: If a port other than 443 is defined, the license server port on the ProfileUnity host(s) must be updated as well.

  6. Note: To update the port on the host(s), edit the associated port value in ProfileUnity.LicenseServer.exe.xml within the Licence Server subdirectory of the ProfileUnity install directory and restart the License Server service.

  7. When directed to provide the Mongo connection string, follow the steps below the text input field to retrieve the encrypted connection string from the ProfileUnity console.
  8. Complete the installation process.
  9. Using the Certificate snap-in via MS Management Console on the Liquidware ProfileUnity License Server, export the local machine License Server certificate and private key (mark as exportable).
  10. Using the Certificate snap-in via MS Management Console on the ProfileUnity host, export the local machine ProfileUnity-Mongo certificate and private key (mark as exportable).

  11. Note: If clustered, do the same on the remaining nodes.

  12. Using the Certificate snap-in via MS Management Console on the ProfileUnity host, export the local machine Liquidware ProfileUnity License Server certificate and private key (mark as exportable).

  13. Note: If clustered, do the same on the remaining nodes.

  14. Using the Certificate snap-in via MS Management Console on the ProfileUnity host, import the exported Liquidware ProfileUnity License Server cert into the local machine Trusted Root CA store.

  15. Note: If clustered, do the same on the remaining nodes.

  16. Using the Certificate snap-in via MS Management Console on the Liquidware ProfileUnity License Server, import the exported ProfileUnity-Mongo certificates into local machine Trusted Root CA store.
  17. Restart the MongoDB service on the ProfileUnity host(s).