Summary

Microsoft Hyper-V provides a reliable platform for hosting a GibbsCAM Network License (NLO) Server when it is configured correctly.

This article outlines recommended practices for deploying and maintaining a GibbsCAM Network License Server in a Hyper-V environment, including virtual machine configuration, networking, hardware key considerations, and maintenance.

TABLE OF CONTENTS

Applies To

Virtualization Platform:

  • Microsoft Hyper-V

Overview

Many organizations use Microsoft Hyper-V to host Windows-based infrastructure, including GibbsCAM Network License Servers.

When configured correctly, Hyper-V provides a stable platform for network licensing. Changes to virtual hardware, networking, or USB device access, however, can affect license activation or client connectivity.

Recommended Virtual Machine Configuration

For the best experience:

  • Install a supported 64-bit version of Windows.

  • Assign a static computer name.

  • Configure a static IP address whenever possible.

  • Install the latest Hyper-V Integration Services (included with current versions of Windows).

  • Keep Windows fully updated.

  • Install the latest supported GibbsCAM Network License (NLO) Server software.

Hardware Key (USB) Licenses

If your Network License uses a USB hardware key:

  • Verify that your Hyper-V environment supports your chosen method of USB device access.

  • Install the appropriate hardware key drivers before registering the license.

  • Confirm that Windows detects the hardware key before starting the GibbsRLMServer service.

Note: Hyper-V does not provide native USB passthrough for virtual machines. If your deployment requires a USB hardware key, you may need a supported USB-over-network or USB redirection solution. Consult your IT department to determine the best approach for your environment.

Keyless Licenses

Keyless Network Licenses are associated with the server configuration.

If you plan to:

  • Create a replacement virtual machine

  • Move the license to another Hyper-V host

  • Rebuild the server

contact CAMCO before making the change so the license can be updated if necessary.

Networking Recommendations

Verify that:

  • Client workstations can resolve the server hostname.

  • The required RLM license server port is accessible.

  • Windows Firewall permits inbound licensing traffic.

  • VPN users can communicate with the license server, if applicable.

Using a static hostname and IP address minimizes future client configuration changes.

Checkpoints (Snapshots)

Hyper-V checkpoints are useful for maintenance and testing but should be used with care.

Before restoring a checkpoint:

  • Ensure current backups of the license files are available.

  • Be aware that restoring an older checkpoint may also restore older licensing or server configuration.

After restoring a checkpoint:

  • Verify that the GibbsRLMServer service is running.

  • Confirm that client workstations can successfully obtain licenses.

Live Migration

Hyper-V Live Migration is generally transparent to GibbsCAM when:

  • Network connectivity is maintained.

  • The server hostname remains unchanged.

  • The virtual machine configuration is not modified during migration.

After a Live Migration:

  • Verify the virtual machine is running normally.

  • Confirm that the license service has started.

  • Test license checkout from one or more client workstations.

Backups

Regularly back up:

  • License files (.lic)

  • Network License configuration files

  • Product Code documentation

  • Server configuration

Maintaining current backups simplifies disaster recovery and server replacement.

Troubleshooting

Problem: Clients Cannot Obtain Licenses

Possible Causes

  • Virtual machine is powered off.

  • GibbsRLMServer service is not running.

  • Firewall rules have changed.

  • Network configuration is incorrect.

Resolution

Verify that the virtual machine is running, confirm that the license service is active, and test connectivity from a client workstation.


Problem: USB Hardware Key Is Not Detected

Possible Causes

  • USB device is not available to the virtual machine.

  • Hardware key drivers are not installed.

  • USB redirection solution is not configured properly.

Resolution

Verify that the hardware key is accessible from within the guest operating system and that the appropriate drivers have been installed.


Problem: License Stops Working After Rebuilding the Virtual Machine

Cause

Keyless licenses are associated with the original server configuration.

Resolution

Contact CAMCO before replacing or rebuilding the virtual machine so your license can be updated if necessary.


Problem: Clients Cannot Connect After Live Migration

Possible Causes

  • Temporary network interruption

  • Firewall or routing changes

  • License service failed to restart

Resolution

Verify network connectivity, ensure the GibbsRLMServer service is running, and test client connectivity using Test-NetConnection.

Best Practices

  • Use a static hostname.

  • Assign a static IP address whenever practical.

  • Keep Windows fully updated.

  • Minimize changes to the virtual hardware configuration.

  • Test client connectivity after Hyper-V maintenance.

  • Maintain regular backups of licensing and configuration files.

  • Document any non-default RLM port assignments.

Expected Result

The GibbsCAM Network License Server operates reliably in a Hyper-V environment, allowing client workstations to obtain licenses before and after routine maintenance.

Related Articles

Keywords

Hyper-V, Microsoft Hyper-V, Virtual Machine, Network License, NLO, RLM, Reprise License Manager, Live Migration, Checkpoint, Virtualization, License Server, Hardware Key, USB Redirection, Keyless License