Day: May 16, 2011

When a user launches a session, XenApp tries to map disk drives on the server to the typical drive letters for the client device. If the drive letters are available, the server maps the client’s first floppy disk drive to A, the second floppy drive to B, the first hard disk drive to C, and so on. However, a server cannot map client device drives to letters that are assigned to the server’s own disk drives. Client drives that use the same letters as the server’s drives are assigned different drive letters, starting with V and going backward through the […]

Client drive mapping allows drive letters on the XenApp server to be redirected to drives that exist on the user device. For example, drive H in a Citrix user session can be mapped to drive C of the local device running the plug-in. Client drive mapping is built into the standard Citrix device redirection facilities transparently. To File Manager, Windows Explorer, and your applications, these mappings appear like any other network mappings. Note that Client drive mapping is not supported when connecting to MetaFrame Server 1.0 for UNIX operating systems. The XenApp server can be configured during installation to map […]