The following are the minimum system requirements for Network License Manager 23.03. Exceeding these requirements will in most cases lead to a performance increase. Running Network License Manager 23.03 on a system that does not meet these requirements is not supported.
In some cases where an operating system has an active virus scanner or security management system active, installation of software may cause issues. The License Manager installer is signed, notarized and verified with a certified virus scanner.
If there is still a problem on the local customer computer, update or install a certified virus scanner; or stop the virus scanner or de-activate the security management system during the installation, and start it again afterward.
Minimum Requirements
Mac
Minimum System Requirements
Processor type and speed
64 bit Intel processor or Apple Silicon processor.
RAM
2 GB or better.
Network
10/100/1000 Base-T Ethernet, TCP/IP v4 protocol. TCP/IP v6 protocol is not supported.
Windows: multiple Ethernet hostids are supported
Mac: multiple Ethernet hostids are NOT supported
Supported Operating Systems
Recommended operating systems are highlighted in green in the tables below.
If an operating system is not listed in the tables below, it is not supported. Do not try to install Network License Manager on a computer running an unsupported operating system.
Edition
Client OS
13 (Ventura) Intel, Apple Silicon
12 (Monterey) Intel, Apple Silicon
11.1 (Big Sur) Intel, Apple Silicon
10.15 (Catalina)
10.14 (Mojave)
10.13 (High Sierra)
Windows
Minimum System Requirements for Network License Manager 23.03 (Windows)
Processor type and speed
x64 (64-bit) compatible processor (Intel or AMD), minimum dual-core.
RAM
Minimum 2GB.
Network
10/100/1000 Base-T Ethernet, TCP/IP v4 protocol, TCP/IP v6 protocol is not supported in applications.
Virtualization
VMWare Workstation 16.1.0, VMWare ESXi 6.5, 6.7, Citrix 8, Parallels 15.1.2 for Mac 10.15.4, Microsoft Windows 10, 2019 Hyper-V.
In a virtual infrastructure, you must be sure that the VM parameters are fixed and do not change, examples are Unique identifier, Disk size, Memory layout, size, CPU, MAC address. Also, when you duplicate virtual machines, you must be sure these different virtual machines are unique and do not have overlapping parameters like VM unique identifier, MAC address, IP address, computer name.
Supported Operating Systems
Recommended operating systems are highlighted in the tables below.
If an operating system is not listed in the tables below, it is not supported. Do not try to install Network License Manager on a computer running an unsupported operating system.
Windows Server
Windows
Windows Server 2022
Windows Server 2019
Windows server 2016
Windows, 64-bit version
Windows
Windows 11
**
Windows 10
**
** Esko tested on Pro editions. ** Although support, advise running license servers on Windows servers only.
Unsupported Operating Systems
Windows Virtual Desktop, Azure Virtual Desktop
Windows Server 2012 **
Windows Server 2008
Windows Server 2003 (all editions)
Windows 7
Windows 2000 (all editions)
Windows Vista (all editions)
Windows XP (all editions)
** The 23.03 Network License Manager can be installed on Windows Server 2012R2, but support will be dropped soon in next versions.
Unsupported configurations
Installing the Esko Network License Manager on a computer running another vendor software using Flexera (Revenera) Flexnet License Manager is not supported.
Certificate license files (.dat files) are not supported.
The network latency should not exceed 100msec, you can find more info here. Running the Network License Manager in the cloud, whereas your applications are running locally, may severely impact the performance of the application. Therefore, these configurations are not supported.
The name of the computer running the Esko Network License Manager should contain ISO LATIN characters only and should be stable and registered in DNS server (if any).
Make sure that the Network License Manager Software is always updated to the latest compatible version, before installing client software. Running an application of a higher version with a Network License Manager of a lower version will not work.
Before virtualizing an OS, or manipulating a VM, you must first deactivate the existing licenses on the physical hardware machines.
When running on a VM, rebooting or resetting a Windows host should not replace the ethernet MAC address; otherwise licenses will be broken.
When running on a VM, rebooting or resetting a Windows host should not replace the VM unique identifier; otherwise licenses will be broken.
When using VPN network, the VPN must ensure that the MAC addresses do not change across different VPN sessions.
The Network License Manager installer has been tested with the most popular virus scanners. If you observe installation problems related to your virus scanner, you may have to stop the virus scanner, update the virus scanner to the latest version and definitions, and or contact your virus scanner vendor for more information and or an update.