| During the File Storage section of the Design Phase, you should have documented how client drives will be configured. Client drive mapping is built into the standard Citrix device redirection facilities and the client drives appear as a network type (Client Network) in Network Neighborhood. The clients disk drives are displayed as shared folders with mapped drive letters. These drives can be used by Windows Explorer and other applications like any other network drive. By default, the drives on the client system are all automatically mapped. If the MetaFrame servers drives were not remapped during installation of MetaFrame then the client drives will, by default, start with V$ and continue mapping all available client disk drives and CDROMS in ascending order. If they were remapped then the client drives will start with C$. The client drive letter is a configurable setting via the servers registry. (this is a per server setting, so if you choose to change the default drive letter then you will need to make the change on all your MetaFrame servers) Remember if you configure MetaFrame to automatically auto-create drive then you will need to make sure enough drive letters are available. You can configure client drive mapping farm wide or with the release of MetaFrame XP with Feature Release 2 you can configure on a user / group basis.
With the release of MetaFrame XP with Feature Release 2, Citrix has given you the ability to assign auto-created client drive mappings on a user and or group basis. This is the mechanism that I recommend you use. By default automatic client drive mapping is enabled, so we will need to create a policy to disable it and add the appropriate user and group accounts. The following defines how to create a Citrix policy to disable the auto creation of the end users local drives. 1. Create a specific user global group to disable client drive mapping. i.e., Disable Client Drive Mappings 2. Open the Citrix Management Console, right click on Policies and click Create Policy. 3. Enter a name for the new policy. I recommend something like Disable Client Drive Mapping. Click OK when finish. 4. Right click on the newly created policy and click Properties. 5. Open the Client Devices folder open the Client Drives folder double click the Connect Client Drives policy Click to select the Rule Enabled radio button in the Connect Client Drives box Click to select the Do Not Connect Client Drives at Logon radio button and click OK to enable the policy. 
6. Right click on the policy created in the above steps and click Assign Users. 7. Select the users group you created in step 1 and click OK when finished. You have now successfully created a Citrix policy to disable client drive mapping. If you would ever find a need to disable auto creation of local client drives then all will need to do is add their users and or group to the Disable Client Drive Mapping global group.
You are able to disable automatic client drive mapping and through the Client Settings dialog box of a selected ICA connection in the Citrix Connection Configuration Utility. The Connection options control whether drives are auto-created. If this option is cleared, the devices are still available but must be mapped to drive letters manually. If during the File Storage section of the Farm Design you decided upon disabling automatic client drive creating, then you need to manually map client drives or use policies to enable them as discussed is the above sections. The following defines how to manually map client drives. 1. Click Start Click Programs Click Citrix Click MetaFrame XP Click Citrix Connection Configuration double-click on your connection type. 2. Click the Client Settings button 
3. Uncheck the Inherit user config button. 4. Uncheck the Connect Client drives at Logon button. 
5. Click OK. 6. You are now ready to manually map client drives. This can be done in a multitude of ways. You can configure all MetaFrame users at once through the %SystemRoot%\System32\UsrLogn2.Cmd file. You can configure drive mapping on a user / group basis through login scripts. You can instruct your users to manually map via the command line. Add the following line to each of the above ways to manually connect client drives: net use x: \\client\c$ Note: where x: is the drive letter you want to map and c$ in the client drive you want mapped. NET USE connects a computer to or disconnects a computer from a shared resource, or displays information about computer connections. The command also controls persistent net connections. | net use [devicename | *] [\\computername\sharename[\volume]] [password | *]] [/user:[domainname\]username] [[/delete] | [/persistent:{yes | no}]] | | net use devicename [/home[password | *]] [/delete:{yes | no}] | | net use [/persistent:{yes | no}] | | | | None | Used without parameters, net use retrieves a list of network connections. | | devicename | |