Windows® 2000 and XP operating systems manage mapped drives differently. Windows 2000 uses a common namespace for drive mappings while Windows XP uses separate namespaces for each user session. The agent attempts to remap remembered connections for user accounts, but may not be able to successfully complete the mapping at runtime. You can use a special environment variable to assist with drive mapping on Windows: the _MAP variable. When you set this variable, the Windows Agent maps drives before executing your steps.
A typical practice when using the _MAP variable is to assign it in the project environment, so that the same drive mapping is passed down to all the step environments through environment variable inheritance. Note that if you also define a _MAP variable in a step environment, the step environment's value overrides the project environment, as only one _MAP value can be defined for a particular step.
Although it is intended for Windows environments, use forward slashes to separate directory path names in the _MAP variable. When the paths are used, the agent automatically corrects them as needed.
X:=//server/sharedefines a runtime mapping that connects the X: drive to the Windows UNC path name \\server\\share.
X:=//server/share;Y:=//server/share2
X:=//server/share(alternateusername,password)
Drives mapped via the _MAP variable are unmapped on command completion.
Even if they map successfully, drive mappings on Windows 2000 may still be inaccessible if a user logged onto the system's console is using the drive or share in question.