Why Licensing Has Become Invalidated
There are multiple reasons why a license would break. Doing any of the following makes the software think that the server has
been cloned without permission. If the license breaks, we must sign the license (approve that it is a genuine copy of the
software). There are some basic notes below on resolutions, Knowledge article KB0010420 has more detail and text from that
has been copied to the last page of this document for reference.
1. Microsoft license changed.
• RESOLUTION: Do not change Microsoft Windows license again (unlikely to ever happen)
2. C:\ partition size changed.
• RESOLUTION: Please be aware that changing the C:\ partition size breaks our license. Please plan ahead if you
want to change the partition size again and contact your account manager so that we can be on standby to sign
3. VMAC address changes.
• RESOLUTION: We tie the license to the MAC address of the network card. Please plan ahead if you want to
intentionally change the network card again and contact your account manager so that we can be on standby to
sign the license. Set the VMAC to a Static MAC so that it does not change unless you want the ability to move
VM hosts then see item 5.
4. On reboot the server may change the order of the network cards.
• RESOLUTION: Change the NIC priority on the recorder Windows server and Delete the C:\LTR\
AdditionalNICs.ini file and reboot the recorder to pick the NICs up in the correct order. (This may need the
license signing once more after change)
5. Moving from Virtual Server Host to a different Virtual Server Host.
• RESOLUTION: Changing Virtual Server host also changes MAC address of the network card used and other
settings. Check whether the server is moving host and change the network card type in the VM host to an
emulated card with Windows drivers (the exact type depends on the VM hosting software), rather than a
virtualized card type. Red Hat VirtIO Ethernet Adapter & E1000 Series Adapter are none compatible with RedBox
Procedure For Setting NIC Priority On Server 2016
- Select your NIC and right click and choose properties.
- Select Internet Protocol Version 4 (TCP/IPv4) and choose properties.
- Select Advanced.
- Untick Automatic Metric and add your priority 1, 2, 3, etc.
- Delete the C:\LTR\AdditionalNICs.ini file and reboot the recorder to pick NICs up in the correct order.
Notes from KB0010420
License - Recorder license invalidated,
revoked, expired, or otherwise lost
Recorder's license becomes invalid for any reason. The license must
be reapplied for the Recorder to continue normal operation. For a
more detailed explanation, see: KB0010422.
Fix 1: Check the network adapter types in use. Change if
the physical host that hosts the virtualized Recorder.
management application for the virtualization software in use,
(Hyper-V, Virtual Box, VM Ware).
settings for the virtualized Recorder, identifying the network
adapters installed. The following adapter types are not
compatible with the Recorder software:
incompatible network adapter is identified, it must be changed to a
compatible one, (a non-virtualized card type), such as:
specific adapters available will vary, depending on the
virtualization software in use.
Fix 2: Change the adapter binding order.
the Recorder, open Control Panel and select "Network and
On the left
pane, click on "Change Adapter Settings".
Network Connections Window, click on the drop-down menu "Advanced"
and select "Advanced Settings...". A dialog "Advanced
Settings" will appear.
"Connections:" pane, use the up and down arrows to reorder
the adapters. The adapter at the top of the list becomes the Primary
Recorder for the change to take effect.
Fix 3: If ErrorLog.txt contains "Illegal operation attempted
on a registry key that has been marked for deletion.", change
group policy to resolve.
Domain policy that is applied to the Recorder or continue from step
mmc.exe and add in the "Group Policy Object Editor"
group policy for the local computer.
to: Computer Configuration -> Administrative Templates ->
System -> UserProfiles
setting "Do not forcefully unload the user registry at user
logoff" from “Not Configured” to “Enabled”.
Recorder for the change to take effect.