Finding in the Wild | Citrix Printers Missing After a Windows Upgrade?

Citrix currently documents a known issue around CVAD 2603: After an in-place Windows upgrade on a system with Citrix VDA already installed, the Citrix Print Providers may disappear from the Windows execution order. Possible symptoms: – Client printers

Citrix currently documents a known issue around CVAD 2603:

After an in-place Windows upgrade on a system with Citrix VDA already installed, the Citrix Print Providers may disappear from the Windows execution order.

Possible symptoms:

– Client printers are no longer created
– The Citrix Universal Printer is missing
– Printing issues occur only on the upgraded VDAs
– Spooler and Citrix Print Manager nevertheless run without errors

According to Citrix, the cause lies in the Windows upgrade process: the registered Print Provider order is not fully retained.

Workaround:

Open the following registry path:

In the Order value, add the following entries before the other providers:

• Universal Printer
• Client Printer

Then restart the VDA.

My recommendation:

After every in-place upgrade of a VDA, check not only VDA registration and session launch, but explicitly test Client Printer, Session Printer and Universal Printer too.

A successful logon does not automatically mean anyone will be able to print afterwards.

Finding in the Wild | Citrix Admins – How Many of Your PowerShell Scripts Still Use Get-BrokerMachine?

Probably more than you would like. Anyone who has operated Citrix Virtual Apps and Desktops for a while knows this cmdlet: Get-BrokerMachine It appears in countless: 👉 Health-check scripts 👉 Monitoring solutions 👉 Automations 👉 Reporting scripts 👉

Probably more than you would like.

Anyone who has operated Citrix Virtual Apps and Desktops for a while knows this cmdlet:
Get-BrokerMachine

It appears in countless:
👉 Health-check scripts
👉 Monitoring solutions
👉 Automations
👉 Reporting scripts
👉 Scheduled tasks
👉 Custom admin tools

With CVAD 2507 LTSR, Citrix marked Get-BrokerMachine as deprecated.

Its intended successor is:
Get-BrokerMachineV2

Why should I care?
Deprecated initially does not mean the cmdlet will stop working tomorrow.

That is exactly why such changes are often ignored.

The problem usually comes later.

The next CVAD upgrade is completed, everything looks good, and eventually a ten-year-old PowerShell script suddenly stops working.

Then the search begins:
What actually changed?

The answer may have been in the deprecation list several releases earlier.

Now is the right time to check

I would not wait until Citrix actually removes the cmdlet.

Search your Citrix scripts for:
Get-BrokerMachine

And check:
Can I already switch this to Get-BrokerMachineV2?

Scripts that run automatically are particularly interesting.

An interactive admin script tends to attract attention quickly.

But a scheduled task that has generated reports or processed machine states every night for years?

It can be broken for several days before anyone notices something is missing. 😎
It is not just Get-BrokerMachine

Other older Citrix PowerShell functions are also being gradually deprecated.
Another example from CVAD 2507 is:
Repair-AcctADAccount

For me, a Citrix upgrade now therefore includes more than:
Supported OS → hypervisor → SQL → VDA → StoreFront

It also includes:
Which custom automations depend on the Citrix PowerShell API?

My recommendation
Before the next CVAD upgrade:
👉 Search PowerShell repositories for deprecated cmdlets
👉 Check scheduled tasks
👉 Include monitoring and health-check scripts
👉 Do not forget custom admin tools
👉 Test replacement cmdlets in the lab

Old automations have an inconvenient characteristic:
They work brilliantly for years, until the day they do not.

Usually during an upgrade, of course.

Finding in the Wild | Renaming a Citrix Site – What Could Possibly Go Wrong?

An apparently harmless change. The name of a Citrix site needs changing. No VDA update. No StoreFront upgrade. No NetScaler change. Just a new site name. What could possibly go wrong? 😎 More than you might think. 💥

An apparently harmless change.

The name of a Citrix site needs changing.

No VDA update.
No StoreFront upgrade.
No NetScaler change.

Just a new site name.

What could possibly go wrong? 😎

More than you might think.

💥 StoreFront loses Optimal HDX Routing

Citrix fixed an interesting issue in StoreFront 2507 LTSR CU2:

Renaming a Citrix site could delete the existing Optimal HDX Routing configuration in StoreFront.

A seemingly cosmetic change suddenly becomes a networking issue.

Optimal HDX Routing determines which NetScaler Gateway routes ICA/HDX traffic to a particular Citrix site or zone.

If this mapping disappears, the session path may change.

In the worst case:

StoreFront works.

The application is displayed.

The user clicks Start.

Yet ICA traffic no longer follows the intended gateway path, or launch no longer works as expected.

Exactly why I like these findings

During a StoreFront, NetScaler or CVAD upgrade, everyone expects an impact and plans corresponding tests.

But when someone says:

We are only changing the site name.

Hardly anyone thinks of Optimal HDX Routing.

These supposedly small changes are often the interesting ones.

Affected?

Citrix resolved the behavior in StoreFront 2507 LTSR CU2.

Anyone still using an older 2507 LTSR build with Optimal HDX Routing should account for this when renaming a site.

My recommendation

Before a site rename:

👉 Back up the StoreFront configuration
👉 Document Optimal HDX Routing
👉 Check gateway mappings
👉 Perform a real ICA launch after the change
👉 Verify the ICA/gateway path

And, of course:

Plan for StoreFront 2507 LTSR CU2.

Takeaway

Another example of a Citrix change having an impact somewhere other than where it was made.

Site name changed → StoreFront routing lost → ICA traffic suddenly follows a different path.

Finding in the Wild. 🕵️‍♂️

Or put another way:

Never assume an administrative change is just cosmetic. 😉

Finding in the Wild | A New Edge Security Baseline – and Your Browser Integration Suddenly Stops Working?

Microsoft has released the new Security Baseline for Microsoft Edge 151. Normally, that initially sounds like: New version → new ADMX → update baseline → done. This time, however, I would look more closely in Citrix and RDS

Microsoft has released the new Security Baseline for Microsoft Edge 151.

Normally, that initially sounds like:

New version → new ADMX → update baseline → done.

This time, however, I would look more closely in Citrix and RDS environments.

Microsoft includes several new recommendations. One is particularly interesting:

👉 Process Isolation

What is behind it?

Process Isolation aims to prevent other local processes from interfering with Microsoft Edge or manipulating browser processes.

Entirely understandable from a security perspective.

However, enterprise environments have plenty of software that operates exactly at this point.

For example:

DLP / endpoint security / SSO / monitoring / browser integrations / legacy agents

And this is where it becomes interesting for Citrix.

On a normal client, it affects one user.

On a multi-session VDA with 30, 50 or more users, a small browser baseline change may suddenly affect many sessions simultaneously.

A typical scenario

New Edge ADMX files are added to the Central Store.

The new Security Baseline is applied to the Citrix VDAs.

Edge starts.

Websites work.

Test successful?

Not necessarily. 😉

The interesting part is the integrations:

👉 Does SSO still work?
👉 Do DLP/security components work?
👉 Do browser extensions work?
👉 Do internal web applications work?
👉 Are there sudden errors or unusual processes?

Another point: Automatic HTTPS

Microsoft also recommends evaluating Automatic HTTPS.

That initially sounds sensible too.

However, anyone still running internal applications accessible only through HTTP should be cautious with aggressive upgrade modes.

Experience shows that older Citrix environments still contain quite a few of these. 😎

My recommendation

A new browser Security Baseline should not go straight into the production golden image.

First:

Baseline diff → test VDA → security/SSO/DLP → internal web apps → multi-session test → production

And if Process Isolation causes problems:

Do not simply disable the policy again.

First determine which software is trying to interfere with the browser process.

That may be the actual finding.

Takeaway

Security Baselines are not collections of settings to simply switch to Enabled.

Especially on Citrix multi-session VDAs, small browser changes can have a substantial impact.

Hardening without compatibility testing is another way to prepare for future troubleshooting. 😉

Finding in the Wild | MCSIO Cache Disk Exists, but Stays Empty

Another Citrix issue where everything initially looks correct. You update the environment to VDA 2607. MCS provisions the machine. The write-cache disk is present and correctly attached to the VM. VDA registered. Users can work. Looks good. Except

Another Citrix issue where everything initially looks correct.

You update the environment to VDA 2607.

MCS provisions the machine.

The write-cache disk is present and correctly attached to the VM.

VDA registered.

Users can work.

Looks good.

Except for one small detail:

👉 The MCSIO write-cache disk stays empty.

The combination matters

Citrix currently documents this issue under PMCS-63379 for this exact combination:

**Windows Server 2019 * VDA 2607 * MCSIO**

The cache disk is successfully attached to the provisioned VM, but is not used as a write-back cache as intended.

The tricky part:

If your upgrade checks only confirm that the cache disk exists, this issue is easy to overlook.

The workaround is almost typically Citrix 😎

On the master image, open the following registry path:

Create an empty registry key named:

Parameters

Yes.

An empty registry key.

Then:

Shut down/reseal the master image → create a new snapshot → update the MCS catalog → restart the machines.

Afterwards, normal user activity should populate the write-back cache disk again.

Why I find this interesting

MCSIO exists specifically to absorb writes through RAM and the temporary cache disk.

Citrix uses the following file as part of this:

mcsdif.vhdx

If the disk is attached but not used, simply looking at the VM configuration is not enough.

My recommendation after a VDA upgrade

With MCSIO, do not check only:

✅ Cache disk attached

Also check:

✅ MCSIO driver present
✅ Cache actually active
✅ mcsdif.vhdx present
✅ Write-cache disk receives writes
✅ Catalog update works

Because:

Disk attached apparently does not automatically mean cache working. 😉

Affected: VDA 2607 + Windows Server 2019 + MCSIO

Citrix issue: PMCS-63379