1. Home
  2. Windows App
  3. Windows App Drive Configuration

Windows App Drive Configuration

The CFP Windows App allows you to access local disks and network shares from your CFP 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 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 CFP 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 CFP. 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.
  • The Windows app converts all drive letters to UNC paths.
  • When the Windows app is installed, it will search for all of the mapped drives for the currently logged in user and will automatically generate a system for each mapped letter drive and network share for that user.

Best practices – Adding Drives on the Windows App:

  1. 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.  Once systems are auto created in CFP for each of the drives, you can switch the Win app to run as a service, and all of the mapped drives will convert over to UNC paths automatically.
  2. Adding a drive to the Windows app (desktop mode):
    1. Map the drive as a letter or as a network share.
    2. Create a new system (Windows Drive or Share) and select the Win app for Point of Presence.  You’ll see your new drive  in the Disk or Share enumerator.
  3. Adding a drive to the Windows app (service mode):

    You can mount a drive with net use:

    net use * \\path\todrive /persistent:yes

    The drive should enumerate in the drive listing once you have done this.

    UNC paths can be added to Windows apps in service mode via CFPclient.  Please contact cfp-support@tervela.com if you need to do this, or visit Adding an UNC Path to a Windows App for information on adding UNC paths in CFPclient.

Additional Tools and Troubleshooting Tips:

  1. 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.
  2. If you create a drive with net use, make sure that the drive is persistent (/PERSISTENT).
  3. 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

  1. Mapped drives must be mapped under the same user as the Win app installer.
  2. 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.
  3. You can add UNC paths to systems via CFPclient.
  4. 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.
  5. The Win app supports CIFS drives and some NFS drives.
  6. For MacOS drives, note that while CFP 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.
  7. If you suspect that you have duplicate files and folder names (e.g., Linux OS), make sure Generic Folder Listing is checked on in Advanced Options for the Windows source.
Updated on April 22, 2021

Related Articles