Finding in the Wild | PVS 2507 – When the Device License Suddenly Disappears

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

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.

Finding in the Wild | Sometimes Old Citrix Problems Simply Return

Recently, with WEM 2507 CU1 on non-persistent VDAs , I encountered behavior that felt very familiar. And yes, I observed it myself. The VDA starts correctly, registers and initially appears completely healthy. But the WEM Agent cache does

Recently, with WEM 2507 CU1 on non-persistent VDAs, I encountered behavior that felt very familiar.

And yes, I observed it myself.

The VDA starts correctly, registers and initially appears completely healthy.
But the WEM Agent cache does not initialize correctly, so the WEM configuration is not applied reliably.

Interestingly, similar cases are currently appearing in the community:

Golden image → WEM works ✅
Provisioned VDA → WEM cache issue ❌
Cache reinitialize → WEM works again ✅

According to a community report, Citrix Support also suspected a startup timing issue: the VDA and WEM Agent start before the local WEM cache database has initialized correctly.

The interesting part:
This topic is not new at all.
Back in 2017, BIS-F introduced a WEM cache refresh at system startup.
A feature added later is particularly interesting for non-persistent images:
“Move WEM Agent Cache to the PVS or MCSIO persistent disk”

This places the WEM cache on a persistent location rather than the non-persistent system disk, for example:

PVS/MCSIO CacheDisk
↓
Citrix
↓
WEMCache

At system startup, BIS-F can also run commands such as:

-RefreshCache -RefreshSettings -RefreshCache -Reinitialize

.

To be honest, I had not paid much attention to this functionality for a long time, until I observed the behavior again myself.

A useful reminder:
Just because an old workaround once appeared unnecessary does not mean the underlying architecture no longer matters.

Especially with PVS/MCSIO + WEM + non-persistent VDAs, I would therefore include the WEM cache and its persistence in a health check again.

Incidentally, I have not yet found a public Citrix bug ID explicitly linking the current behavior to WEM 2507 CU1. For now, it remains exactly that:

Finding in the Wild. 🔎

Finding in the Wild | CWA CleanInstall & Teams SlimCore

During a recent Citrix Workspace App update , I encountered interesting behavior involving Microsoft Teams SlimCore . The Microsoft Teams VDI Plugin was already installed on the client. Workspace App was then updated using /CleanInstall . Initially, everything

During a recent Citrix Workspace App update, I encountered interesting behavior involving Microsoft Teams SlimCore.

The Microsoft Teams VDI Plugin was already installed on the client. Workspace App was then updated using /CleanInstall.

Initially, everything looked fine:
Citrix Workspace App ✔️
Teams VDI Plugin ✔️
Software deployment ✔️

Nevertheless, SlimCore optimization no longer worked.

The investigation revealed that the required DLLs were no longer present in the ICA Client directory, although the Teams VDI Plugin still appeared as installed under Apps & Features.

That is precisely what makes this issue interesting.

If an automated CWA update checks only installation status, you get a successful deployment even though the actual Teams optimization no longer works.

For my update tests, this means:
CWA version → Teams VDI Plugin → DLLs → SlimCore → actual optimization mode
must be checked together.

Especially with the increasing move to SlimCore, I believe this functional test should be part of a CWA/Teams update.

👉 Finding in the Wild: installed does not automatically mean operational.

These issues are exactly why I do not just install Citrix updates, but also check the relevant functions afterwards.

Finding in the Wild: I will keep investigating.

Finding in the Wild | PVS + Secure Boot – A Small CU2 Feature That Could Become Important in 2026

Citrix Provisioning 2507.1 LTSR CU2 is here. Among the usual fixes is a change that I find much more interesting for PVS environments than the version number suggests: 👉 Support for Microsoft Windows UEFI CA 2023 Why is

Citrix Provisioning 2507.1 LTSR CU2 is here.

Among the usual fixes is a change that I find much more interesting for PVS environments than the version number suggests:

👉 Support for Microsoft Windows UEFI CA 2023

Why is this important?

Microsoft is currently renewing the certificate chain behind UEFI Secure Boot. Some existing Secure Boot certificates date back to 2011, and Microsoft is gradually migrating Windows to the new 2023 certificates.

This is exactly where it becomes interesting for Citrix PVS.

PVS must understand the new Secure Boot world

With PVS 2507.1 LTSR CU2, Citrix now supports Secure Boot with images signed using the new Windows UEFI CA 2023 certificate.

Initially, this sounds like a small compatibility fix.

But it is not necessarily.

Anyone familiar with PVS knows:

💥 If the boot chain is wrong, there is no Citrix session.

We are no longer discussing logon duration, profiles or HDX performance.

The target simply does not boot.

Another interesting change

When a target device starts, PVS now automatically detects whether the system booted using:

BIOS or UEFI

.

This information is saved in the device record and is also available through farm telemetry.

I find this particularly useful in larger or long-established PVS farms.

Different firmware and boot configurations are surprisingly common there.

What would I check now?

Anyone using PVS + Windows 11 or Windows Server 2025 + Secure Boot should definitely keep CU2 on their radar.

Before a rollout, I would test in particular:

👉 Secure Boot + Windows UEFI CA 2023
👉 Target device boot
👉 PXE / BDM
👉 Existing vDisks
👉 Hypervisor firmware / UEFI configuration
👉 Boot after promoting a vDisk version
👉 Failover to a second PVS server

With changes like these:

The vDisk has worked for years is no guarantee that the future Secure Boot chain will also work.

My takeaway

For me, PVS 2507.1 CU2 is therefore more than just:

Another cumulative update with a few bug fixes.

Support for Windows UEFI CA 2023 is a classic future-readiness topic.

Microsoft is changing the Secure Boot trust chain.

Citrix is following suit with PVS.

And once a target fails to start after a Windows/Secure Boot update, an inconspicuous release-note entry suddenly becomes an important feature. 😎

Finding in the Wild | XenServer 9 + Windows Server 2025 – When a Boot Storm Becomes a Problem

An interesting detail from the current XenServer 9 known issues that may be particularly relevant to larger Citrix environments: XenServer documents a Windows Server 2025 issue under CP-51655. If many Windows Server 2025 VMs start simultaneously on the

An interesting detail from the current XenServer 9 known issues that may be particularly relevant to larger Citrix environments:

XenServer documents a Windows Server 2025 issue under CP-51655.

If many Windows Server 2025 VMs start simultaneously on the same XenServer host, some VMs may fail to start.

Why do I find this especially interesting in a Citrix context?

Because this scenario is completely normal there.

Citrix Power Management starts several workers in the morning.

An MCS catalog starts after a maintenance window.

Or PVS boots numerous targets almost simultaneously following a reboot schedule.

Initially, the symptoms may look like this:

Some of my Citrix workers will not start.

Troubleshooting will probably begin with MCS, PVS, the master image or the Delivery Controller.

But the cause may be one layer lower.

XenServer explicitly states that the issue can occur when a larger number of Windows Server 2025 VMs start simultaneously on a single host.

This also makes acceptance testing for new Server 2025 Citrix environments interesting.

A test with two or three VDAs may not be sufficient.

For XenServer 9 + Windows Server 2025, I would therefore also plan a realistic boot-storm test:

Start 5 VMs → 10 VMs → 20 VMs → 30+ VMs simultaneously.

Do not check only whether the VDAs are registered afterwards. Already at the XenServer layer, observe whether individual VM starts fail.

With Windows Server 2025 as a future multi-session platform in particular, this is a small detail with potentially significant consequences.

Known issue: CP-51655