MA can be installed on an image that is later deployed to multiple systems. You must take precautions to make sure that the agent functions properly in this scenario.
MA includes a Globally Unique Identifier (GUID). The GUID must be unique for each system in your environment. The most common way that multiple systems have duplicate GUIDs is when MA is installed on a primary image without having the GUID removed.
Duplicate MA GUIDs can cause following problems:
- Agents from newly deployed systems do not populate in the ePolicy Orchestrator (ePO) System Tree.
- Agents do not appear to report to the ePO server.
- Clients do not receive correct policies.
- Clients disappear from the ePO console.
- Clients overwrite the same system object in the ePO System Tree.
To ensure that MA GUIDs are not duplicated, run the following command on the primary system image.
NOTE: The primary image is the image where MA is installed for deployment on client systems:
maconfig -enforce -noguid
On non-Windows operating systems, the command is case sensitive and you must run the command with root permission using sudo. For example:
sudo /Library/McAfee/agent/bin/maconfig -enforce -noguid
The GUID is regenerated the next time the agent is started. So, it is important to run this command
immediately before you create your system image. If you do not do so, a new GUID might be assigned before the system image is created.
The
MAconfig file is a command-line tool provided with MA for Windows and non-Windows operating systems. It is installed with MA, and its default location is:
- Windows: You can find the agent in one of the following directories:
NOTE: The location depends on whether the agent was upgraded from MA 4.x, or is a fresh installation.
- C:\Program Files\McAfee\Agent\
- C:\Program Files\McAfee\Common Framework\
- C:\Program Files (x86)\McAfee\Common Framework
- Linux: /opt/McAfee/agent/bin/
- Apple OS X: /Library/McAfee/agent/bin/
