MAP

Use MAP to map drives and search drives to network directories or to map to NDS objects such as cluster-enabled volumes.

If you use MAP to automate drive map assignments during execution of the login script, users don't need to map drives every time they log in.

If you do not want the result of each mapping to be displayed as it is executed, add the MAP DISPLAY OFF command at the beginning of the login script. When all drive map assignments have been completed, add the line MAP DISPLAY ON and MAP to your login script. This sequence provides a cleaner display for users as they log in.

Instead of specifying drive letters such as F: or G:, you could use an asterisk followed by a number n to represent the nth network drive. For example, if the first network drive is F: then using MAP *3:= would assign H: {1 2 3 = F G H}. Or, if the first network drive is D:, then using MAP *4:= would assign G: {1 2 3 4 = D E F G}.

This allows drive letters to reorder themselves automatically when local drives are removed or added or when the first network drive is changed. This also allows users to log in from workstations with a different number of local drives than their regular workstation.

You can map a local drive (usually A: through C:) to a network directory, but you cannot access the local drive until you remove the network drive mapping. Do not map over the local drive containing the Windows directory.

Do not map a drive to a network drive such as a CD-ROM drive.


Command Format

MAP [[options]|[parameters][drive:=path]

Replace drive with any valid network drive letter, local drive letter, or search drive number.

Replace path with either a drive letter, a full directory path, a Directory Map object, or an NDS object such as a cluster-enabled volume.

More than one command can be on the map line if the commands are separated by a semicolon ( ; ), as shown in the following example:

MAP *1:=SYS:PUBLIC;*2:=SYS:PUBLIC\DOS

When mapping a drive to a directory on an NDS server, begin the path with either the Volume object name or server\volume.

When mapping to a directory on a bindery-based server or to an NDS server that isn't the current server, begin the path with the server's name.

When mapping to an NDS object, use the object's fully distinguised name preceeded by a leading period (.).

Replace option with one of the following:

Replace parameter with one of the following:



Previous | Next