Skip past navigation linksSecure Global Desktop 4.31 Administration Guide > Users and authentication > Client Drive Mapping (--cdm)

Client Drive Mapping (--cdm)

Objects with this attribute

Object Manager

Attribute name Usage
Client Drive Mapping Create as many client drive mapping specifications as you need, using the New and Delete buttons. Order them using the arrows.

Command line

Command optionUsage
--cdm drive_spec... Replace drive_spec with a drive mapping specification of the form clientdrive:access:driveletter.
For example, a:rw:z. See below for more information. Separate each drive_spec with the "pipe" character, "|".

Description

This attribute defines which drives on their Microsoft Windows client device a user may access from applications running on Microsoft Windows, UNIX and Linux application servers, and which drive letters to use on the application server for those drives.

The Client Drive Mapping attribute is an ordered list of drive mapping specifications. Each specification names:

Note The first matching entry in the list is used, so make sure the most specific settings (for example, A or B) appear before more general settings (for example, All Drives).

The following tables show the values displayed in Object Manager for each part of a drive mapping specification, and the corresponding value to use on the command line.

For Client Drive:

Object Manager Command line
All drives alldrives
Fixed drives fixeddrives
R/W removable rw
R/O removable ro
Network drives networkdrives
A:, B: ... Z: a, b ... z

For Access Rights:

Object Manager Command line
Read-only ro
Read-write rw
None none

For Drive Letter:

Object Manager Command line
Same as client same
A:, B: ... Z: a, b ... z

Examples

Skip past command syntax or program code--cdm 'a:rw:z|networkdrives:rw:same'

For a person object, this means the user is given read-write access to drive A on their client device using drive Z on the application server, and also has read-write access to all network drives defined on their client device using the same drive letter used on the client.

The user might have access to other drives, for example a fixed drive C, depending on the Client Drive Mapping attributes for the person object's ancestors in the organizational hierarchy.

Related topics