The Windows App allows you to access local disks and network shares from your Shuttle jobs. You can install as many Windows Apps in as many locations as you want. For optimal performance the computer the Windows App is installed on should be close to or on the server which serves the network share.
Network Share access
We aim to make it as easy as possible to access network shares, but there are some complexities to be aware of.
- The Windows App normally runs as a local administrator (via “elevation”). This is typically a separate Windows session from the user session. Windows maintains separate drive mappings and file share authentications for each user session. The consequence of this is that you will most likely not be able to access a drive mapped ad-hoc from a user session (via Windows Explorer or
net use...) from Shuttle. Ad-hoc drive mappings should be done from an elevated Administrator command prompt.
- The Windows App can run in application mode or in service mode. In service mode it will continue to run after the user session ends. In service mode, you can explicitly specify which user the app runs as.
Best practices – Adding Drives on the Windows App:
- The easiest way to connect all of your drives, regardless of whether you are running in desktop or service mode, is to map them as letter drives before the Windows app is installed. The user who maps the drives must be the same user who installs and runs the Windows app.
- Adding a drive to the Windows app (desktop mode):
- Map the drive as a letter or as a network share.
- You’ll see your new drive listed when you create a job and select the Windows app in the UI that is connected to that drive.
- Adding a drive to the Windows app (service mode):You can mount a drive with net use:net use * \\path\todrive /persistent:yesThe drive should enumerate in the drive listing once you have done this.
Additional Tools and Troubleshooting Tips:
- The show_attached_drives.bat utility, located in C:\Program Files (x86)\Tervela\Cloud FastPath\utils, will display all valid drives currently available for the Windows app. Simply double click the file to run it. If the drive is not listed after the batch file runs, it won’t enumerate for the Windows app.
- If you create a drive with net use, make sure that the drive is persistent (/PERSISTENT).
- If you do not see the drive enumerate, make sure that you can access the drive directly from File Explorer on the Windows computer, including browsing directories in the drive.
Troubleshooting Drive Connectivity
- Mapped drives must be mapped under the same user as the Win app installer.
- Mapped letter drives will not be visible if the Win app is run as a service. However, any letter drives created with the Win app as an app will be converted over to their UNC paths automatically when the Win app switches to service mode.
- If you have drive accessibility issues, the first thing to do is to try to access the drive from the Win app machine and user. Make sure you can browse the folder you are trying to access, and note any errors.
- The Win app supports CIFS drives and some NFS drives.
- For MacOS drives, note that while Shuttle supports paths that are longer than 256 characters, there is a Windows limitation for paths that are longer than this. This results in the paths being truncated with an appended string (e.g., ~ABCDEF) when they travel through the Windows environment. Run a simulation to ensure that this is not an issue. Note that not all Mac drives are Windows accessible.