Last updated:
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. 😉
