Double Hop Drive Mappings
A good friend oof mine ran into the problem below where users were unable to map their drives in a double hop environment. The whole solution looks something like this:
Situation A : User is connecting to Windows 7 VM via XenDesktop from Windows 7 Desktop. Then, from the VM he goes on and launches an application from XenApp 6.5 farm.
Result : User can see his network drives mapped in XenApp 6.5 session from Windows 7 VM.
Situation B : User is connecting to Windows 7 VM via XenDesktop from Wyse Terminal (RX0L). Then, from the VM he goes on and launches an application from XenApp 6.5 farm.
Result : User can’t see his network drives mapped in XenApp 6.5 session from Windows 7 VM.
Same network, same user with the same access rights, same Windows 7 VM and the same application hosted on XenApp 6.5. Wyse support didn’t really have any ideas, although they mentioned that this will probably be related to the version of Citrix client they use on their terminal. It is not a proper Citrix Receiver or anything like that. It is a custom client which is based on god knows what version of receiver or PNagent.
Anyway, I came across this article http://support.citrix.com/article/CTX127872 which described a similar situation, but with double hop being two XenApp servers rather than XenDesktop-XenApp. This reminded me the way ICA traffic functions. When you are connecting in a double hop environment, older clients by default will enable a pass-through connection. This means the last hop, in my case XenApp 6.5 server, is trying to map drives from the Wyse terminal because it thinks that it Wyse terminal is your local device and XenDesktop VM is just a jump-box.
It works fine when source device is a Win7 desktop because it is running Receiver 3.3 which by default does not use pass-through session mode. Obvious solution would be to disable pass-through mode on the source device, but as it is a Wyse terminal – we can’t really do that. So, I applied registry tweak on VM to modify drive mapping behavior to make sure that it thinks that is the starting point in this chain of connections and the problem was solved:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA
Client\Engine\Configuration\Advanced\Modules\ClientDrive
Create the following registry value:
Value name: NativeDriveMapping
Type: REG_SZ
Value: True
Thanks for this, hopefully it should help some peeps out.
