1Since version 11.0, AutoConnect stores it’s settings in an SQLite database. If you use multiple terminal servers or a VDI and want to avoid duplication of the configuration tasks, you should therefore first move the location for this database from a local to a network drive:
- To do so, open the AutoConnect settings.
In the General tab, you will find the storage location of the configuration database for the AutoConnect settings (Mapping) as well as the settings users have selected for preferences such as default printer or default paper tray (User-specific printer preferences).
- To relocate the mapping database onto a network drive, firstly move the database from:
into a shared folder on the network, to which the domain computer (the TP AutoConnect Service) has read permission and the administrators have write permission.
Note! You have to set up the access settings of the directory in the share permissions as well as in the NTFS permissions.
- Then, under Mapping, enter the UNC path to the new storage location. Confirm with OK or Apply.
Note! Under Mapping, specify the UNC path only when you have already moved the AutoConnect database there. Otherwise AutoConnect would try to remotely create a database that would then not work because the tables Dynamic Printer Matrix and Map Additional Printers missing. It’s also possible to move the local database later on and thus overwrite the incomplete remote one.
- Restart the TP AutoConnect Service.
Note! You can use the AutoConnect group policy Specify mapping configuration file path (Mapping database) alternatively.
- To relocate the databases with user settings onto a network drive, under User-specific printer preferences, you can enter the UNC path to the new storage location. On this, specify the database name with the user variable, e. g. %username%.db, since a separate database is required for each user. Confirm with OK or Apply and restart the TP AutoConnect Service.
Note! You can use the AutoConnect group policy Specify mapping configuration file path (Mapping database) alternatively – especially when using the Desktop Engine installer role.