This message was deleted.
# citrix-vads
Slackbot
08/14/2019, 12:41 PMThis message was deleted.
n
Nick Panaccio
08/14/2019, 12:44 PMI opened the ICA reference PDF that was linked. Assuming that the NativeDriveMapping keys listed there need to be set for this to work, I've confirmed that they're there in my W10 VDA and am waiting for the XA admin to confirm them on her end.
m
Martin Zugec
08/14/2019, 12:46 PMYou have to apply those changes on first hop (VDI), not on last hop (RDS)
n
Nick Panaccio
08/14/2019, 12:47 PMIn that case, already set.
m
Martin Zugec
08/14/2019, 12:48 PMAnd works?
n
Nick Panaccio
08/14/2019, 12:48 PMNope. I've had that enabled from the start.
m
Martin Zugec
08/14/2019, 12:48 PMDid you make registry changes or .ini changes?
Martin Zugec
08/14/2019, 12:49 PMIt was a couple of years ago, but pretty sure it required registry changes, not changing any .ini files
n
Nick Panaccio
08/14/2019, 12:49 PMYeah, these are registry changes
Nick Panaccio
08/14/2019, 12:49 PMAnd I believe it's all being handled by our Citrix policy in Studio
l
Lucas Van den Broeck
08/14/2019, 12:54 PMNativedrivemapping should only be needed if you want the drives from the middle hop to show (since XA6.5 and up). Default unset it should map through client drives from the original client to the second hop, which it does in the environments where I use it. If you set nativedrivemapping on your VDI you're telling the next hop XA to map to your VDI, not your original client (even though in some environments the text on the drivemapping will have you think otherwise)
n
Nick Panaccio
08/14/2019, 12:59 PMWell there you go, changing NativeDriveMapping to FALSE worked.
Nick Panaccio
08/14/2019, 12:59 PMin HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICAClient\Engine\Configuration\Advanced\Modules\ClientDrive
l
Lucas Van den Broeck
08/14/2019, 1:00 PMthought so, I was going to type, if you have it set and don't have a E: drive natively on your VDI, you'd be seeing that issue
n
Nick Panaccio
08/14/2019, 1:00 PMNow I need to figure out where that particular registry setting is coming from
l
Lucas Van den Broeck
08/14/2019, 1:04 PMremember that if you're using other citrix in citrix connections that they might be using the mapping in that way. A lot of HR applications that are used in Belgium work that way and we actually need the second hop to present client drives since the first hop could be a thin client etc.
m
Martin Zugec
08/14/2019, 1:41 PM@Lucas Van den Broeck Would be worth a blog post (or CTX article)
n
Nick Panaccio
08/14/2019, 2:32 PMYeah. that'd be helpful. I was manually modifying that key in my W10 VDA, but if I change the "Client drive mapping" GPO by deselecting "Enable client drive mapping", none of the drives are mapped in the XA session.
l
Lucas Van den Broeck
08/14/2019, 2:38 PMyeah that gpo controls the cdm virtual channel from the client side. So turning that off is the same as applying a ctx policy to say no drive maps are allowed, just only for that client.
As far as I know, there is no managed gpo setting for nativedrivemapping so manual (gpp prefs etc.) is the way to go. It will take on any session after that, no reboots necessary.
Lucas Van den Broeck
08/14/2019, 2:49 PM@Martin Zugec having them fix the original article would probably go a long way, I'm pretty sure it used to contain something in the direction of that. Otherwise I'd gladly give some feedback on extra stuff they could mention in it.
m
Martin Zugec
08/14/2019, 2:51 PMAlready opened a ticket to get it fixed...
We have been planning for a while to create a "Double-hop Best Practices" article for techzone.citrix.com
👍 1
n
Nick Panaccio
08/14/2019, 3:18 PMWhenever you write it, definitely throw a link to it somewhere on Slack.
Nick Panaccio
08/14/2019, 3:19 PMI'll have to test setting that key as a GPP, because I'm not sure if the other policy enabling it will override that setting.
m
Martin Zugec
08/14/2019, 3:43 PMAny new content is automatically promoted on #CLKSAPFUG channel 🙂
2 Views