ip address for System Name has changed and EPO can't connect

[User64044111]

Our pcs are on DHCP and the ip address can change on a re-boot. How do I get the EPO to communicate to the new ip address for policy updates?

[YashT]

Hello @User64044111 

There is an option to change the agent communication method.

EPO> Menu > Server Settings> Agent Contact Method.

Keep IP address in last position, so from next time agent will be communicating to EPO based on FQDN or Netbios name, once connected it will update its information to new IP address.

[YashT]

Hello @User64044111 ,

One More thing I want to add here:  

If the ip is changed then it will be automatically updated when the client systems communicates to EPO.

If we are doing a wake up agent then only we have to make changes to server settings in agent communication method because that determines the priority of methods that the McAfee ePO server will use when attempting to contact a McAfee Agent (applies to Push Agent, Agent Wakeup, and Show Agent Log actions).

Client will be communicating with EPO with their Agent guide and Epo server information.

[cdinet]

As @YashT pointed out, you really don't need to do anything.  The agents will report their new IP on next asci.  You don't need to do wakeups either to get them to report it, they will communicate on their scheduled asci interval.

[User64044111]

The information provided is exactly  how the system is set up, and yet the agent is still not connecting to my pc and updating the ip address in the EPO system.   

[cdinet]

That isn't a dhcp problem then, but an agent communication issue.  See KB90603 for how to troubleshoot agent-server communication issues.

[User64044111]

Thank you.  I did find that the pc name had been changed.  I started a new task with the new name of the pc and I am watching for the completion status to change.  So far 0%.  

[cdinet]

What type of task?  Does the new system name show up in epo?

[User64044111]

I selected new system and used the correct name of my pc.   Then I did a new deployment to my correct pc name.  In reading other cases, I see I did not do a Force Update.  My deployment is still at 0%.

[cdinet]

What specifically are you deploying?  If the agent is failing to communicate, that run client task now type thing won't work, as it can't send a response back to epo.  You need to first fix the communication failures.  If the agent was communicating properly, you shouldn't have to add the system to the system tree by new name, it should add itself on next asci.