Mcafee Agent 5.6.X Installation Guide
Mcafee Agent 5.6.X Installation Guide
Mcafee Agent 5.6.X Installation Guide
x Installation Guide
COPYRIGHT
Copyright © 2020 McAfee, LLC
TRADEMARK ATTRIBUTIONS
McAfee and the McAfee logo, McAfee Active Protection, ePolicy Orchestrator, McAfee ePO, McAfee EMM, Foundstone, McAfee LiveSafe, McAfee QuickClean, Safe Eyes,
McAfee SECURE, SecureOS, McAfee Shredder, SiteAdvisor, McAfee Stinger, True Key, TrustedSource, VirusScan are trademarks or registered trademarks of McAfee,
LLC or its subsidiaries in the US and other countries. Other marks and brands may be claimed as the property of others.
LICENSE INFORMATION
License Agreement
NOTICE TO ALL USERS: CAREFULLY READ THE APPROPRIATE LEGAL AGREEMENT CORRESPONDING TO THE LICENSE YOU PURCHASED, WHICH SETS FORTH THE
GENERAL TERMS AND CONDITIONS FOR THE USE OF THE LICENSED SOFTWARE. IF YOU DO NOT KNOW WHICH TYPE OF LICENSE YOU HAVE ACQUIRED, PLEASE
CONSULT THE SALES AND OTHER RELATED LICENSE GRANT OR PURCHASE ORDER DOCUMENTS THAT ACCOMPANY YOUR SOFTWARE PACKAGING OR THAT YOU HAVE
RECEIVED SEPARATELY AS PART OF THE PURCHASE (AS A BOOKLET, A FILE ON THE PRODUCT CD, OR A FILE AVAILABLE ON THE WEBSITE FROM WHICH YOU
DOWNLOADED THE SOFTWARE PACKAGE). IF YOU DO NOT AGREE TO ALL OF THE TERMS SET FORTH IN THE AGREEMENT, DO NOT INSTALL THE SOFTWARE. IF
APPLICABLE, YOU MAY RETURN THE PRODUCT TO MCAFEE OR THE PLACE OF PURCHASE FOR A FULL REFUND.
1 Installation overview 5
Which type of installation do you need? . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
First-time installation workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
First-time installation using McAfee ePO On-Premises . . . . . . . . . . . . . . . . . . 6
First-time installation using McAfee ePO Cloud . . . . . . . . . . . . . . . . . . . . . 7
Product name conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Methods of installing the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Install from McAfee ePO (McAfee ePO On-Premises) . . . . . . . . . . . . . . . . . . . 8
Install manually (McAfee ePO On-Premises) . . . . . . . . . . . . . . . . . . . . . . 9
Install using third-party deployment (McAfee ePO On-Premises) . . . . . . . . . . . . . . 10
Install using logon scripts on Windows systems (McAfee ePO On-Premises) . . . . . . . . . . 11
Install using install scripts on non-Windows systems (McAfee ePO On-Premises) . . . . . . . . 11
Install the agent on an image (McAfee ePO On-Premises) . . . . . . . . . . . . . . . . . 12
Deploy using McAfee Smart Installer . . . . . . . . . . . . . . . . . . . . . . . . 13
Install in Virtual Desktop Infrastructure mode . . . . . . . . . . . . . . . . . . . . . 14
Upgrade installation workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2 System requirements 17
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Ports used by the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Index 59
Contents
Which type of installation do you need?
First-time installation workflow
Product name conventions
Methods of installing the agent
Upgrade installation workflow
®
McAfee Agent 5.6.0 bundles the McAfee Data Exchange Layer (DXL) client as a component. When you install
McAfee Agent 5.6.0 on the system, the McAfee Data Exchange Layer client is automatically installed. The Data
Exchange Layer client installation scenarios are covered later in this guide.
McAfee ePO The umbrella term for all McAfee ePO management platforms. When used in this
guide, the content applies to all platforms.
McAfee ePO On-Premises The locally installed (on-premises) version of McAfee ePO.
McAfee ePO Cloud The cloud version of McAfee ePO.
Deploying using McAfee ePO On-Premises Deploying using McAfee ePO Cloud
Install from McAfee ePO Deploy using McAfee Smart Installer
Install manually Install in Virtual Desktop Infrastructure mode
Install using third party deployment methods Install using Agent Deployment URL
Install using logon scripts (Windows)
Install using install scripts (Non-Windows)
Include the agent as an image
Deploy using McAfee Smart Installer
Install in Virtual Desktop Infrastructure mode
Install using Agent Deployment URL
See also
Install from McAfee ePO on page 28
Install on non-Windows operating systems from McAfee ePO on page 35
See also
Install manually on page 29
Install on non-Windows operating systems manually on page 36
Install the agent in managed mode on Ubuntu systems on page 37
See also
Install using third-party deployment methods on page 29
Install using Group Policy Object on page 34
Install the agent on Red Hat Linux systems using third party deployment method on page 38
Install the agent on Ubuntu systems using third party deployment method on page 39
See also
Install with logon scripts on page 30
See also
Install the agent on non-Windows systems using install scripts on page 41
See also
Including McAfee Agent on an image on page 25
See also
Deploying the agent using McAfee Smart Installer on page 23
See also
Install McAfee Agent in Virtual Desktop Infrastructure mode on page 27
3 Check in the required McAfee Agent packages to the McAfee ePO repository.
Upgrade manually
Use Framepkg.exe to manually upgrade McAfee Agent.
1 Create and download Framepkg.exe from McAfee ePO.
2 Right-click Framepkg.exe, select Run as administrator, and click OK to complete the upgrade.
See also
Upgrading and restoring agents (McAfee ePO On-Premises) on page 3
Contents
Requirements
Ports used by the agent
Requirements
Make sure that your client systems meet specific hardware and software requirements to install the agent.
System requirements
• Installed disk space — 50 MB (minimum), excluding log files
The list specifies the minimum system requirements for installing the agent. For information about system
requirements for other McAfee products, see the respective McAfee product documentation.
The agent supports all Data Execution Prevention modes in Windows operating systems.
When McAfee Agent is deployed on an incompatible operating system, the installation fails and an alert is sent to
system log file.
• VMware player
If peer-to-peer service and RelayServer are disabled, these ports are not open.
For information about the ports used by McAfee ePO for communicating through a firewall, see KB66797.
The method of installing McAfee Agent depends on the client operating system, tools used, new installation, or
an upgrade.
• McAfee Agent software package (MAxxxWIN.zip or MAxxxLNX.zip or MAxxxMAC.zip) — A .zip file that
contains product installation files. Once the package is checked in to the Master Repository, McAfee ePO can
deploy it to your managed systems.
• McAfee Agent key updater package (AgentKeyUpdate.zip) — This distributes the new master keys when an
update is received from the McAfee ePO managed repositories. McAfee Agent uses agent-server secure
communication (ASSC) keys to communicate securely with the server. You can generate new ASSC keys and
use them as a master set. Existing agents that use other keys in the agent-server secure communication
keys list do not change to the new master key unless there is a client agent key updater task scheduled and
run. McAfee Agent key updater package is multi-platform and updates the master public key (srpubkey.bin)
and the corresponding request key (reqseckey.bin).
Contents
McAfee Agent with integrated McAfee Data Exchange Layer (DXL)
®
McAfee Agent 5.6.0 bundles the McAfee Data Exchange Layer client as a component.
The Data Exchange Layer client is automatically installed on managed systems and connects to a DXL broker in
your environment. If the DXL broker is not present in your environment, the DXL client goes into an idle mode
where it consumes minimal resources until brokers become present. DXL services run as part of McAfee Agent
services.
For information about using the DXL client and installing the DXL broker, see McAfee Data Exchange Layer
documents.
• Sitelist.xml file
• req2048seckey.bin
• sr2048pubkey.bin
• agentfipsmode file
By default, McAfee Agent installation packages are at <System Drive>\Program Files (x86)\McAfee
\ePolicy Orchestrator\DB\Software\Current\<Product Id>\Install\0409. Product IDs for
supported operating systems are listed in the following table.
The Windows installation package is FramePkg.exe and the non-Windows package is install.sh.
This is the installation package that McAfee ePO uses to distribute and install McAfee Agent. FramePkg.exe
files are created when:
• You specifically create one in McAfee ePO
• McAfee Agent packages are checked in to any branch of the repository (Previous, Current, or Evaluation)
The default McAfee Agent installation package doesn't contain user credentials. When executed on the targeted
system, the installation uses the account of the currently logged-on user.
You can create custom installation packages with embedded credentials if needed by your environment.
Because an installer package has embedded credentials, access to it must be severely restricted. Installer
packages with embedded credentials must only be used in specific situations where another deployment method
is not available. For additional, important information about the use of embedded credentials, see McAfee
KB65538.
You can manage previous versions of McAfee Agent (4.8.x and 5.0.x) with 5.x.x extension. But, previous version
extensions cannot manage McAfee Agent 5.x.x clients.
Task
1 Download the McAfee Agent extension, EPOAGENTMETA.zip, McAfee Agent packages, and the key updater
packages to the system with McAfee ePO.
You can download McAfee Agent packages from McAfee ePO Software Catalog (or Software Manager on McAfee
ePO 5.9 or earlier). See McAfee ePO product documentation for more details.
McAfee Agent comes with different packages for each supported operating system.
Name Description
MA5xxLNX.zip Linux package
MA5xxWIN.zip Windows package
MA5xxMAC.zip Macintosh package
MA5xxWIN_Embedded.zip Windows Embedded Credentials package
help_ma_5xx.zip McAfee ePO Help extension
EPOAGENTMETA.zip McAfee ePO extension
AgentKeyUpdate.zip Key updater package
When upgrading from McAfee Agent 4.8 Help extension to 5.0, uninstall the agent 4.8 Help extension then
perform steps a through d to install 5.0 Help extension.
3 For each agent package you need to check in to the McAfee ePO repository:
a Select Menu | Software | Master Repository.
b Click Check In Package, then browse to the agent packages list, select the required package, then click Next.
c Make sure that Current is selected under Branch, then click Save.
If you have not yet created the System Tree groups, you can deploy the McAfee Agent installation package to
systems when you add groups and systems to the System Tree. But, if you are importing large domains or
Active Directory containers, don't use this method. It generates significant network traffic.
• The user must have local administrator rights on all target systems. Domain administrator rights are
required on a system to access the default Admin$ shared folder. McAfee ePO service requires access to this
shared folder to install McAfee Agent.
The ability to successfully use ping commands from McAfee ePO to managed systems is not required for
McAfee Agent to communicate with the server. But it is a useful test to determine if you can deploy McAfee
Agent to those client systems from McAfee ePO.
• The Admin$ share folder on Windows target systems must be accessible from McAfee ePO. Verify that this is
true on a sample of target systems. This test also validates your administrator credentials, because you
cannot access remote Admin$ shares without administrator rights.
From McAfee ePO, click Windows Start | Run, then type the path to the target system's Admin$ share,
specifying system name or IP address. For example, type \\<System Name>\Admin$.
If the systems are properly connected over the network, and your credentials have sufficient rights, and the
Admin$ share folder is present, a Windows Explorer dialog box appears.
• Enable SSH on the Linux and Macintosh client systems before installing McAfee Agent from McAfee ePO.
Comment out the following line in the /etc/sudoers file on a Red Hat operating system.
Default requiretty
PermitRootLogin Yes
You must have root permissions to install McAfee Agent on non-Windows systems.
• Temporarily disable the user account control on client systems to push McAfee Agent from McAfee ePO.
The push deployment feature can install McAfee Agent on many systems at the same time. You can only install
a single version of McAfee Agent on a client system.
Task
Options Definition
Choose Columns Opens the Choose Columns page where you select the columns to display
on the Agent Deployment page.
Create Agent Deployment URL Opens the Agent Deployment URL page where you create a URL for Agent
Deployment.
Delete Agent Deployment URL Deletes the selected Agent Deployment URL.
Enable/Disable Agent Deployment Controls whether the client system users can deploy the agent using the
URL URL.
Export Table Displays the Export page where you choose the way the table is exported.
View Agent Deployment URL Displays the Agent Deployment URL.
Clicking the McAfee Smart Installer prompts you to save or run the executable file. The managed system users
with administrator rights can run the executable file and install McAfee Agent on their system. Running the
executable on the client system extracts McAfee ePO details and McAfee Agent unique token.
Once the executable is extracted, the client system tries to discover peer-to-peer servers in its broadcast
domain to download the McAfee Agent installation and configuration files. On receiving the request, the McAfee
Agent that is configured as peer-to-peer server responds to the request and serves the content.
If the client system is unable to find peer-to-peer servers in its broadcast domain, it tries to connect McAfee
ePO to download the configuration files. If the connection succeeds, the client system downloads and installs
McAfee Agent.
If the installer is unable to connect to McAfee ePO directly, it uses the proxy server setting configured on the
client system to download and install McAfee Agent. The installer uses the proxy server settings configured in
Internet Explorer for Windows or System Preferences for Macintosh OS X client systems.
Download using proxy server is supported only on Windows and Macintosh operating systems. For Macintosh
client systems, the installer uses System Preferences. You must provide the proxy server credentials if your client
system requires authentication to connect to the proxy server.
If the client system fails to connect to McAfee ePO directly or using the proxy server, it broadcasts a message to
discover McAfee Agent with relay capability in its network. The RelayServer responds to the message and
establishes connection with the client system.
If McAfee Agent package download fails due to network connectivity problems, McAfee Agent resumes
downloading the remaining installation files from the point it stopped when the McAfee Smart Installer runs
next time.
(McAfee ePO On-Premises) McAfee Agent then installs other McAfee products through the deployment tasks
and enforces new policies assigned to the managed system fetched during the first agent-server
communication.
While creating the McAfee Smart Installer, you can also set McAfee Agent or the other McAfee products to
update automatically. If you select other McAfee products to be included in the installer, a deployment task is
created to install the product. These products are then installed after the first agent-server communication.
Task
1 Select Menu | Dashboards, then on the Getting Started pane, click Customize Installation.
4 If you want McAfee Agent or the other McAfee products to be updated automatically, select Software is
automatically updated to the latest version.
5 Click Done, then follow the on-screen instructions to download and install McAfee Agent.
The install.zip file cannot be downloaded from the FTP or UNC servers.
Task
1 Click the URL or copy and paste it into a browser.
Enter the complete URL without any space, in the browser.
1 When prompted, download the installer. Or, click Install to download and install
McAfee Agent.
2 In the File Download dialog box, click Run.
3 Click Run to confirm installation. A dialog box shows the progress of the installation.
The installation log McAfeeSmartInstall_<date>_<time>.log is saved in
<LocaltempDir>\McAfeeLogs.
For Macintosh When prompted, download the installer. The customized URL downloads the
McAfeeSmartInstall.sh file.
McAfee Agent 5.6.6 and later versions provides the McAfeeSmartInstall.sh installer
file for Smart Installer. However, McAfee Agent doesn't support the launch of
McAfeeSmartInstall.sh through remote console.
• Open Terminal, then switch to the location where you have downloaded the
McAfeeSmartInstall.sh file.
• Run the following commands:
sudo chmod +x McAfeeSmartInstall.sh
sudo ./McAfeeSmartInstall.sh
For other • Run McAfee Agent installer from the folder where it is downloaded.
supported <McAfeeSmartInstall.sh>
non-Windows
operating The installation log McAfeeSmartInstall_<date>_<time>.log is saved in the folder
systems
where you downloaded McAfee Agent installer.
No two agents can share the same GUID. The most common way McAfee Agent ends up with duplicate GUIDs is
if it was installed on an image without having its GUID removed, and that image was deployed onto more than
one system.
To make sure the GUIDs are not duplicated, run this command on the system image where McAfee Agent is
installed and is used to deploy on more than one client systems.
Restart the McAfee Agent service on your system after running the maconfig -enforce -noguid command to
generate a unique GUID.
Task
• Run the following command on the client system with any of these parameters:
On Windows, run McAfeeSmartInstall.exe
On Macintosh, run McAfeeSmartInstall.sh
On Linux, run McAfeeSmartInstall.sh
To know more about using command-line switches with McAfee Agent, see KB52707.
Parameter Description
‑d "Data path" Overrides the path of McAfee Agent data files (Windows only). The default location
is: <Documents and Settings>\All Users\Application Data\McAfee
\Agent. If the operating system does not have a Documents and Settings
folder, the default location is C:\ProgramData\McAfee\Agent.
Example: McAfeeSmartInstall.exe ‑d D:\McAfeeAgent\Data
‑i "Install path" Overrides the default folder where installation files are saved (Windows only). You
can use Windows system variables, such as <SYSTEM_DRIVE>. If not specified, the
default location is: <DRIVE>:\Program Files\McAfee\Agent.
Example: McAfeeSmartInstall.exe ‑i D:\McAfeeAgent
‑a "Proxy Specifies the proxy server address and the port number (Windows and Macintosh
address" ‑p only).
"Proxy port" If the proxy server details are not provided, the installer uses the default browser
proxy server setting.
‑k Switches off the peer and certificate verification of the https server from where the
installer downloads the configuration file.
‑u "Proxy user Specifies the user name and password for the authenticated proxy server (Windows
name" ‑w "Proxy and Macintosh only).
password"
‑f Forces McAfee Agent installation (Windows only).
‑s Installs McAfee Agent in silent mode (Windows and Macintosh only).
‑v Installs McAfee Agent in VDI mode.
‑h Uninstalls the existing agent and installs a new agent while retaining the Agent
GUID. (Windows only)
Example: McAfeeSmartInstall.exe ‑h
All parameters are optional. If you don't specify a parameter, the installer uses the default value.
Installing McAfee Agent in VDI mode deprovisions the virtual image or the system every time it shuts down. This
enables McAfee ePO to save the deprovisioned McAfee Agent in its database. Once deprovisioned in the
database, McAfee Agent is not displayed on McAfee ePO console.
Task
2 Next to How to add systems, select Create and download agent installation package.
On McAfee ePO Cloud, type a name for the URL and click OK to generate the Agent Deployment URL.
4 Select or deselect Embed Credentials in Package. If selected, type the appropriate Credentials for agent installation.
If you want these credentials to be remembered the next time you complete this task, click Remember my
credentials for future deployments.
5 If you want the deployment to use a specific Agent Handler, select it from the drop-down list. If not, select All
Agent Handlers.
6 Download McAfee Agent and copy the installer on the virtual image.
8 To verify if McAfee Agent was installed in VDI mode, select Menu | Systems | System Tree, then select the
system.
The System Information page displays the properties of the client system reported by McAfee Agent. The value
of the system property VDI should be Yes.
McAfee Agent starts the agent-server communication and enforces all policies and tasks as configured on
McAfee ePO.
• Copy the customized McAfee Smart Installer to download and install agent manually on the managed
systems.
Tasks
• Install from McAfee ePO on page 28
You can install the agent on multiple systems at the same time using McAfee ePO. All such systems
should be running on the same operating system.
• Install manually on page 29
Manually install the agent on client systems, using the FramePkg.exe installer.
• Install using third-party deployment methods on page 29
Installing the agent using third-party deployment methods requires an installation package created
for that environment.
• Install with logon scripts on page 30
In environments where the client systems log on to the network, use network logon scripts to install
the agent.
• Install with custom installation packages on page 32
Use custom installation packages to install the agent on systems that are not managed by McAfee
ePO.
• Install using Group Policy Object on page 34
Configure your third-party software, such as Microsoft Group Policy Objects (GPO), to distribute the
agent installation package, which is on your McAfee ePO.
This method is recommended if large segments of your System Tree are already populated. For example, if you
created System Tree segments by importing domains or Active Directory containers, and you chose not to deploy
McAfee Agent during the import.
You can only install one version of McAfee Agent on one type of operating system with this task. If you need to
install on multiple operating systems or versions, repeat this task for each additional target operating system or
version.
Task
1 Select Menu | Systems | System Tree, then select the groups or systems where you want to deploy McAfee
Agent.
3 Select the appropriate Agent version drop-down list given the target operating system, and select a version
from that list.
If you use the force installation option, the existing McAfee Agent is removed in its entirety, including policies,
tasks, events, and logs, before the new McAfee Agent is installed.
5 To change the installation path from the default, enter the target path in the Installation path option.
6 Type valid credentials in the Domain, User name, and Password and Confirm password fields.
If you want these entries to be the default for future deployments, select Remember my credentials for future
deployments.
7 If you do not want the default values, enter values in the Number of attempts, Retry interval, and Cancel after
options.
8 If you want the deployment to use a specific Agent Handler, select it from the drop-down list. If not, select All
Agent Handlers.
9 Click OK.
The Server Task Log page appears with the Deploy McAfee Agent task listed.
Install manually
Manually install the agent on client systems, using the FramePkg.exe installer.
If you want users (with local administrator rights) to install McAfee Agent on their own systems, distribute the
installation package file to them. You can attach it to an email message, copy it to media, or save it to a shared
network folder.
Task
1 Copy the installation package, FramePkg.exe, from your McAfee ePO to a shared folder on a network
server accessible by the target system.
2 On the target system, navigate to and right-click FramePkg.exe, select Run as administrator, and wait a few
moments while McAfee Agent is installed.
Systems where McAfee Agent is installed manually are located initially in the Lost & Found group of the McAfee
ePO System Tree.
After McAfee Agent is installed, it calls into the server and adds the new system to the System Tree.
Task
d Deselect Embed Credentials in Package to receive the default package. Otherwise, specify the required
credentials.
e If you want the deployment to use a specific Agent Handler, select it from the drop-down list. If not,
select All Agent Handlers.
f Click OK.
2 To embed credentials on systems not belonging to a domain, change the local security policy on the target
systems.
a Log on to the target system using an account with local administrator rights.
b From the command line, run SECPOL.MSC to open the Local Security Settings dialog box.
c From the Security Settings | Local Policies, select User Rights Assignment.
d In the Policy column of the details pane, double-click Impersonate a client after authentication to open the Local
Security Policy Setting dialog box.
e Click Add User or Group to open the Select Users or Groups dialog box.
f Select the user or group that the user is likely to run as, then click Add.
g Click Add.
You are now ready to use your third-party software to distribute the installation package, FramePkg.exe.
By default User Access Control is enabled on Windows Vista and later operating systems. The administrator must
add permission to the user or turn off User Access Control to install the agent manually on client systems.
• See your operating system documentation for writing logon scripts. The details of the logon
script depend on your needs. This task uses a basic example.
• Create a batch file (ePO.bat) that contains commands you want to execute on systems when
they log on to the network. The content of the batch file depends on your needs, but its purpose
is to check whether McAfee Agent has been installed in the expected location and, if not, run
FramePkg.exe to install McAfee Agent. Below is a sample batch file that does this. This example
checks the default installation folder for McAfee Agent files and, if not present, installs the
McAfee Agent.
@ECHO OFF
SETLOCAL
set MA_KEY_NAME="HKEY_LOCAL_MACHINE\SOFTWARE\McAfee\Agent"
set MA_VALUE_NAME=InstallPath
• You already have a managed environment and want to make sure that new systems logging
on to the network become managed as a result.
• You already have a managed environment and want to make sure that systems are running
a current version of McAfee Agent.
Task
1 Copy McAfee Agent installation package, FramePkg.exe, from your McAfee ePO to a shared folder on a
network server, where all systems have permissions.
Systems logging on to the network are automatically directed to this folder to run McAfee Agent installation
package and install McAfee Agent. The default location for the installation packages for Windows is:
<Program Files>\McAfee\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3000\Install
\0409\FramePkg.exe. Embedded credential package always runs in silent mode and does not display any
error message when an installation fails.
2 Save the batch file you created, ePO.bat, to the NETLOGON$ folder of your primary domain controller (PDC)
server.
The batch file runs from the PDC every time a system logs on to the network.
3 Add a line to your logon script that calls the batch file on your PDC server.
For example: CALL \\<PDC>\NETLOGON$\EPO.BAT
Because an installer package created for this purpose has embedded credentials, access to it should be severely
restricted. Installer packages with embedded credentials should only be used in specific situations where another
deployment method is not available. For additional, important information about the use of embedded
credentials, see KB65538.
Task
2 Next to How to add systems, select Create and download agent installation package.
4 Select or deselect Embed Credentials in Package. If selected, type the appropriate Credentials for agent installation.
If you want these credentials to be remembered the next time you complete this task, click Remember my
credentials for future deployments.
5 If you want the installer to use a specific Agent Handler, select it from the drop-down list. If not, select All
Agent Handlers.
6 Click OK.
7 When prompted, select the file to be downloaded. Click to open the file, or right-click to save the file.
Use these command-line options with the deployment task to upgrade to a new version of McAfee Agent.
This table describes McAfee Agent installation command-line options. These options are not case sensitive.
FramePkg.exe and FrmInst.exe require administrator rights, so they must be run from an administrator
command prompt or configured to always run as administrator.
Command Description
/Customprops Allows you to set custom properties.
Example:
FRAMEPKG /INSTALL=AGENT /Customprops1="prop1" /Customprops2="prop2" /
Customprops3="prop3"
/DATADIR Specifies the folder on the system to store McAfee Agent data files. The default location is:
<Documents and Settings>\All Users\Application Data\McAfee\Agent. If the
operating system does not have a Documents and Settings folder, the default location
is C:\ProgramData\McAfee\Agent.
Example: FRAMEPKG /INSTALL=AGENT /DATADIR=D:\AgentData
/DOMAIN Specifies a domain, and account credentials used to install McAfee Agent. The account
/USERNAME must have rights to create and start services on a system. If left unspecified, the
credentials of the currently logged-on account are used. If you want to use an account
/PASSWORD that is local to a system, use the system’s name as the domain.
Example:
FRAMEPKG /INSTALL=AGENT /DOMAIN=mydomain.com /USERNAME=jdoe /
PASSWORD=password
Example:
FRAMEPKG /INSTALL=UPDATER
Command Description
/INSTALL=AGENT /Relay Allows the user to manually define the RelayServer
information, such as IP address or DNS name, to the client
system during the agent installation.
When the client system fails to connect to the McAfee ePO
server directly or using the proxy server, it communicates
using the RelayServer that is specified during the agent
installation.
Example:
FramePkg.exe /Install=Agent /
Relay="<IP1>:Port1[;<IP2>:Port2;...]"
/INSTDIR Specifies the installation folder on the system. You can use Windows system variables,
such as <SYSTEM_DRIVE>. If not specified, the default location is: <DRIVE>: \program
files\mcafee\Agent
Example: FRAMEPKG /INSTALL=AGENT /INSTDIR=C:\ePOAgent
/REMOVE Removes McAfee Agent if not in use. If in use, McAfee Agent changes to updater mode.
Example: FRMINST /REMOVE=AGENT
/RESETLANGUAGE Resets McAfee Agent language to its default operating system language.
/SILENT or /S Installs McAfee Agent in non-interactive mode, hiding the installation from the user.
Example: FRAMEPKG /INSTALL=AGENT /SILENT
/SITEINFO Specifies the folder path to a specific repository list (McAfee Agent installer, reqseckey
.bin (the initial request key), srpubkey.bin (the server public key), req2048seckey
.bin, sr2048pubkey.bin, Sitelist.xml file, and agentfipsmode file).
Example: FRAMEPKG /INSTALL=AGENT /SITEINFO=C:\TMP\SITELIST.XML
/USELANGUAGE Specifies the locale ID of McAfee Agent that you want to install. Use the switch to change
current McAfee Agent language to any supported language.
Example: FRAMEPKG /INSTALL=AGENT /USELANGUAGE=0404
If errors occur during installation, all error messages are displayed in English regardless of
the installed locale.
/keepguid Retains the Agent GUID during force installation. This command is used with
FramePkg.exe installation method.
Example: FramePkg.exe /Install=Agent /ForceInstall /keepguid
Use this command on McAfee Agent version 5.6.3 or later. This command is valid only
when it is used with the /ForceInstall option.
Task
1 Download Framepkg.exe from McAfee ePO to a shared folder on a network server, where all systems have
permissions.
• Sitelist.xml • sr2048pubkey.bin
• srpubkey.bin • req2048seckey.bin
• reqseckey.bin
3 Copy the extracted files to a shared UNC location specified in siteinfo path.
7 When prompted for a package, browse to the shared UNC path, then select MFEAgent.msi.
• McAfee Agent extension must be installed on McAfee ePO and appropriate packages must be
added to the Master Repository before installing McAfee Agent on a non-Windows system.
• Comment the following line in the /etc/sudoers file on a Red Hat operating system.
Default requiretty
The following non-Windows operating systems support installing McAfee Agent from McAfee ePO.
You can only install one version of McAfee Agent on one type of operating system with this task. If you need to
install on multiple operating systems or versions, repeat this task for each additional target operating system or
version.
Task
1 Select Menu | Systems | System Tree, then select the groups or systems where you want to deploy McAfee
Agent.
3 Select the appropriate Agent version drop-down list for the target operating system, and select a version from
that list.
4 Select Install only on systems that do not already have an agent managed by this McAfee ePO server.
5 Type valid credentials in the User name, Password, and Confirm password fields.
If you want these entries to be the default for future deployments, select Remember my credentials for future
deployments.
6 If you do not want the defaults, enter appropriate values into the Number of attempts, Retry interval, and Cancel
after options.
7 If you want the deployment to use a specific Agent Handler, select it from the drop-down list. If not, select All
Agent Handlers.
8 Click OK.
Task
• Copy the install.sh file directly from McAfee ePO. The path includes the name of the selected
repository. For example, if checked in to the Current branch of the McAfee ePO software repository, the
path of the required files is:
3 Open Terminal, then switch to the location where you copied the install.sh file.
To determine the version of McAfee Agent installed on a Macintosh system, see KB68746.
Task
2 Click New Systems, select Create and download agent installation package, choose the appropriate Agent version, click
OK, and save the agentPackages.zip file that contains the installdeb.sh file.
3 Open Terminal, then switch to the location where you copied the installdeb.sh file.
$chmod +x ./installdeb.sh
$sudo ./installdeb.sh -i
Contents
Install the agent on Red Hat Linux systems using third party deployment method
Install the agent on Ubuntu systems using third party deployment method
Install the agent on Red Hat Linux systems using third party deployment method
Install the agent on Red Hat Linux systems using third-party deployment methods with the help of an rpm
package created for that environment.
Task
2 Click New Systems, select Create and download agent installation package, choose the appropriate Agent version, click
OK, and save the agentPackages.zip file that contains the install.sh file.
3 Open Terminal, then switch to the location where you copied the install.sh file.
Make sure the rpm-build package is installed on the local system before generating MAProvision files. Run
the following command to check if it is already present.
rpm -q redhat-rpm-config
If the rpm-build package is not installed on the local system, run the following command to install.
If the unzip package is not installed on the local system, run the following command to install.
• Run the command, giving root credentials when requested. For example:
./install.sh -p
• Open Terminal, then switch to the location where you copied the install.sh file.
• The following installation files are available. Collect the files as needed.
• MFEma.i686.rpm
• MFEma.x86_64.rpm
• MFErt.i686.rpm
Use the appropriate MFEma package based on the operating system used. For example:
For a 64-bit operating system: Use MFEma.x86_64.rpm
• Open Terminal, then switch to the location where you copied the DXL.zip file.
• The following installation files are available. Collect the files as needed.
• MFEdx‑ma‑<build_number>.i686.rpm
• MFEdx‑ma‑<build_number>.x86_64.rpm
Use the appropriate MFEdx‑ma‑<build_number> package based on the operating system used. For
example:
For a 64-bit operating system: Use MFEdx‑ma‑<build_number>.x86_64.rpm
8 Install McAfee Agent in managed mode using third-party tools (for example, yum install
MAProvision.rpm).
Install the agent on Ubuntu systems using third party deployment method
You can generate a debian package and install the agent on Ubuntu systems using third-party deployment
methods.
Task
2 Click New Systems, select Create and download agent installation package, choose the appropriate Agent version, click
OK, and save the agentPackages.zip file that contains the install.sh file.
3 Open Terminal, then switch to the location where you copied the install.sh file.
• Open Terminal, then switch to the location where you copied the install.sh file.
• The following installation files are available. Collect the files as needed. From McAfee Agent 5.6.6
onwards, McAfee Agent includes version information in the filename.
• mfema‑<build_number>.i686.deb
• mfema‑<build_number>.x86_64.deb
• mfert‑<build_number>.i686.deb.
Use the appropriate mfema package based on the operating system used. For example:
For a 64-bit operating system: Use mfema‑<build_number>.x86_64.deb
• Open Terminal, then switch to the location where you copied the DXL.zip file.
• The following installation files are available. Collect the files as needed.
• mfedx‑ma‑<build_number>.i686.deb
• mfedx‑ma‑<build_number>.x86_64.deb
Use the appropriate mfedx‑ma‑<build_number> package based on the operating system used. For
example:
For a 64-bit operating system: Use mfedx‑ma‑<build_number>.x86_64.deb
8 Install McAfee Agent in managed mode using third-party tools (for example, apt-get install
maprovision.deb).
See also
Deploying the agent using McAfee Smart Installer on page 23
Install URL-based McAfee Agent manually from the command line on page 26
Install McAfee Agent in Virtual Desktop Infrastructure mode on page 27
Manage Agent Deployment URLs on page 23
When McAfee Agent 5.6.0 is installed on Windows systems in unmanaged mode, the DXL client is automatically
installed and is in idle state.
Task
1 Download and extract the McAfee Agent package (Example: MAxxxWIN.zip) to a temporary location.
3 On the target system, navigate to and right-click FramePkg_UPD.exe and select Run as administrator.
When McAfee Agent 5.6.0 is installed on non-Windows (rpm or debian, or Macintosh) systems in unmanaged
mode, the DXL client is installed automatically and is in idle state.
Task
1 Download and extract the McAfee Agent package (Example: MAxxxLNX.zip and MAxxxMAC.zip) to a
temporary location.
install_upd.sh is available in MAxxxLNX.zip and MAxxxMAC.zip.
When McAfee Agent 5.6.0 is installed on rpm systems in unmanaged mode, the DXL client does not get installed
automatically. Hence, the DXL client has to be installed manually.
Task
1 Download and extract the McAfee Agent package (Example: MAxxxLNX.zip) to a temporary location.
DXL.zip is available in MAxxxLNX.zip. Extract DXL.zip to get MFEdx‑ma‑<build_number>.i686.rpm and
MFEdx‑ma‑<build_number>.x86_64.rpm files.
• MFEma.x86_64.rpm • MFEdx‑ma‑<build_number>.x86_64.rpm
• MFErt.i686.rpm
Use the appropriate MFEma and MFEdx‑ma‑<build_number> packages based on the operating system used.
For example:
For a 64-bit operating system: Use MFEma.x86_64.rpm and MFEdx‑ma‑<build_number>.x86
_64.rpm
5 Run the following commands to install the agent on the client system:
• For a 64-bit operating system:
When McAfee Agent 5.6.0 is installed on debian systems in unmanaged mode, the DXL client does not get
installed automatically. Hence, the DXL client has to be installed manually.
Task
1 Download and extract the McAfee Agent package (Example: MAxxxLNX.zip) to a temporary location.
DXL.zip is available in MAxxxLNX.zip. Extract DXL.zip to get mfedx‑ma‑<build_number>.i686.deb and
mfedx‑ma‑<build_number>.x86_64.deb files.
• mfema‑<build_number>.x86_64.deb • mfedx‑ma‑<build_number>.x86_64.deb
• mfert‑<build_number>.i686.deb
Use the appropriate mfema and mfedx‑ma‑<build_number> packages based on the operating system used.
For example:
For a 64-bit operating system: Use mfema‑<build_number>.x86_64.deb and mfedx‑ma‑<build
_number>.x86_64.deb
5 Run the following commands to install the agent on the client system:
• For a 64-bit operating system:
When McAfee Agent 5.6.0 is installed on Macintosh systems in unmanaged mode, the DXL client does not get
installed automatically. Hence, the DXL client has to be installed manually.
Task
1 Download and extract the McAfee Agent package (Example: MAxxxMAC.zip) to a temporary location.
DXL.zip is available in MAxxxMAC.zip. Extract DXL.zip to get MFEdx‑ma‑<build_number>.i686.pkg and
MFEdx‑ma‑<build_number>.x86_64.pkg files.
• MFEdx‑ma‑<build_number>.i686.pkg
• MFEdx‑ma‑<build_number>.x86_64.pkg
Use the appropriate MFEdx‑ma‑<build_number> package based on the operating system used. For example:
For a 64-bit operating system: Use MFEdx‑ma‑<build_number>.x86_64.pkg
5 Double-click the appropriate MFEdx‑ma‑<build_number> package based on the operating system to install
the DXL client.
If you have an older version of the agent installed in your environment, you can upgrade to the latest version
when you install the latest version of McAfee ePO.
Periodically, McAfee releases newer versions of the agent that can be deployed and managed using McAfee
ePO. When the agent installation package and the extension are available, you can download it from the
McAfee download site or the Software Catalog (or Software Manager on McAfee ePO 5.9 or earlier) . Check in the
installation package to the Master Repository and install the new extension, then use the Product Deployment task to
upgrade McAfee Agent.
It is not mandatory to update McAfee Agent key updater when you upgrade McAfee Agent to a new version. If
needed, run the agent key updater task to get new keys.
You can create a customized McAfee Smart Installer to upgrade McAfee Agent on the client systems.
If you're using McAfee Agent 4.5.x or an earlier version, upgrade to 4.6.x or 4.8.x, then upgrade to 5.0.0. For
details about upgrading McAfee Agent to version 5.5.1 or later, see KB90642.
• When you upgrade the agent on the system where the agent and the DXL client are already present, the
agent and the DXL client are upgraded. Old DXL services are removed and DXL services run as part of
McAfee Agent services.
• When you upgrade the agent on an unmanaged system, the DXL client is in idle state.
If you are upgrading McAfee Agent on a Microsoft Windows system that has a DXL client version older than 2.1.0
(not including 2.1.0), you must first upgrade the DXL client to any DXL version between 2.1.0 and 4.1.0 before
upgrading the McAfee Agent. This does not apply to non-Windows systems.
Contents
Upgrading vs. updating
Upgrade the agent using Product Deployment task
Upgrade the agent manually
Methods of upgrading McAfee Agent in unmanaged mode
Restore a previous version of the agent on Windows systems
Restore a previous version of the agent on non-Windows systems
Upgrading means installing a newer version of McAfee Agent over an older version, for example, replacing
McAfee Agent 4.8 with McAfee Agent 5.0.0.
Updating means getting the most up-to-date DATs and signatures that products use to identify and disarm
threats.
• If you use McAfee ePO to deploy McAfee Agent in your network, the procedure differs slightly depending
which previous version of McAfee Agent you are upgrading.
• If you are upgrading your McAfee Agent and your network is large, consider the size of the installation
package file and your available bandwidth before deciding how many agents to upgrade at once. Consider
using a phased approach. For example, upgrade one group in your System Tree at a time. In addition to
balancing network traffic, this approach makes tracking progress and troubleshooting easier.
• (McAfee ePO On-Premises) If you use a product deployment client task to upgrade McAfee Agent, consider
scheduling the task to run at different times for different groups in the System Tree.
The procedure for upgrading depends on the version of McAfee Agent running on your managed systems.
Some previous McAfee Agent versions do not support all features in McAfee ePO 5.3.x. For full McAfee ePO
functionality, upgrade to McAfee Agent version 5.0.0 or later.
Upgrading McAfee Agent by a method other than using McAfee ePO, such as upgrading manually or using
network logon scripts, is identical to installing McAfee Agent for the first time.
Task
2 On the Assigned Client Tasks tab, click Actions | New Client Task Assignment to open the Client Task Assignment Builder
wizard.
3 Next to Task to Schedule, select McAfee Agent as Product, Product Deployment as Task Type, and select the existing
deployment task.
You can also create an upgrade task or view the properties of the existing deployment task by clicking Create
New Task or View Selected Task respectively. To define a new task, click Create New Task and enter the information
appropriate to the task you are creating.
During the agent upgrade on non-Windows operating systems, enter -r on the Command line to run macmnsvc
with root permissions. Make sure -u is prefixed with -r on the Command line.
4 Next to Lock task inheritance, you can choose to unlock or lock the upgrade task to allow or prevent breaking
inheritance.
5 Next to Tags, you can choose to send this upgrade task to all systems or specific systems that match the
expected criteria.
The upgrade task is sent to the selected client systems at the next agent-server communication. Every time this
task executes, it checks to determine whether to install the specified version of McAfee Agent.
Task
1 Copy FramePkg.exe, from your McAfee ePO to a shared folder on a network server accessible by the target
system.
By default, the FramePkg.exe installation package is at <System Drive>\Program Files
(x86)\McAfee\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3000\Install\0409.
The path includes the name of the selected repository. For example, if checked in to the Current branch of the
McAfee ePO software repository, the path of the required files is:
2 On the target system, navigate to and right-click FramePkg.exe, select Run as administrator, and wait a few
moments while McAfee Agent is upgraded.
Task
1 Download and extract the McAfee Agent 5.x.x Update X package (Example: MA550XWIN.zip) to a temporary
location.
Where “X” is the Update value of the package, such as McAfee Agent 5.5.0 Update 1.
3 Browse to the location of FramePkg_UPD.exe on the target system and type cmd to open the Command
Prompt.
Or, on the target system navigate to and right-click FramePkg_UPD.exe and select Run as administrator.
Task
1 Download and extract the McAfee Agent package (Example: MAxxxLNX.zip and MAxxxMAC.zip ) to a
temporary location.
install_upd.sh is available in MAxxxLNX.zip and MAxxxMAC.zip.
Task
1 Download and extract the McAfee Agent 5.x.x Update X package (Example: MA564XLNX.zip) to a temporary
location.
Where “X” is the Update value of the package, such as McAfee Agent 5.6.x Update 1.
• MFEma.x86_64.rpm • MFEdx‑ma‑<build_number>.x86_64.rpm
• MFErt.i686.rpm
Use the appropriate MFEma and MFEdx‑ma‑<build_number> packages based on the operating system used.
For example:
For a 64-bit operating system: Use MFEma.x86_64.rpm and MFEdx‑ma‑<build_number>.x86
_64.rpm
This process supports upgrading an unmanaged McAfee Agent from version 4.8.0 to version 5.x.x.
Task
1 Download and extract the McAfee Agent 5.x.x Update X package (Example: MA564XLNX.zip) to a temporary
location.
Where “X” is the Update value of the package, such as McAfee Agent 5.6.x Update 1.
• mfema‑<build_number>.x86_64.deb • mfedx‑ma‑<build_number>.x86_64.deb
• mfert‑<build_number>.i686.deb
Use the appropriate mfema and mfedx‑ma‑<build_number> packages based on the operating system used.
For example:
For a 64-bit operating system: Use mfema‑<build_number>.x86_64.deb and mfedx‑ma‑<build
_number>.x86_64.deb
Task
1 Download and extract the McAfee Agent 5.x.x Update X package (Example: MA550XMAC.zip) to a temporary
location.
Where “X” is the Update value of the package, such as McAfee Agent 5.5.0 Update 1.
• MFEdx‑ma‑<build_number>.i386.pkg
• MFEdx‑ma‑<build_number>.x86_64.pkg
Use the appropriate MFEdx‑ma‑<build_number> package based on the operating system used. For example:
For a 64-bit operating system: Use MFEdx‑ma‑<build_number>.x86_64.pkg
Task
1 Select Menu | Systems | System Tree, then select the systems where you want to install a previous version of
the agent.
3 From the Agent version drop-down list on the Deploy Agent page, select the agent you want to restore, then do
the following:
a Select Force installation over existing version.
d Provide the information for Number of attempts, Retry interval, and Cancel after.
e Select whether the connection used for the deployment is to use a specific Agent Handler or All Agent
Handlers.
Task
1 On the client system, uninstall the currently installed version of the agent.
Tasks, policies, and other data is restored at the first agent-server communication following reinstallation.
When you select Remove McAfee Agent on next agent-server communication while deleting a system from the System
Tree, McAfee Agent is removed from the system during the next agent-server communication.
If managed products still reside on systems after trying to remove McAfee Agent, it continues to run
unmanaged in updater mode to maintain those managed products.
You cannot remove McAfee Agent using the Product Deployment task.
• On Windows systems, when the agent mode changes from managed to updater, during the agent removal,
the DXL client does not get uninstalled from the client system.
Contents
Remove agents when deleting systems from the System Tree
Remove agents when deleting groups from System Tree (Windows only)
Remove agents from systems in query results
Remove the agent using Windows command line
Remove the agent in unmanaged mode using Control Panel
Remove the agent using non-Windows command line
Task
1 Select Menu | Systems | System Tree, then select the group with the systems you want to delete.
2 Select the systems from the list, then click Actions | Directory Management | Delete.
3 Select Remove McAfee Agent on next agent-server communication, then click OK.
Remove agents when deleting groups from System Tree (Windows only)
You can remove McAfee Agent from a group of systems when you delete that group from System Tree.
When you delete a group, all its child groups and systems are also deleted.
Task
2 At the bottom of the System Tree panel, click System Tree Actions | Delete Group.
3 Select Remove McAfee Agent on next agent-server communication from all systems, then click OK.
Task
1 Run a query, then from the results page, select the systems to be deleted.
2 Select Directory Management from the drop-down list, then select Delete from the submenu.
3 Select Remove McAfee Agent on next agent-server communication, then click OK.
Task
1 Open a command prompt on the target system.
2 Run the agent installation program, FrmInst.exe, from the command line with the /REMOVE=AGENT
option.
If there are managed McAfee products installed on the client system already, the agent continues to run in
the updater mode. In this scenario, the DXL client does not get uninstalled.
To remove the agent forcibly from the Windows client system, run the command FrmInst.exe /
FORCEUNINSTALL. In this scenario, the DXL client gets uninstalled automatically. If the agent is still not
removed, remove the agent manually. For details, see KB65863.
In this scenario, the DXL client gets uninstalled automatically. The agent removal using Control Panel is not
allowed in managed mode.
Task
If there are McAfee products installed on the client system already, the agent continues to run in the updater
mode. In this scenario, the DXL client does not get uninstalled.
• Removing the system names from the McAfee ePO System Tree.
Task
2 Run the command for your operating system to remove the agent from the system. Provide root credentials
when requested.
Debian /opt/McAfee/agent/scripts/uninstall.sh
You can also use below commands to remove individual packages.
dpkg --purge mfedx
dpkg --purge mfecma
dpkg --purge mfert
Mac /Library/McAfee/agent/scripts/uninstall.sh
3 On McAfee ePO, select Menu | Systems | System Tree, then select the systems where you uninstalled McAfee
Agent.
4 From the Actions drop-down list, select Directory Management, then select Delete from the submenu.
A F
agent FRAMEPKG.EXE 20
removal methods 55, 56
removing from systems in query results 56 G
restoring a previous non-Windows version 54 global unique identifier (GUID)
restoring a previous Windows version 53 duplicate 25
system requirements 17 groups
uninstalling 56 deleting from System Tree 56
upgrading with phased approach 48 GUID, See global unique identifier
agent distribution
FrmInst.exe command line 56 I
agent installation
installation script (install.sh) options 41
command-line options 32
creating custom packages 32
L
from an image 25
manually on Windows 29 Locale IDs, settings for installation 32
on non-Windows 36 Logon scripts
on Windows via push technology 28 install the agent via 30
package, location of 20, 30
uninstalling 56 N
update packages 48 non-Windows
using logon scripts 30 agent package file name 36
agent upgrade 47, 48 installing the agent on 36
agent-server communication
interval, (ASCI) 25
O
operating systems
C
McAfee Agent 17
command-line options
agent installation 32
P
FrmInst.exe 56
credentials packages
required for agent installation 32 agent file name, for non-Windows 36
creating custom for agent installation 32
push technology
D
initial agent deployment via 28
Data Execution Prevention (DEP) 17
deployment
Q
push technology via 28
upgrading agents 48 queries
removing agents in results of 56
E
extension files
non-Windows, agent package file name 36
R U
removal uninstallation
agent, from UNIX systems 57 agent, from Macintosh OS 57
requirements agent, from UNIX systems 57
operating systems 17 UNIX
processors 17 uninstalling the agent from 57
updates
S agent installation packages 48
upgrading agents 48
scripts, logon for agent installation 30
user accounts
Smart Installer 24
credentials for agent installation 32
system requirements 17
System Tree
deleting systems from 55 V
removing agents 56 virtual image
removing agents from systems 55 non-persistent 27
T
troubleshooting
upgrading agents by group 48