Feature request: Map drives for Windows network locations

[jblagden]

Describe the problem

Windows network paths are only available to the user that mounts them, and only mounted automatically during an interactive login. This means we have to be able to mount network locations (aka letter drives) as the service user, from within the service user's session.

Proposed Solution

If the service user mounts the network location, the path will be valid and available.

This could be configured as a part of local storage profiles.

Example Use Cases

On an SMF machine where I'm providing my own storage available as a network location.

[epmog]

Thanks for the suggestion, it's definitely an interesting thought to have the service map drives and/or potentially mount drives on other operating systems based on storage device. Would require also having the user provide connection information to these devices.

From what I understand there's a few different options available right now on service-managed fleets that should work depending on the device? But important to know that I haven't tried these myself.

1. Queue Environment - Could set-up a net use command. Note: this won't set it up for the service user, but for the user running the jobs. net use by default is ephemeral to the logon context, so with the queue environment it gets set for the session of the worker agent impersonating the job user.
2. Host Config - If you require any additional software to be installed on the machine as Admin to support your filesystem then this allows you to perform the set-up on worker startup.
3. Use UNC with path mapping - If the application/integration support you're using supports path mapping then you could set-up storage profiles to point the UNC path for the worker. The storage profile may already be required if you're submitting Unix -> Windows, but not necessarily Windows -> Windows if you have the same mapped drives across contexts.

For more information on:

• net use
• mapped drives in services