Setting Up a Virtualized DS License Server Failover Cluster Using Hyper-V on Windows Server

The Hyper-V role in Windows Server lets you create a virtualized computing environment where you can create and manage virtual machines. It can be used to create and run a virtualized DS License Server.

This task shows you how to:

Before you begin: Note the following prerequisites:
  • a DS License Server running in a virtualized environment must be a failover cluster: three virtual machines (VMs) able to communicate together are then required. We strongly recommend that the three VMs be hosted by three different physical machines.
  • the only supported operating system for generating the virtual machine is Windows Server, on which the Hyper-V role has to be added and a TPM 2.0 activated
  • the only supported operating system for running the VM is also Windows Server, on which there must be a Virtual Trusted Platform Module; the VM must be Generation 2.
Note: The Computer ID format generated for VMs is longer than the one generated in physical environments, which is shorter. For more details about both formats, see DSLicTarget Command. However, when using the client-side Local Key Manager, the Nodelock Key Manager (DSLicMgt) or Tools > Options > Licensing tools, only the short format is displayed, even if running in a VM.

Prepare the Hardware

On a physical machine running Windows Server, ensure that there is a Trusted Platform Module (TPM) 2.0, then activate the TPM in the UEFI.

  1. Activate the TPM by running the Trusted Platform Module (TPM) Management tool using the tpm.msc command in a command prompt. Select the Action > Initialize the TPM... command. If the TPM status is not ready in the Trusted Platform Module (TPM) Management tool, prepare the TPM by selecting the Action > Prepare the TPM... command.
  2. Run the Device Manager and click Security Devices to check that the TPM level is correct. It should display: Trusted Platform Module 2.0.

Add the Hyper-V Role and Create the Virtual Machines

Configure the physical machine running Windows Server by adding the Hyper-V role which lets you create a virtualized computing environment where you can create and manage virtual machines. The only supported operating system for the VM is Windows Server.

  1. Configure the physical machine running Windows Server by adding the Hyper-V role.

    You add the role using the Server Manager tool in Windows Server.

  2. On the physical machine, create a VM using the Hyper-V Manager.

    When creating the VM, in the Hyper-V Manager tool, from the New Virtual Machine Wizard, click Specify Generation and click Generation 2.

  3. Still using the Hyper-V Manager, after creating the VM, enable TPM mode.

    In the Hardware - Security section, click Enable Trusted Platform Module.

  4. Disable checkpoints the VM by clearing the Enable checkpoints check box.
  5. Create two more VMs the same way.

You can now install a DS License Server in each VM and configure the failover cluster as explained in Configuring and Activating a Cluster in Failover Mode.

When installing the license server on Windows, run the SetupDSLSmsi.exe file: do not double-click the DSLS.msi file.

Note: Each VM can optionally be shielded, and managed by a Host Guardian Server.

Operate the VMs

Certain operations can safely be performed on each VM using the Hyper-V Manager, but others are not supported because they change the ComputerID, which in turn invalidates the license keys. Like for physical machines, backup/restore are not supported.

  1. You can perform the following operation (which do not change the ComputerID):

    • Turn Off (then Start) VM
    • Shutdown (then Start) VM
    • Save (then Start) VM
    • Pause (then Resume) VM
    • Reset VM
    • Move VM, including Live Migration
    • Rename VM.
    Note: Export VM is supported, but is not useful since Import VM is not supported.

  2. Do not perform the following operations (which do change the ComputerID):

    • Import
    • Replication
    • Checkpoint (ensure checkpoints have been disabled).

Offline Licensing Restrictions

Generally, any V5/V6/3DEXPERIENCE DSLS licensing client works the same way when connected to a DS License Server running in a VM, but there are restrictions concerning offline licensing.

In particular, when running a licensing client in a virtual machine, it is still not possible to extract an offline license. There is no difference if the license server itself is running in a virtual machine or a physical machine.

And it is still not possible to get nodelock licenses to work in a VM.

The following table summarizes the different cases (green = supported; red = not supported):

Limitations

The following list summarizes limitations:

  • When the DS License Server runs as a service in a physical machine, the account used is Network Service. However, when running in a VM, the account used by the Windows service is Local System.
  • Standalone license server is not supported
  • Nodelock licenses are not supported
  • Windows versions lower than Windows Server 2016 are not supported
  • Linux is not supported
  • VMWare and other hypervisors are not supported
  • Microsoft Azure is not supported. This is because the Hyper-V implementation in Azure is different from its implementation on physical computers.
  • Nested VMs are not supported: the VM in which the license server runs must be hosted by a physical machine, and not by another VM.