Allow the agent to communicate with the handler on the ePO server. This option may not always be feasible, depending on the environment.

When the agent has successfully communicated once, it's given a new Sitelist.xml file. The file contains the Remote Agent Handlers, according to the AH priority assignment rules configured on the ePO server. 

Reinstall MA on the client. This option always overwrites the existing Sitelist.xml file with the default sitelist, which contains all available AHs.

When the agent has successfully communicated once, it's given a new sitelist. The new file contains the Remote Agent Handlers, according to the AH priority assignment rules configured on the ePO server.

Several methods can be used to deploy an agent to a client. They're documented in the "Deploy agents to your systems to be managed" section of the ePO 5.10 Installation Guide.

1. On the ePO server, navigate to the following folder:
   
   C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Software\Current\ePOAgent3000\Install\0409
    
2. 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
      
3. Open a command prompt.
4. Navigate to the following location:
   
   C:\Program Files\McAfee\Agent
    
5. Run the following command:
   
   maconfig.exe -provision -managed -directory_location
   
   Here, directory_location is the location of the exported Sitelist.xml file and security keys.
    
6. 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 AH. So, when the agents try to connect to the ePO Server, they're redirected to the Remote AH that they can access.