Using TeamDrive in conjunction with a Windows Terminal Server can sometimes cause issues for users due to the terminal server’s procedure of synchronizing the user’s roaming profile while TeamDrive is already running.

To combat this issue, we have implemented a check to make user’s aware of their TeamDrive app’s data directory being stored in a roaming user profile. If the check finds this case to be true, all Spaces will be marked with the status “TeamDrive Data Volume in Roaming User Profile” and synchronization will be halted until one of the following two solutions has been implemented. We highly recommend applying the first solution when feasible.

Solution 1: Move the TeamDrive app’s data directory outside of the roaming user profile.

It is highly recommended that this step be performed by a terminal server admin, as they should know which local locations are accessible by the user, regardless as to where the user is logging in from.

On a small scale, i.e. for a handful of users, the data directory can be moved by:

  • opening the TeamDrive app and going into the settings,
  • in the “Cache” section, clicking “Select New Location” to choose a new path for the data directory,
  • restarting TeamDrive (the data directory will be moved during the start of TeamDrive).

On a large scale, i.e. for rolling out TeamDrive for multiple users, the TeamDrive home directory path can be set on a global scale using the teamdrive.ini file:

  • Locate the teamdrive.ini file. (C:\ProgramData\TeamDrive\teamdrive.ini)
  • Open the “teamdrive.ini” file with a text editor.
  • Enter the absolute path using slashes in Unix style (‘/’), e.g. “teamdrive-home=c:/td-data“. Please note that when entering settings in the “teamdrive.ini” file, no section “[Settings]” may be used. Sections are not supported in the “teamdrive.ini” file.
  • Save your changes.

Please note that this method is only recommended when introducing TeamDrive on a new system. For existing TeamDrive users, it is necessary for the administrator to move the TeamDrive data directory for each user individually. Use the following link to find out the default location of the TeamDrive data directory.

Solution 2: Ignore the check altogether.

Please be advised that this setting should only be set in exceptional cases as this could possibly lead to synchronization issues with the TeamDrive app database in the terminal server environment, due to the terminal server’s procedure of synchronizing the user’s roaming profile while TeamDrive is already running.

To ignore the check altogether on a small scale, i.e. for a handful of users:

  • Locate the teamdrive.settings file, which is usually located in the default location of the TeamDrive database (..\AppData\Roaming\TeamDrive).
  • Quit TeamDrive.
  • Open the “teamdrive.settings” file with a text editor and enter the following setting in the [Settings] section, “ignore-roaming-profile=true”.
  • Save your changes.
  • Start TeamDrive.

On a large scale, i.e. for rolling out TeamDrive for multiple users, the “ignore-roaming-profile=true” setting can be set on a global scale using the teamdrive.ini file as described above or, if you have your own provider code, directly on the server in your provider settings.