-runInstaller

Windows

eps.rmm.exe -runInstaller <path to full kit> [-installerXml <path to file>] [-resumeAfterReboot]

macOS

./eps.rmm -runInstaller <path to full kit>

Linux

./eps.rmm -runInstaller <path to full kit>

-runInstaller

As part of the installation flow, the SDK RMM Tools will perform a detect operation before starting the installer and another one post-install. The results of the operations are reported back to the caller via both process exit codes and standard output print.

In case the pre-install detect operation finds a running product on the endpoint, the RMM SDK Tools returns the exit code and the installation ends.

If the pre-install detect operation does not find a running product, it starts the BEST installation and monitors the process until its completion. At the end of the installation, another detect operation is performed, at the end of which the RMM SDK Tools returns the exit code from the install process and prints to stdout the results from the post-install detect operation.

In case of a failure encountered by the BEST installer, such as limited disk space, the end results are as follows:

In case of a successful installation the end results are as follows:

-installerXml

Optional parameter supported on Windows only. Use this during installation to configure the BEST installer to use a different configuration file than the one built into the installation package, or in case the installation package includes no configuration files.

-resumeAfterReboot

Optional parameter supported on Windows only. Use this switch only in combination with –installerXml to update the installer.xml file to force resume Bitdefender Endpoint Security Tools installation after reboot.