Jump to content
Welcome to our new Citrix community!
  • 0

Double hop drive mapping shows incorrect client name on drive maps, is that normal?

Terry Rebstein


When doing a double hop scenario with users accessing a W2K16 Session host desktop, then launching a W2K16 published app from that desktop, we are finding that the drive mappings are behaving strangely. The HKLM\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ClientDrive\NativeDriveMapping is set to FALSE (default).  The behavior we see is the client endpoint drives are mapped all the way to the published application, which is good, but it says C:\ on Server1 on the second hop despite the drives in fact being from the Client. I would expect/prefer it to say C:\ on Client within the published application.


Also I had to open map network drives for some reason to get the drives to map through the second hop despite them being identified as local drives. 


This is Xendesktop 7.1903

Link to comment

1 answer to this question

Recommended Posts

  • 0

The behavior you are experiencing is normal and expected.
- To map a network drive in ICA Citrix uses it as: \\client. 
-  While creating second ica session, ica uses available drives on first hop 2016 server and maps them using \\client (as if they were original drives on server1)

- And now these get reflected in second hop session as C:\ on Server1

Hope it answers your query. I was curious to know if this was causing any functional loss?



Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...