Methods of deploying McAfee Agent

You can deploy the agent to client systems using different methods.

Use this table to choose the suitable method.

Method Action Notes
McAfee ePO You specify the systems and select one of the Push Agents options when adding a system, or Deploy Agents for systems already in the System Tree.
  • Selecting many systems can temporarily affect network throughput.
  • You must specify credentials with administrator rights to the target systems.
Manual (using the FramePkg.exe installer) You manually install the agent on each managed system.
  • Allows for information such as custom properties to be added on an individual system basis.
  • Once McAfee Agent is installed, use McAfee ePO to upgrade products and update product content.
Third-party software such as Microsoft Systems Management Server (SMS), Microsoft Group Policy Objects (GPO), or IBM Tivoli Configure your third-party software to distribute McAfee Agent installation package, which is on your McAfee ePO.
  • McAfee Agent installation package contains needed security keys and the Sitelist.xml file.
  • See the instructions that come with your third-party tools.
Logon scripts (Windows only) You create an installation or upgrade script, which runs at each logon to a system.
  • The user must log on to the system to trigger the installation or upgrade.
  • The installation package must be in a location accessible to the system.
Customized McAfee Smart installer You create a customized McAfee Smart installer and distribute it to managed system users for manual installation.
  • The managed system users must have administrator rights to install McAfee Agent manually.
  • Enabling peer-to-peer servers helps reduce load on McAfee ePO.
  • Once McAfee Agent is installed, assigned policies and client tasks are enforced on the managed system.
Deployment task Use McAfee ePO System Tree to upgrade McAfee Agent on selected target systems.
  • McAfee Agent must already be present on the target system.
  • Enabling peer-to-peer servers helps reduce load on McAfee ePO.
An image with McAfee Agent You remove McAfee Agent GUID using the command-line switch, then create an image that contains McAfee Agent and deploys the image.
  • Removing the GUID allows McAfee Agent to generate a new GUID on the first agent-server communication.
  • Failure to remove the GUID results in "sequencing errors" from multiple identical systems.
Unmanaged McAfee products on Windows systems Using the System Tree, you select systems to be converted from unmanaged status to managed status and select ActionsAgentDeploy Agents.
  • McAfee Agent must already be present on the target system in unmanaged mode.
Unmanaged McAfee products on non-Windows platforms Type the following command on the system with McAfee Agent that you want to convert from unmanaged to managed:

<agent install path>/bin/maconfig -provision -managed -dir <Path of location containing agentfipmode, srpubkey.bin, reqseckey.bin, sr2048pubkey.bin, req2048seckey.bin, Sitelist.xml>

  • You must have root permission to perform this action.
  • You must use the srpubkey.bin, reqseckey.bin, sr2048pubkey.bin, req2048seckey.bin, and Sitelist.xml files from McAfee ePO.