Last updated:
This week, I upgraded a customer’s Citrix environment to the current CVAD 2607 LTSR release.
Initially, the upgrade went completely smoothly.
✅ VDAs started correctly
✅ Registration with the Delivery Controller succeeded
✅ Applications could be launched
✅ No anomalies in Citrix Director
An apparently successful upgrade.
But shortly afterwards, individual business applications suddenly reported licensing issues.
❌ Invalid license
❌ Hardware ID changed
❌ Reactivation required
Initially, everything pointed to an issue with the licensing software.
However, the actual cause was a change in Citrix MCS.
🔍 What did I find?
Since VDA 2511, Citrix ensures that MCS-provisioned Windows machines have a unique MachineGuid.
Previously, multiple MCS machines could inherit the same value from the master image.
With newer VDA versions, including 2607 LTSR, this machine identity is assigned uniquely and persists across restarts and image updates.
A sensible technical improvement.
However, some business applications use the Windows MachineGuid as part of their licensing fingerprint.
If that value changes during an upgrade, the software may identify a new machine.
🛠️ How did I check this?
The MachineGuid can be read from the registry:
|
1 2 3 4 |
Get-ItemPropertyValue ` -Path HKLM:SOFTWAREMicrosoftCryptography ` -Name MachineGuid |
Comparing it with the previous machine identities revealed the change after the upgrade.
This also explained why the affected applications required license reactivation.
What am I taking into future upgrades?
✔ Document MachineGuid before the upgrade
✔ Check licensing dependencies of business applications
✔ Test the new VDA version on pilot machines first
✔ Validate license activation after the upgrade
✔ Coordinate reactivation with the vendor if needed
⚠️ Simply restoring the old MachineGuid or copying it to multiple VDAs is not a sound solution.
💡 My takeaway
The Citrix upgrade was technically successful. Nevertheless, a background change directly affected users’ applications.
Not every issue after a Citrix upgrade is a classic Citrix fault. Sometimes a technical foundation changes that other applications depend on.
Citrix documents this behavior under PMCS-58288.
