During a hardware-refresh project, a systems administrator exports a bare-metal Windows Server image and restores it to a brand-new rack-mount host that has a different CPU and NIC. The line-of-business reporting application installed on the server is licensed with a node-locked model. Which outcome should the administrator expect immediately after the restored system is powered on?
The application will function normally because its license information is stored within the operating-system image.
The application will fail its license check and require the vendor to re-host or reactivate the license on the new hardware.
The application will run only if the number of CPU cores in the new server does not exceed the entitlement purchased.
The application will continue to run but will restrict execution to a single concurrent user.
Node-locked licensing binds the activation key to a unique hardware fingerprint-typically the MAC address, CPU ID, or another device identifier-of the original machine. When the image is moved to different hardware, that fingerprint no longer matches, so the application's license check will fail and the software will not start until the vendor re-hosts or re-activates the license for the new device. Concurrent-user limits, core-based entitlements, or OS-image persistence are characteristics of other licensing models, not node-locked licensing.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is node-locked licensing?
Open an interactive chat with Bash
How does a hardware fingerprint work in node-locked licensing?
Open an interactive chat with Bash
What steps are needed to reactivate a node-locked license on new hardware?