Command-line options for deploying the software

Use these command-line options when creating a deployment task to install the product on managed systems.

Type supported options in the Command line box.

Options are not case-sensitive.

Examples

  • INSTALLDIR="D:\Installed Programs" /l"D:\Installed Programs\Logs"

    Installs the product files to a folder on drive D under Installed Programs and saves the installation log files to a folder under Installed Programs\Logs.

  • ADDLOCAL="tp,wc"

    Installs Threat Prevention and Web Control, and automatically installs the Common module.

Option Definition
ADDLOCAL="tp,fw,wc"

Selects the product modules to install:

  • tpThreat Prevention
  • fwFirewall
  • wcWeb Control
  • fw,tp,wc — Install all three modules.

The shared Endpoint Security Platform (Common module) is also installed automatically when any product module is installed.

Example:

ADDLOCAL="tp,wc"

Installs Threat Prevention, Web Control, and Common.

CAVA="number_of_scanning_threads" Installs Endpoint Security with support for the Common AntiVirus Agent (CAVA). Requires Threat Prevention.

Disables the blocking cache in the On-Access Scanner (OAS), increases the number of OAS scanning threads to 200, and enables network scanning, to ensure the OAS scans all files from CAVA. Optionally, you can specify a different number of scanning threads. See KB88973 for more information.

Note: When upgrading from a previous version of Endpoint Security with CAVA, you must use the CAVA command-line option. Otherwise, the installation removes CAVA from the upgraded system.
INSTALLDIR="install_path"

Specifies where to install the product files on the system.

The installation wizard creates an Endpoint folder at the specified location and installs the product to this folder.

Example:

INSTALLDIR="D:\Installed Programs"

Installs the product modules under D:\Installed Programs\Mcafee\Endpoint Security.

By default, product files are installed in the folder C:\Program Files\McAfee\Endpoint Security.

/log"install_log_path" or /l"install_log_path"

/l*v"install_log_path"

  • Specifies where to save the installation log files for tracking installation events.

    The installation wizard creates an Endpoint folder at the specified location and saves the log files to this folder.

    Example:

    /l"D:\Log Files"

    Installs the product log files under D:\Log Files.

    By default, log files are saved in the Windows System TEMP folder C:\windows\Temp\McAfeeLogs.

  • *v — Specifies verbose (more descriptive) logging entries.
/nocontentupdate Does not automatically update product content files on the managed system as part of the installation process.

Content files include the latest AMCore, Exploit Prevention, and Adaptive Threat Protection content files required for Endpoint Security.

Caution: Update content files to ensure that the system is fully protected. If you don't update them during installation, schedule an update as soon as possible.
/override"program_name" Overrides and removes the specified conflicting products:

  • hipsMcAfee Host Intrusion Prevention

Example:

/override"hips"

Removes McAfee Host Intrusion Prevention automatically during installation.

/quarantinefolder="directory path" Specifies the location of the Quarantine folder where detected threats are placed. The folder path is limited to 190 characters.

Example:

/quarantinefolder="D:/reports"

Creates a Quarantine folder at D:\reports\Quarantine.

By default, the Quarantine folder is located in the folder <SYSTEM_DRIVE>\Quarantine.

/import <file_name> Imports settings from the specified file.
Note: Must be used from a Windows command line with the SetupEP utility.

Example:

SetupEP /import mysettings

Imports settings from the file called mysettings.

Tip: Best practice: To create custom packages that include custom policies and client software for deployment with McAfee ePO, use Endpoint Security Package Designer.
/module <TP|FW|WC|ESP> Applies imported settings to the specified product modules.
  • TPThreat Prevention
  • FWFirewall
  • WCWeb Control
  • ESP — Resources shared by product modules.
Note: Must be used from a Windows command line with the SetupEP utility.

Example:

SetupEP /import mysettings /module TP FW

Imports settings from the file called mysettings to Threat Prevention and Firewall.

Tip: Best practice: To create custom packages that include custom policies and client software for deployment with McAfee ePO, use Endpoint Security Package Designer.