- #BUHTRAP SILENT INSTALLATION LITEMANAGER .EXE#
- #BUHTRAP SILENT INSTALLATION LITEMANAGER INSTALL#
- #BUHTRAP SILENT INSTALLATION LITEMANAGER DOWNLOAD#
Passes along the specified properties to the installer as command line arguments. Specifies the directory where the log files will be placed in, if not specified, the current working directory will be used. Please refer at the corresponding documentation for more information on this property.
Will not include 'OVERRIDE_CONFIG=1' for the MSI installation. Will only work in combination with the parameter /startDeployment. Halts execution for the program as long as the deployment process is running. Runs the command ' ShellAPI deployment start' after installing the Workspace Agent.
#BUHTRAP SILENT INSTALLATION LITEMANAGER DOWNLOAD#
If you're using the static server download feature, it will download the legacy installer instead of the Universal Windows Agent installer. Uses the input after '=' as the download URL, instead of the static address. Lists the available commands with a quick description of its function.įorce the download from URL even if the Agent installer is locally available. Command Line OptionsĪll commands are case insensitive. If you'd like the application to wait until deployment is finished, you can use the flag /waitForDeployment. This is important because otherwise the ShellAPI will not know which deployment to start. If the /startDeployment flag is specified, the bootstrapper will run the command ' ShellAPI deployment run' after successful installation.Īlso, if /startDeployment is specified, the Bootstrapper will write the field to True in the configuration file.
#BUHTRAP SILENT INSTALLATION LITEMANAGER INSTALL#
The tool will then run the installer and check for a successful install afterwards.
#BUHTRAP SILENT INSTALLATION LITEMANAGER .EXE#
EXE file via command line or include the Agent.MSI or Agent.EXE file with the Bootstrapper before running. You must specify a direct download URL to the. NOTE: If you are using a version lower than Liquit Workspace Server, the static zone URL fetch will not function. If you are using Liquit Workspace Server or higher, the tool can use the server URL specified in the Agent configuration to attempt to download the installer file directly from the Workspace Server. The tool also checks if the downloaded file is a valid.
If you want to download the legacy MSI installer instead of the new Universal Windows Agent installer, you should specify /legacyDownload as a command-line argument. If you are using Liquit Workspace Server 4.0 or higher, the tool will by default download the new Universal Windows Agent installer instead of the legacy MSI installer. If you're using a version before Server 4.0 the command /legacyDownload is also required! If you are using a Server version earlier than, and you are not including an installer file with the tool, then /downloadUrl= is required instead. Using the static zone URL download only functions on Server or higher. Otherwise it will use the configuration file to get the server zone URL. If the command /downloadUrl= is specified it will use this. To download the file the tool needs a direct download URL. If not, it will try to download it instead. The tool will then check if there is an Agent.MSI or Agent.EXE file already present in the directory from which the bootstrapper is started. If the command /certificateThumbprint="XYZ" is specified the bootstrapper will also write the value to the "Certificate Thumbprint" field under the "Registration" section in the configuration file. If the command /certificate="path/to/file.cer" is specified the bootstrapper will copy the certificate to the Liquit data folder, for example to C:\ProgramData\Liquit\Agent.Īfter that it will add the data "Type" = "Certificate" to the configuration file under the "Registration" section. The bootstrapper will either use the Agent.JSON or Agent.XML configuration file depending on which is available next to the bootstrapper. If the command /zoneOverride= is specified, the tool will write the value to the Agent configuration file before continuing.
To uninstall multiple copies of the Liquit Agent you will have to run the Bootstrapper multiple times with the /uninstall command specified.Īfter executing the uninstall the bootstrapper will quit. The bootstrapper will find the first Liquit Agent installation it can find in the registry, searching for the DisplayName matching "Liquit Universal Agent" or "Liquit Workspace Agent", and use its GUID to run the msiexec /x command. If the command /uninstall is specified, the uninstall process is executed and the rest of the bootstrapper processes are ignored.
0 kommentar(er)
