Summary

Microsoft Azure Virtual Machines (VMs) can be used to host a GibbsCAM Network License (NLO) Server when configured correctly.

This article provides best practices for deploying, maintaining, and troubleshooting a GibbsCAM Network License Server in a Microsoft Azure environment.

TABLE OF CONTENTS

Applies To

Cloud Platform:

  • Microsoft Azure Virtual Machines

Overview

Microsoft Azure provides a flexible platform for hosting Windows-based applications, including the GibbsCAM Network License (NLO) Server.

To ensure reliable licensing, the Azure virtual machine should be configured with stable networking, appropriate firewall rules, and a consistent server identity.

Recommended Azure Configuration

For the best experience:

  • Deploy a supported 64-bit version of Windows Server or Windows Professional.

  • Assign a consistent computer name.

  • Configure a static private IP address within the Azure Virtual Network.

  • Keep Windows updated.

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

  • Back up the VM and license files regularly.

Hardware Key (USB) Licenses

If your Network License uses a USB hardware key:

  • Verify that your Azure deployment supports your chosen USB-over-IP or USB redirection solution.

  • Install the appropriate hardware key drivers.

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

Note: Microsoft Azure does not provide native USB passthrough to virtual machines. If your licensing requires a USB hardware key, you will need a supported USB redirection solution or consider using a keyless Network License.

Keyless Licenses

Keyless Network Licenses are associated with the server configuration.

If the Azure VM is:

  • Recreated

  • Redeployed

  • Replaced

  • Migrated to a new VM

the license may need to be updated.

Contact CAMCO before making significant changes to your Azure deployment.

Networking Requirements

Client workstations must be able to communicate with the Azure VM over the configured RLM license server port.

Verify that:

  • Azure Network Security Groups (NSGs) permit the required inbound and outbound traffic.

  • Windows Defender Firewall allows the RLM license service.

  • VPN or Azure ExpressRoute connectivity is functioning if users are connecting from an on-premises network.

  • DNS correctly resolves the server hostname.

Avoid exposing the license server directly to the public Internet unless your organization's security policies specifically require it.

Public vs. Private Access

For most organizations, the recommended configuration is:

  • Host the license server on a private Azure Virtual Network.

  • Allow access only through a secure VPN or ExpressRoute connection.

  • Restrict access using Azure Network Security Groups and Windows Firewall.

This approach improves both security and reliability.

Maintenance

When performing Azure maintenance:

  • Avoid unnecessary changes to the VM hardware profile.

  • Verify the GibbsRLMServer service after planned maintenance.

  • Test license checkout from a client workstation after updates.

  • Document any custom RLM port assignments.

Backup and Recovery

Regularly back up:

  • License files (.lic)

  • Product Code documentation

  • Network License configuration

  • Azure VM configuration

Before restoring a backup or creating a replacement VM, understand that licensing tied to the original VM may require updating.

Troubleshooting

Problem: Clients Cannot Obtain Licenses

Possible Causes

  • VPN disconnected

  • Azure Network Security Group blocking traffic

  • Windows Firewall blocking the RLM service

  • Incorrect server hostname or IP address

Resolution

Verify network connectivity and test communication using Test-NetConnection from a client workstation.


Problem: License Stops Working After Redeploying the Azure VM

Cause

Keyless licenses are associated with the original server configuration.

Resolution

Contact CAMCO for assistance updating the license if the server has been redeployed or replaced.


Problem: Hardware Key Is Not Detected

Possible Causes

  • USB-over-IP solution is not configured

  • Hardware key drivers are missing

  • USB device is unavailable to the VM

Resolution

Verify the USB redirection solution and confirm that Windows recognizes the hardware key before starting the license server.


Problem: Remote Users Cannot Obtain Licenses

Possible Causes

  • VPN unavailable

  • Azure firewall rules

  • DNS resolution failure

  • Incorrect RLM port configuration

Resolution

Verify VPN connectivity, Azure Network Security Groups, Windows Firewall settings, and DNS resolution before troubleshooting the license server itself.

Best Practices

  • Use a static hostname.

  • Assign a static private IP address.

  • Restrict access to trusted networks.

  • Keep Windows and the NLO Server software current.

  • Test client connectivity after Azure maintenance.

  • Back up licensing and configuration files regularly.

  • Document all custom networking and firewall configurations.

Expected Result

The GibbsCAM Network License Server operates reliably in Microsoft Azure, allowing authorized client workstations to obtain licenses securely over the network.

Related Articles

Keywords

Microsoft Azure, Azure VM, Azure Virtual Machine, Cloud Server, Network License, NLO, RLM, Reprise License Manager, VPN, ExpressRoute, Azure Network Security Group, NSG, Windows Firewall, Keyless License, Hardware Key, USB-over-IP, Cloud Licensing