Clientname pass-trough 2nd Hop

[Tom Tschage]

Hello Citrix Community,

before I attempt to reach out to Citrix support again, I would like to present my issue publicly here. I don’t believe we’re the only ones experiencing this, so I hope there may be kind souls in the community willing to share their expertise.

Our problem and requirement is as follows:

We launch additional published applications from a published Citrix desktop. When the client is switched by the user, only the endpoint name of the 1st hop is updated. However, the 2nd hop does not receive an update if the session status remains unchanged (connected). This update of the clientname is essential due to multiple dependencies on the endpoint name.

The available Citrix documentation on this matter is unfortunately insufficient, sometimes contradictory, and possibly outdated. See:

• Client Name Not Passing Through in a Double-Hop Scenario (registry entries are set but appear to have no effect).
• Session State Monitor Tool for XenApp/XenDesktop (seems contradictory/outdated).
• Virtual Channel Driver 10 (also seems contradictory/outdated).

Following this forum post, we plan to process the client name from the registry, but the update first needs to reach the 2nd hop:

• Environment Variable CLIENTNAME for Published Apps Not Found

Our setup is as follows. I can provide further details if needed:

• 1st Hop: VDA version 2203.0.3000.3300 OS: Windows 2016
• 2nd Hop: VDA version 2203.0.5000.5310 OS: Windows 2019

The two registry keys are set on the first VDA: Client Name Passthrough in Double-Hop Scenario. The 2nd hop is managed by a service provider (SaaS).

We are using several different versions of the Citrix Workspace App (usually 24.x.xx.xx). The issue persists across all versions.

My questions:

1. Is the functionality (automatic update of the endpoint name in a Citrix multi-hop scenario for all sessions) still available?
2. If so, how should it be exactly configured as of November 2024? What troubleshooting options might be available?

Any helpful responses are greatly appreciated.

Best regards,
Tom

[Jeff Riechers]

I just did this for a client.  This article fixed it for us.

https://support.citrix.com/s/article/CTX239561-client-name-not-passing-through-in-a-doublehop-scenario?language=en_US

However this is only for Citrix Workspace App based launches.  If they are using a different launcher, like Epic Slingshot, that captures the clientname and passes it through differently.

How do you connect to the Saas provider?

[Tom Tschage]

Hi Jeff,
Thanks for your response. We are connecting to the SaaS provider via Citrix Workspace App - mainly with Version 24.2.1000.1016. Which version are you using?
The registry keys are configured as described in article CTX239561, but unfortunately, we are not observing any effect from the registry keys; no updates are being made to the client name in the 2nd hop session. I also tested this internally by setting up a 2nd hop (launching a published application). Even here, the client name is not updated during an active session. Now I’m confused.

Are these the only configuration requirements? Or should this work out-of-the-box with the regkeys alone?

The  key “KEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Citrix\SessionStateMonitor” refers to the SessionStateMonitor tool (which we currently do not use). I found an article about it:
https://support.citrix.com/s/article/CTX127491-session-state-monitor-tool-xenappxendesktop?language=en_US&t=1730951949397
However, it all seems somewhat outdated.

Edited November 8 by Tom Tschage

[Jeff Riechers]

Mine worked just fine with that client and those registry entries.