Last updated:
At a customer, I recently encountered an old acquaintance:
“No device license is currently available for this computer. A system shutdown will be initiated in 720 hours.”
A classic PVS error message.
With PVS 2507 + LAS, however, it is worth taking a closer look.
For example, the community has an interesting report involving PVS 2507 on Windows Server 2025:
Licensing initially works, but after approximately 23 hours PVS loses its licensing. Running the PVS Configuration Wizard again restores it. Until the following day.
A community finding? Yes.
But Citrix has now also officially fixed several interesting PVS licensing issues in 2507.1 CU2:
🔴 CVADHELP-31063
After migration to Citrix License Activation Service (LAS), PVS could incorrectly report Not entitled. Processing of expiration dates and time zones was among the factors involved.
🔴 CVADHELP-31165
Even time differences between PVS servers could cause device licensing issues. With CU2, PVS now tolerates up to 15 minutes of clock difference.
Another familiar issue after a LAS migration is :
Cloud vs. on-premises licensing.
For CVAD on-premises + PVS + UHMC/Platform licensing, check that PVS is actually configured for on-premises use and that the corresponding PVS_CCS / PVSD_CCS entitlements exist.
My current PVS 2507 licensing checks therefore look like this:
✅ Check the exact PVS build
✅ Account for 2507.1 CU2 / known fixes
✅ Check LAS status and entitlements
✅ Check cloud vs. on-premises
✅ Check PVS_CCS / PVSD_CCS
✅ Compare NTP/clock settings across all PVS servers
✅ Consider the Stream Service after licensing changes
Only then would I start investigating the conventional route through ports, firewalls and the license server.
The interesting part:
The error message is old.
Its possible causes are not.
Anyone simply following the old CTX132198 checklist for PVS 2507 may easily overlook the newer LAS/2507-specific causes.
