Transferred System only Attempting communication with ePO

[Former Member]

We are trying to build out a Mcafee environment for us and all our clients. There will be one ePO with each client site with an Agent Handler installed. The agent handlers can commucanite with the single ePO directly, but the workstations can not. This is based on the requirement that we keep our clients domains/networks completely separated. 

My issue is when we transfer systems and push a wake agent on the transferred system, the only agent handler listed in the agent settings is the single ePO server and none of the Agent Handlers that have priority for their OU or IP subnet. Is there a way to ensure that transferred systems know which agent handlers they need to comm with?

At the moment we are transferring systems, then pushing a agent deploy from their respective agent handlers but we'd rather automate the process more. Especially for the encrypted workstations.

Thanks,

Michael

[jappell]

I thought that you might find the following article helpful.

https://kc.mcafee.com/corporate/index?page=content&id=KB71865&pmv=print

[Former Member]

Hey Jappell,

Thanks for the reply.

I don't think that Kb pertains to my issue however.

The transferred systems can't communicate with the new ePO, but the new ePO is the only Agent Handler listed in their settings initially upon transfer. Since the systems can't comm with the new ePO its also not getting a list of Agent Handlers it should be communicating with. 

I was hoping there was a way to manually set the agent handler prior to transferring. Would altering the sitelist.xml do this? 

[cdinet]

When you registered the new epo server you are transferring to, did you choose to automatically download sitelist, or import sitelist?  If you chose automatic, export the sitelist from the new epo server and verify the agent handlers are listed in it.  Then import it and see if that helps.

[jappell · Accepted solution]

Here is a short post I made earlier this year. See if it helps you dot the i's and cross some t's.

1. Register the source keys with the destination ePO server.

2. Register the destination keys with the source ePO server.

3. Take the sitelist from: Source ePO server >  import to Destination ePO server (do this manually as I have not had reliable results with automatically obtain sitlist.xml.)

4. Take the sitelist from: Destination ePO server > import to Source ePO Server (do this manually)

Anything other than these steps make it an inconsistent implementation of "transfer". Now the only caveat here is that all of my implementation of transfer has been with previous versions of 5.x. I have heard it is "more automated" now but I am not clear what that means. Share what you learn and I'll look forward to hearing how you do.

There is only so much iunformation we can provide remotely to help. The devil is in the details and I would open a ticket for a deeper understanding of what might have been missed or overlooked.

Jay

[Former Member · Accepted solution]

Hey Jappell,

Setting the sitelist import to manual and importing the sitelist from the new ePO is what finally worked for me. This forced all 3 agent handlers to be used upon system transfer. Prior to this only the ePO server was showing up after system transfer.

Thanks for everybody's help!

[jappell]

Glad to help!