This topic describes general guidelines for installing the Auto Updater on multiple Windows endpoints. You can use Microsoft System Center Configuration Manager (SCCM) or similar application.
Once you have initially installed the Auto Updater on all the endpoints using SCCM (or other application), add and use the Endpoint Update Policies you create when updating the endpoints. (See Endpoint Update Policies.) (There is no need to deploy using SCCM for further updates of the Auto Updater or the agent.)
If you are using the Auto Updater, it is recommenced that you disable SCCM updates for the Agent or enforce the minimum version.
Contact your Account Representative or the Support Team for more information about Auto Updater.
Prerequisites for the target endpoints:
-
The Auto Updater can be installed on any supported Windows-based operating system (server or desktop) that you want to monitor.
For requirements:
-
See Supported Platforms and System Requirements for ITM / Endpoint DLP. (it is recommended that you always use the latest Service Pack for your operating system)
-
- When using HTTPS connection, make sure the target endpoints trust your CA digital certificate (or the self-signed digital certificate) that issues the SSL certificate. To enable the computers that are running the agent to trust your digital certificate source, you must import the root CA digital certificate (or the self-signed digital certificate) to each client computer. After importing the digital certificate, the computer will trust that source and communication through SSL/TLS will be allowed.
Installing the Auto Updater
-
Download the select the stable version, for example winupdater-x.x.x.zip for the relevant tenant and agent Realm. See Windows Auto Updater Installation.
-
Extract the contents .zip file, you'll have the following files
When you extract the contents of the .zip file, you'll have the following files:
-
UpdaterSetup--<version>.msi: Setup file
- SaasUpdaterSetupInstall.cmd: Executable installation file
-
-
Download the Installation Configuration File.json for the relevant tenant and Agent Realm. This is the Installation Configuration File, see Installation Configuration File.
-
Edit and define the parameters in SaasUpdaterSetupInstall, see Installing the Auto Updater for Windows from the Command Line.
-
Copy the following files to the target endpoint:
- Installation Configuration File.json
- ITMSaaSBundle-<version>.exe
- WinagentInstall.cmd
When installing the agent, the .exe files are located on the target endpoint and when the .cmd is installed, the .msi files will be called from the local path.
-
If using SCCM , to initiates the installation process, initiate as Admin on the target machine.
This is an example of the .CMD file with the install command:
msiexec /i{local path on the target endpoint}\UpdaterSetup-<version>.msi INSTALLDIR="%ProgramFiles%\Windows Client Utility\Saas Updater Utility" /quiet /norestart PRECONFIGPATH="<path_to_preconfig_file.json>" /l*v "%temp%\Windows Client_Updater_Utility_setup.txt"