Finding in the Wild | StoreFront + Entra ID Is Becoming Seriously Interesting

During a current Citrix project, I came across a development that will be particularly interesting for future StoreFront architectures. StoreFront can now configure Microsoft Entra ID directly through the management console. This becomes especially interesting in hybrid environments:

During a current Citrix project, I came across a development that will be particularly interesting for future StoreFront architectures.

StoreFront can now configure Microsoft Entra ID directly through the management console.

This becomes especially interesting in hybrid environments:

→ Hybrid users can receive resources from Citrix DaaS and on-premises CVAD through StoreFront.

→ From CVAD 2603, StoreFront supports Entra ID SSO to published resources, provided the VDAs are appropriately hybrid Entra ID joined.

→ Even more interesting: Entra SSO and FAS can be used in parallel within the same store.

StoreFront uses each delivery group’s logon type to decide which authentication method to use for resource launch.

For example, this enables gradual modernization of an environment without immediately removing FAS from the design.

What I take from this for new designs

In future, I would create an authentication matrix during the design phase:

Delivery group → VDA join state → authentication method → SSO method

For example:

• Conventional AD VDAs → FAS
• Hybrid Entra ID joined VDAs → Entra SSO
• DaaS workloads → according to the identity design

In larger hybrid environments in particular, this prevents considerable confusion later.

For me, this is another step towards making StoreFront more interesting in modern Entra ID/DaaS architectures, rather than viewing it solely as a component of conventional on-premises CVAD environments.

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. 😉

Upgrade to Virtual Apps and Desktops Version 1912 LTSR

On December 18, Citrix Virtual Apps and Desktops (CVAD) version 1912 was released. Following a little guide to the update to the latest version.

Link to Citrix Virtual Apps and Desktops Documentation

Citrix Virtual Apps and Desktops EOM EOL Matrix
Continue reading “Upgrade to Virtual Apps and Desktops Version 1912 LTSR”

Citrix Virtual Apps and Desktops & WEM 2003 is released

The new current releases of Citrix Virtual Apps and Desktops, Workspace Environament Management & Citrix Provisioning are now available. They contains many new features compared to the last LTSR.

Citrix Virtual Apps and Desktops 2003
Continue reading “Citrix Virtual Apps and Desktops & WEM 2003 is released”

Citrix Virtual Apps and Desktops 7 1912 LTSR is out now

The new Long Term Service Release of Citrix Virtual Apps and Desktops is now available. It contains many new features compared to the last Current Release and of course more regarding the last LTSR.

New Features

The following new features have been added compared to the last current release.

Citrix Virtual Apps and Desktops 1912 LTSR
Continue reading “Citrix Virtual Apps and Desktops 7 1912 LTSR is out now”