Summary

VMware 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 VMware environment, including hardware key considerations, virtual machine configuration, networking, and maintenance.

TABLE OF CONTENTS

Applies To

Virtualization Platform:

  • VMware ESXi

  • VMware vSphere

  • VMware Workstation (testing only)

Overview

Many organizations deploy their GibbsCAM Network License Server as a VMware virtual machine.

When properly configured, VMware environments generally provide reliable license server operation. However, changes to virtual hardware, networking, or USB device mapping can affect licensing.

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 VMware Tools.

  • Keep Windows fully updated.

  • Install the latest supported GibbsCAM Network License Server software.

Hardware Key (USB) Licenses

If your Network License uses a USB hardware key:

  • Verify that the VMware environment supports USB passthrough or USB device redirection.

  • Connect the USB hardware key directly to the virtual machine.

  • Confirm that Windows detects the hardware key.

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

If the hardware key is disconnected or unavailable, the Network License Server cannot issue licenses.

Keyless Licenses

Keyless Network Licenses are associated with the server configuration.

If you plan to:

  • Create a replacement VM

  • Move the license to different hardware

  • Build a new VMware 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.

  • Firewalls permit client communication.

  • VPN users can reach the server if working remotely.

Use a static hostname whenever possible so client configuration does not need to change if the server IP address changes.

VMware Snapshots

Snapshots are useful for maintenance but should be used carefully.

Before restoring a snapshot:

  • Confirm you have current backups of the license files.

  • Understand that restoring older snapshots may also restore older licensing information or server configuration.

After restoring a snapshot:

  • Verify that the GibbsRLMServer service is running.

  • Confirm clients can obtain licenses.

VMware vMotion and Live Migration

If your VMware environment uses live migration technologies such as VMware vMotion:

  • Verify that the virtual machine remains accessible after migration.

  • Confirm that the server hostname and network connectivity remain unchanged.

  • If using a USB hardware key, ensure the key remains available to the virtual machine throughout the migration.

After migration, test license checkout from a client workstation.

Backups

Regularly back up:

  • License files (.lic)

  • Server configuration files

  • Product Code documentation

  • Network License configuration

These backups simplify disaster recovery if the virtual machine must be rebuilt.

Troubleshooting

Problem: Clients Cannot Obtain Licenses

Possible Causes

  • VMware virtual machine is powered off.

  • GibbsRLMServer service is stopped.

  • Firewall rules have changed.

  • Network configuration has changed.

Resolution

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


Problem: USB Hardware Key Is Not Detected

Possible Causes

  • USB passthrough is not configured.

  • Hardware key drivers are not installed.

  • USB device is connected to the VMware host instead of the guest operating system.

Resolution

Reconnect the USB hardware key to the virtual machine and verify that Windows detects it correctly before starting the license service.


Problem: License Stops Working After Rebuilding the VM

Cause

Keyless licenses are associated with the original server configuration.

Resolution

Contact CAMCO for assistance updating the license before activating the replacement server.


Problem: Clients Lose Access After vMotion

Possible Causes

  • Temporary network interruption

  • DNS update delay

  • Firewall or routing changes

Resolution

Verify network connectivity, confirm the server is reachable, and restart the GibbsRLMServer service if necessary.

Best Practices

  • Use a static hostname.

  • Assign a static IP address whenever practical.

  • Install VMware Tools.

  • Keep VMware Tools and Windows updated.

  • Avoid unnecessary changes to virtual hardware.

  • Test client connectivity after VMware maintenance.

  • Keep regular backups of the license and configuration files.

Expected Result

The GibbsCAM Network License Server operates reliably in a VMware environment, and client workstations can successfully obtain licenses before and after routine VMware maintenance.

Related Articles

Keywords

VMware, VMware ESXi, VMware vSphere, VMware Workstation, Virtual Machine, Network License, NLO, RLM, License Server, USB Passthrough, vMotion, Virtualization, Hardware Key, Keyless License