Agents receive a sitelist that contains only the handler information after ePO 5.10.0 Update 7 installation

Technical Articles ID: KB93131
Last Modified: 9/28/2020

Environment

McAfee ePolicy Orchestrator (ePO) 5.10.0 Update 7

Problem

Some clients have a Sitelist.xml file that includes only the ePO server. All remote Agent Handlers are missing from the sitelist.

If these clients can't communicate with the ePO server, the agent-server communications fail.

On the client, the McAfee Agent McTray Information section only contains the ePO server information. No remote Agent Handlers are listed.

Cause

The Agent Handler has received agent properties, from which it can't interpret the agent version correctly. The Agent Handler then sends back a sitelist with only one entry for the Primary ePO Server address. Only one entry is sent because older versions of the McAfee Agent only support one Agent Handler.

Solution

ePO 5.10 Update 8 prevents the issue, by not sending out a new sitelist under that condition.

This issue is resolved in ePO 5.10.0 Update 8, which is available from the Product Downloads site.

NOTE: You need a valid Grant Number to access the update.

To view other known and resolved issues, see KB90382 - ePolicy Orchestrator 5.10.x Known Issues.

Workaround

Replace the Sitelist.xml file:

On the ePO server, navigate to the following folder:

C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Software\Current\ePOAgent3000\Install\0409
Copy the following files to a temporary folder on the client. For example, C:\ePOTemp:
- srpubkey.bin
- reqseckey.bin
- sr2048pubkey.bin
- req2048seckey.bin
- agentfipsmode
- Sitelist.xml
Open a command prompt.
Navigate to the following location:

C:\Program Files\McAfee\Agent
Run the following command:

maconfig.exe -provision -managed -directory_location

Where directory_location is the location of the exported Sitelist.xml file and security keys
Do one of the following:
- Send the exported files from the ePO server c:\ePOTemp to the clients.
- Use a Pointer to direct the ePO IP_Address/host_name to the Agent Handler. So, when the agents try to connect to the ePO Server, they are redirected to the Remote Agent Handler that they can access.

Related Information

See also KB92747 where the same issue was reported with ePO 5.10 Update 1 and 2.

Affected Products

ePolicy Orchestrator 5.10.x
Known Issue/Product Defect

Languages:

This article is available in the following languages:

English United States
Spanish Spain
French
Italian
Japanese
Portuguese Brasileiro
Chinese Simplified

Knowledge Center

Agents receive a sitelist that contains only the handler information after ePO 5.10.0 Update 7 installation

Environment

Problem

Cause

Solution

Workaround

Related Information

Affected Products

Languages:

Title

Title

Knowledge Center

Agents receive a sitelist that contains only the handler information after ePO 5.10.0 Update 7 installation

Environment

Problem

Cause

Solution

Workaround

Related Information

Affected Products

Languages:

Choose your region

Title

Title