Hello,we have a problem with client drive mapping on XenApp 6.5 / Windows Server 2008 R2 X64.We use the GPP to map all network and client drives.Also we enabled on the Citrix Policies the access to the local Clientdrives.We denied the Policy for connect the client-Drives automatically because we map the drives with our GPP. (We need drive-letters for the client-drives)The Problem in this constellation is, that in the session the user have all mapped network-drives, but no client drive is visible.When i write \\client\c$ in the explorer (in the same session) i can access the client-drive but i have no connected drive.When i use a logon-script over gpo instead of the gpp the client drives are connected.Have anyone the same problem an a solution for me that i can connect the client drives over gpp ??many thanksRobert
Visit the next link http://support.citrix.com/article/CTX127968
i know this article and have set this registry value.
But this value only works when i connect the local drives automatically over the citrix policy.
Problem with that is, that the citrix policy begins with the letter v: and go backwards for additional drives (i know the reg-key to manipulate the start-letter)
we need very different settings (client-drives) for many users.
for example the user x need only the local D: drive on the server as drive y: and the user y need only the local drive c on the server as drive y: ....
with the gpp it is very easy to manage a lot of drive-connections.
hope you have another solution for me.
can you test with follow command?
\\client\c$ subst v:
to delete it -> subst v: /d
net use and subst works manually and over a gpo logon script.
but we need the connection over the gpp
i think that on session startup maybe the gpp client drive connection implements before the citrix policy which allows the client connection and the logon scripts over gpo implements after the citrix policy.
the gpp works fine in all situations without citrix sessions.
maybe someone knows if we can change the order of implementing policies
I know this is an old post but we have also just come across this problem in our XA6.5 with Hotfix Rollup 1 test installation.
mapping a drive when in the desktop to \\client\c$ works fine but our GPO (that current works with our XA6 farm) doesn't map on XA6.5.
My initial thoughts are XA6.5 processes GPO's slightly differently and is processing this GPO before the desktop launches with the variable to map to the local client (as this is a Citrix specific command).
It's not so much of an issue for us as we use L: across the board to map to \\client\c$ so there are other ways around it for us but would be nice to keep it all in GPO's.
Any help appreciated
the solution is the hotfix XA650R01W2K8R2X64002