Windows Agent Automated Installation

This topic describes general guidelines for installing the Windows agent bundle on multiple targets. (The Windows Agent Bundle lets you install the Agent and optionally the Content Analyzer utility for Content Scanning.) 

You can use Microsoft System Center Configuration Manager (SCCM) or similar application.

Prerequisites for the target endpoints:

• The agent can be installed on any supported Windows-based operating system (server or desktop) that you want to monitor.

  • See Supported Platforms and System Requirements for ITM / Endpoint DLP

• 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.

Installation on x86 Program Files is not supported.

Installing the Agent

1. Download the stable version, for example winagentx64-0.x.x.x.zip for the relevant tenant and Realm. See Windows Agent / Bundle Installation.

2. 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:

   • ITMSaaSBundle-<version>.exe: Agent Setup file

   • WinagentInstall.cmd: Executable installation file

3. Download the Installation Configuration File.json for the relevant tenant and Realm. This is the Installation Configuration File, see Installation Configuration File.

4. Edit and define the parameters in WinagentInstall.cmd, see Installing the Agent Bundle from the Command Line.

5. 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.

6. If using SCCM , it initiates the installation process is initiated as Admin on the target machine.

   This is an example of the .CMD file with the install command:

   ITMSaaSBundle<version>.exe /install /quiet contentdetection=1 TargetDir="%ProgramFiles%\IT Client Utility\Client Utility" PreConfigPath=C:\Temp\preconfig.json /log ITMSaaSBundle_SetupLog.log