The ODDC Server license is strictly binding to the host computer on which it was activated and on which it runs, via a unique hardware identifier.
The hardware identification verification process is intentionally strict, but not extremely sensitive (not inflexible).
Upon initial activation, the license is bound to a specific machine and can only be reactivated if the primary hardware identifiers of the machine remain unchanged.
The ODDC Server license manager does not base its decisions on a single piece of data; rather, it generates a fingerprint value from multiple stable identifiers.
These identifiers include system UUID, BIOS serial number, motherboard serial number, CPU identifier, Windows Product ID.
Disk identifiers and MAC addresses are less stable elements and supplementary pieces of information with lower weight. Changes to these do not necessarily indicate a new machine from a license management perspective.
🟢The following changes are not expected to cause license issues: RAM expansion or replacement; hard drive or SSD replacement or adding a new drive; network card replacement; change in MAC address; changing the machine name; Windows updates; driver updates; minor maintenance procedures.
🔴The following changes will likely require a new license request or reactivation: motherboard replacement; BIOS/firmware modifications that change the machine identifiers; CPU replacement if the identifier changes; Windows reinstallation if the Windows Product ID changes; transferring the license to another physical server; create a new virtual machine to replace the old one; VM cloning or migration if the UUID, BIOS, or CPU identifiers change during the process.