by Kenneth » 01 Aug 2019, 08:35
You can perform a silent installation, using the --mode unattended option from the command line.
*For macOS, however, the following applies: the TeamDrive installer DMG must first be mounted. This can be done via the command line by calling the following "hdiutil attach" function and including the path of the TeamDrive installer DMG. For example: "hdiutil attach /Users/td/Downloads/Install-TeamDrive-4.6.12.2788_TMDR.dmg" (If you would like to avoid having to mount the TeamDrive installer's DMG, you can extract the "installer.app" from the DMG once and then use this on multiple machines.)
From there, you need to navigate into the mounted volume of the TeamDrive installer's DMG. For example: "cd /Volumes/Install-TeamDrive-4.6.12.2788_TMDR". After you have done that, execute "Install-TeamDrive-4.6.12.2788_TMDR.app/Contents/MacOS/installbuilder.sh --mode unattended" OR add any of the other additional parameters listed below.
./sample-installer.bin --mode unattended
This will perform an unattended installation that will not prompt the user for any information. Any required information can be passed to the installer using command line switches. This mode allows for easy integration of the installer into your own scripts.
Useful TeamDrive Installer command line parameters when embedded in MSI installer:
--mode unattended (Installation mode unattended)
--mode unattended --unattendedmodeui minimal (Installation mode unattended with minimal graphics)
Optional Parameters:
--port <port> (TeamDrive Admin Gui Port (Default: 45454), only available in TeamDrive Agent Installers!)
--prefix <prefix> (Installation directory)
Optional: specify an unattended UI mode:
--unattendedmodeui <unattendedmodeui> Unattended Mode UI (Default: none - Valid values: none minimal minimalWithDialogs)
Please note: The command line parameter "--port" is only available in TeamDrive Agent Installers starting from version 4.6.3 build 2147!
After the installation, the preconfigured "teamdrive.ini" or "teamdrive.settings" file can be copied to the appropriate destination.
The settings file "teamdrive.ini" has global validity for the entire computer and can be found on Windows in "%PROGRAMDATA%\TeamDrive\", the respective settings file, "teamdrive.settings", for a single user account can be found in "%APPDATA%\TeamDrive\". The settings for a user account overwrite the global settings. Please note that in the "teamdrive.settings" file, in contrast to the "teamdrive.ini" file, all settings must be listed below a "[Settings]" section.
All paths should be written in Unix with "/" instead of "\".
You can configure the default spaces path with "spaces-path=".
Configure the default backup path with "backup-path=".
You should configure the default path for the application data directory or cache with: "new-data-path=" to ensure that the next time the program is restarted, the current application data directory is moved to the new path and not just referred to.
Example for the "teamdrive.ini" file:
spaces-path=C:/TeamDrive/Spaces
backup-path=C:/TeamDrive/Backup
new-data-path=C:/TeamDrive/Data
Example for the "teamdrive.settings" file:
spaces-path=C:/TeamDrive/Spaces
backup-path=C:/TeamDrive/Backup
new-data-path=C:/TeamDrive/Data
For multiple user accounts and corresponding TeamDrive installations, we strongly recommend that you only make path settings in the "teamdrive.settings" file of the respective user account to avoid conflicts and overwriting the data of other installations.
A configuration of the autostart is currently neither configurable in the unattended mode of the installer nor via a settings variable. However, you can simply create a program shortcut e.g. in "%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup" and add the parameter "autostart" to the target. TeamDrive is then started in the background as a tray application.
The setting for the autostart delay is:
autostart-delay=1
The numerical value indicates the delay in minutes. Allowed interval is 1-60 minutes.
For automatic export:
auto-export-path=
What is the "Exports" path for?
This path contains automatically generated audit trails for
a) all activities/history of all active Spaces
b) all read receipts of all active spaces
as CSV files for further evaluation, processing or backup according to GoBD/DGSVO. The interval for the automatic creation can be configured with the following settings (value is number of days):
activities-auto-export-interval=
read-confirmations-auto-export-interval=
Activate or deactivate local key storage:
perform-backup=true resp. perform-backup=false
Activate or deactivate key storage on the server:
enable-key-repository=true or enable-key-repository=false
The settings for the notifications are slightly more difficult.
To do this, the following values (flags) of the corresponding categories must be specified
ConflictsAndErrors = 1
InvitationsAndMembers = 2
FilesAndVersions = 4
Comments = 8
PublishedFiles = 16
LockedFiles = 32
and the numerical value can be assigned to the respective functions. The value 0 switches off all notifications accordingly. You can also conveniently determine the respective values of the combinations using the TeamDrive interface, as these are saved directly in the "teamdrive.settings" file when you exit the settings dialog.
For the notification center of the operating system or popup messages:
notification-types=63
For email notifications that are sent immediately:
immediate-email-notification-types=0
For email notifications that are sent as a daily report:
daily-email-notification-types=0
With the following setting you can configure that email notifications are sent to all administrators of the space if one of the above mentioned functions is not deactivated (not possible via the interface):
admin-email-notification=true resp. admin-email-notification=false
For settings related to the notification center, we reserve the right to change the values in future versions at any time and to convert them accordingly during an update.
Possible question: If the path for Spaces, Backup, Export and Cache is left on default and the "teamdrive.settings" file now changes, what effect does this have on the 4 locations mentioned?
All these settings can be changed at any time by the user via the TeamDrive application (interface) and overwrite the corresponding settings in the "teamdrive.settings" file. Settings that are manually written to the file are only read when TeamDrive is started. TeamDrive uses the appropriately configured paths or creates them if they are not available, if possible. Any existing databases in these paths are usually only copied if they are changed via the TeamDrive interface, so that if the settings in the "teamdrive.settings" file are changed manually, empty folders or old databases can remain in the previous locations/default paths. You should see the manual configuration of the paths more as a default for standard settings.