Citrix Receiver double hop drive mapping

When we work with Virtual Apps and Desktops in most cases we can use the published App or Desktop from our computer, but in some cases, for security reasons, we need to launch the Desktop and work with our Apps incide the desktop. At this point we do a “Receiver double hop”.

So when we try to save the document to the Desktop, we see that the “Local drive C” it is the driver of our local PC and we can’t save the document to the C driver of the VM. That’s occurs because The first connection map the Local drive C of the PC to the VM as “Local drive c”, and in the VM we can see the original “C drive” of the VM and the new one mapped from the PC as “Local Drive C”. The app see that Local Drive C and try to use it.

Now how we can solve this? We need to modify 2 registry entries:

HKEY_LOCAL_MACHINE\Software\Citrix\UncLinks\UNCEnabled –> We need to set this entrie to 0

If not exist, create a DWORD and set to 0.

On 32 bit OS:

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ClientDrive

name: NativeDriveMapping
Type: REG_SZ
Value: True

On 64 bit OS:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ClientDrive

name: NativeDriveMapping
Type: REG_SZ
Value: True

If not exist, create it.

Now when we restar the VM and do the double hop connection, now see the “Local drive C” of the VM, and the mapped drive of the PC we see it lime a share with another letter. IF we launch the app from the Receiver incide the VM, and try so save or open something, we can now navegate the VM drive.

Author: Nicolas Ventre

Virtualization architect with more than 15 years implementing complex environments. Security Specialist and Linux instructor