Skip to main content

Machine ID Incorrect for License Server on a Windows Failover Cluster node


QAID # 16220 Published

Question / Problem:

Why can't I see the correct license machine id on a Windows Failover Cluster node?

Answer / Solution:

Kofax License Utility makes a local connection on pc by binding to the first network adapter and then use the MAC address of that adapter for the machine ID. A Windows Failover Cluster installs a "Microsoft Failover Cluster Virtual Adapter" and sets it by default to its first connection listed in the binding order.

The solution consists in reordering the binding order so that the primary NIC is listed as the first connection. This is usually made feasible by editing the binding order in the Advanced Settings of the "Network Connections" but for some reason, the cluster's virtual adapter is hidden from this list.

The solution is to use nvspbind utility available from the Microsoft MSDN site at and to proceed as following:

  1. Download and unpack the utility on a temporary folder
  2. Open a command prompt
  3. Identify the adapter name that is the Microsoft Failover Cluster Virtual Adapter by using the nvspbind /n command. Usually it is listed as "Local area connection* 9"
  4. Use the "nvspbind /o ms_tcpip" to determine the binding order for IPv4. You will see that the adapter listed at the top of the binding order for IPv4 is the "Local area connection* 9"
  5. Move the adapter down in the binding order with the command "C:\nvspbind /- "local area connection* 9" ms_tcpip" (considering that "local area connection* 9" is the Virtual Adapter)
  6. Open the license utility and see that the machine ID is now showing the network address in the first binding order

Those steps need to be repeated on the second cluster node if it will be used as the backup license server.

Applies to:

Product  Version