Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1716
  • Last Modified:

Citrix Presentation Server 4.5 Client drive mappings not working

Since migrating our citrix server farm to a VMware ESX environment client drive mappings have stopped working.

We are running two citrix servers on 4.5 and our VMware environment is runing on ESX 4.1.
0
Higalv
Asked:
Higalv
1 Solution
 
S00007359Commented:
check you firewalls and routing. can u do a manual drive mapping, u can start from thre
0
 
HigalvAuthor Commented:
It can't be an issue with routing as this issue has only occured since we virtualised our Citrix Server Farm.

Also - client drives for CD/DVD drives and other system partitions on local PC's do appear but some don't.
0
 
James_3Commented:
Client drives only appear if they are given permission by the user.
We run citrix in esxi and our drive mappings are done in a vbscipt in the startup folder and they work fine.
0
Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as the high-speed power of the cloud.

 
BrummelbartCommented:
Hi,

We have a similar problem. We use the same system (PS4.5, ESXi 4.1). On the first six VM based citrix server, the client drive (not network drive) mapping is working fine. Now we setup ten more Citrix Servers, and the client drive mapping is not working on these machines.

Same user, same Thin Client:
Connecting to Server X --> USB Drive available
Connecting to Server Y --> USB Drive not available

We went through all our documentations and installation notes, but no hint what we have done to enable.

Any Ideas?
0
 
BrummelbartCommented:
Hi there,

solved it! :-)

I went through some citrix KB articles and compared registry dumps from a working and not working server. Check your registry @
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider]

On a NOT working server at least CdmService and Webclient were missing. Below is the set of registry keys that worked for our Citrix Servers.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder]
"ProviderOrder"="PDVFSNP,CdmService,RDPNP,LanmanWorkstation,WebClient,PnSson"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order]
"ProviderOrder"="PDVFSNP,CdmService,RDPNP,LanmanWorkstation,WebClient,PnSson"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ShortName]
"CLIENT"="Citrix Clientnetzwerk"

Open in new window


Best Regards, Brummelbart
0
 
HigalvAuthor Commented:
Thanks for your responses. We resolved this issue a while ago - turn out it was related to a corrupt group policy which was applying to the citrix servers.
0
 
HigalvAuthor Commented:
issue resolved without any assistance from EE.
0

Featured Post

When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot has fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now