Mapped Drive isn't Available for All Users

Learn how to troubleshoot an issue where a File Storage file system mapped to a Windows drive isn't available for all users.

Symptom: After mounting a file system from a Windows instance as the opc user, the mapped drive isn't available to other logged in users.

Cause: This is expected behavior with a mapped network drive mounted locally to a Windows machine.

Solution: 

For domain users, create a logon group policy object that runs the mount command when domain users log in to the Windows machine attached to the domain. For more details about configuring a logon group policy in Windows, see Using Startup, Shutdown, Logon, and Logoff Scripts in Group Policy.

For Windows machine local users, you can have the same mount command logon script as a local policy object at the Windows machine level. Or, you can use following option as well:

1. Log in to the Windows instance as the opc user.

2. Create a batch file called FSSmount.BAT with contents such as:

   net use * "\\<mount_target_ip>\<export_path>" /p:yes

3. Copy the batch file to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp.
4. Log in to the instance as another user to verify that the File Storage file system is mounted and available.