Showing results for 
Show  only  | Search instead for 
Did you mean: 

ePO communication with FQDN and low DNS release time.

Hello everybody,

i have much trouble with a customer environment. All systems hold the IP´s for 14 days.

The default ePO priority setting for wakeup is 1. FQDN, 2. IP, 3 NetBIOS Name.

If there is a client offline for 3 weeks and i want to wake him up, in the first attempt it failed with FQDN, then the ePO tries the IP and wake up the wrong system because of the last known IP. The task writes successfully, but it doesn´t. I had wake up a wrong system.

What to do now? I can´t delete the option "wake up over IP", i can only change the priority. And in the last step, the ePO wake up the wrong system again.

Or is there an other way to handle it? I think it must be an known problem. I have no permisson to change the DNS release time.



3 Replies
Report Inappropriate Content
Message 2 of 4

Re: ePO communication with FQDN and low DNS release time.

That sounds more like dns isn't refreshing the new IP's of the systems.  In epo server settings, agent contact method, you can change the order that epo contacts the agents.  You can put the IP last.  If you find a system being woke up to the wrong IP, do an nslookup for that system name - is it resolving correctly?

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: ePO communication with FQDN and low DNS release time.

Hello cedinet,

the most errors comes up, if i want to wake up an no more existing server. At first the ePO didn´t find an DNS entry, because it is older then 2 weeks and/or AD object is delted.

After this, the ePO tries the IP that had switched 2-3 times since the last contact and an other system showes up as online.

I will clear all old objekts, perhaps i dond´t have issues after this.

thank you


Report Inappropriate Content
Message 4 of 4

Re: ePO communication with FQDN and low DNS release time.

Hello @Kundenservice ,

If the wake up call is triggered to the system which is no longer available, it will fail.

Now as the ip which the old system was using is already assigned to other system then the wake up will pass and update the client system information in EPO.

The systems which is no longer there can be removed with a default McAfee query "Inactive Agents" which will give you details on "McAfee Agents that have not communicated with the McAfee ePO server in the last 30 days."   you can duplicate this query and modify the time frame based on your requirement and then delete the systems, this way it will be faster to remove the unwanted systems and re-arrange the epo system tree.

Was my reply helpful?
If you find this post useful, Please give it a Kudos! l Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

Thanks and regards,
Yash T
You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from product experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by employees.
Join the Community
Join the Community