Unattended Installation via the Command Line
For automated rollouts or setups handled by IT partners, the installer can also be run without user interaction.
Example:
./setup.exe --output="C:\KlardatenDatevService" --install-datev-user --install-service --start-service
Basic installation parameters
--output="C:\KlardatenDatevService": Required for command-line installations. Defines the target directory. Custom paths should be wrapped in quotes so backslashes are preserved.--install-service: Creates a Windows service namedKlardaten DATEV Connectorwith automatic startup. If the service already exists, it is recreated.--start-service: Starts the Windows service automatically after installation.--install-userless: Suppresses the warning when the service is installed without a Windows user. This is useful if credentials will be set later, for example remotely.
Windows and DATEV users via the command line
Create a new user
--install-datev-user: Creates the Windows userklardatenand the matching DATEV user.-s DATEVconnect.Domain="domain.ad.example.com": Overrides the automatically detected domain if necessary.
Use an existing user
If an existing Windows and DATEV user should be used, the values must be set explicitly:
-s DATEVconnect.IsConfigured=true-s DATEVconnect.Username="windowsUsername"-s DATEVconnect.Domain="domain.ad.example.com"-se windows.user.password="windowsPassword"
Secret values should always be passed with -se instead of -s so they are stored encrypted on the system.
Configuration values during installation
Runtime parameters can be set directly during installation:
-s <key>=<value>: Changes a configuration value in the current environment file, for exampleappsettings.Production.json. This flag can be used multiple times.-se <key>=<value>: Stores a secret value in encrypted form. Internally, Windows DPAPI is used, so the value can only be decrypted on the same system.
Example:
./setup.exe --output="C:\KlardatenDatevService" -s DATEVconnect.DatevGroup="My Datev Group" -se windows.user.password="Windows user password"
Debugging and development
The installer also supports a few parameters for operation, debugging, and development:
--dev: Runs the application in PowerShell instead of starting it as a Windows service.--ui: Forces the UI installer instead of switching directly to the service path.--stop-watchdog: Stops all existing watchdog services until the main service starts again.--start-update: Performs update-related finalization tasks. This parameter is used internally during the update process.