Available for: Hybrid work job, End-User Agents
Overview
Configure drive mapping in the Hybrid Work job
Drive Mapping Lifecycle
Overview
This guide is intended for system administrators managing file distribution using Hybrid Jobs with Windows End-user Agents. Drive mapping is designed to support specific customer scenarios where files must be organized under a predefined structure.
Configure drive mapping in the Hybrid Work job
This functionality is supported only when using Hybrid Jobs and Windows End-user Agents. The root path used in the job must be a non-cloud location, not defined by user.
Admins can configure a job to map its root path to a specific drive letter (e.g., Z:). The agent will map this path in the context of the current user session.
Selected drive cannot be changed by editing the job. It's required to remove and add the Agent to the job with the new drive letter.
The MC will issue a warning if the chosen drive letter is already used in another job. This does not block saving but serves to prevent unintentional drive conflicts.
The Agent is designed to report specific error messages if drive mapping fails.
Best practices
Assign unique drive letters per job to avoid conflicts and mapping failures. Carefully organize agent assignments so that no two conflicting jobs target the same device unless absolutely necessary.Always remove Agents from the job via the Management Console to ensure that drives are unmounted cleanly.
Drive Mapping Lifecycle
When the Agent starts or the job begins execution, the drive mapping is automatically applied. By default the drive gets system's name, but it can be changed manually via Registry on the device:
1. Open Registry Editor and navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\Y where Y is the mapped drive letter.
2. Create a string value _LabelFromReg and add the desired drive name. Save. No additional actions required, it’s applied immediately. Max label length is 32 characters.
More details can be found here.
The mapping is persistent:
- upon server restart;
- if Agent process is not running (Agent is stopped).
The Agent ensures the drive is correctly mapped upon job start, agent restart, or system reboot.
If the Agent is gracefully removed from the job, the system will unmount the drive by default. However, in cases where the Agent is uninstalled or removed ungracefully, the mapped drive may remain and require manual cleanup.
Mapped drives can be seen in CMD with subst command from the current user's session.