A collegue of mine had troubles getting Client Drive Mapping (CDM) to work with his new Citrix XenApp 6.5 environment. So I checked the regular stuff;
- Is CDM policy configured? Correctly applied? (Yep)
- Are no group policies configured which might be blocking CDM? (Nope)
- Is CDM blocked on the ICA-tcp protocol? (Nope)
- Is CDM working over RDP? (Yep)
Well, all seemed to be configured correctly. Since XenApp 6.5 is (at this time of writing) a Technical Preview, I almost filed it as a bug.
For a last attempt I turned to CTX238200 – Troubleshooting Client Drive Mapping. I verified all points meticulously until I got to point 7:
7. Ensure that Client Network is visible under Network Neighborhood. If it is not, follow the steps listed below:
a. Start Registry Editor (Regedt32.exe) and go to the following key:
value for ProviderOrder contained only LanmanWorkstation.
Add CdmService, so
that the Value now reads “CdmService,LanmanWorkstation.”
b. For Presentation Server 4.5, ensure the path defined under the
CommonFilesDir value from
c. Restart the server
So I checked HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order, and found no CdmService, only LanManWorkstation. Hey, that could be it! So I put CdmService in there, but unfortunately, after a reboot, the drives still weren’t mapped. I turned to another environment I’ve setup at another customer with XenApp 6, where I knew that CDM was working fine. So I checked the Order value there:
Hmm, PICAClientNetwork looks interesting. And lo and behold, with PICAClientNetwork in the Order key (and rebooting), CDM worked!
So next time, you have troubles with CDM on XenApp 6(.5) and all seems to be configured well, don’t forget this one 😉