Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have recently been given Administrative rights to help maintain ePO on my companies network. From the group of machines that I am in charge of keeping up-to-date, a small amount of these machines do not have the proper McAfee Product information displayed in ePO.

I have remoted into these machines manually and checked the version numbers for these Products (VSE, Policy Auditor, HIPS, DLP, etc.) and they all list the most up-to-date information for those products, (example, HIPS I then open up the McAfee Agent Status Monitor Console and select "Collect and Send Props", "Send Events", "Check New Policies" and "Enforce Policies" to ensure that the agent is able to communicate with the ePO server without throwing out any error messages. Everything seems to register fine. When I log back into ePO and check the computer name in System Tree, the computer still shows an outdated version of that product number (HIPS, for example).

I have tried to tag these systems with Uninstall/Reinstalls to fix the issue, and it worked on two machines, but there is still at least 20 machines that are not registering properly! I've tried this several different times over the course of a week now, giving plenty of time (at least 24 hours) between the uninstall and reinstall but the issue still remains in ePO.

I've done some searching online and see that other people have been suffereing from this same problem (link), but the only "solution" that has been repeated over and over was to uninstall/reinstall, which like I said before, is not working for some of my machines.

Any advice would be much appreciated.

share|improve this question
What version of McAfee Agent and also which version of ePO are you using? What is the "last communication time" for the system in question, Does ePO acknowledge the ASCI? – Schlauge Jul 27 '13 at 0:56
My apologies for the extremely late reply: I'm using currently for all of my machines. For the majority of those machines, they have a check-in time of (today's date). Obviously one or two have agent issues, but, for the majority seem to be communicating properly. They register that tags have been applied for install, but after the install completes it does not reflect the installed software on the server side. – Michael H Jun 30 '15 at 17:59
Please note: in the answer that I provide below, it ignores the part about the install/uninstall tag "trick" not working. This is because I had to perform very specific actions to get it to work (monitoring the agent closely to ensure it didn't throw out error messages or fail to communicate entirely after a short while). Additionally, sometimes it just...doesn't work and needs to be redone from the beginning several times in order to check in properly. – Michael H Jun 30 '15 at 18:37
up vote 0 down vote accepted

I haven't found a full answer to the question I have asked, but for anyone who might be struggling with the same issue:

A temporary work around is to harass the ePO server until it complies with the request. If you have more then 3 to 5 machines being affected by this issue, I would recommend doing this in very small batches, as it can affect network performance significantly.

  1. Ensure you can check the agent log either through the web interface on ePO or by RDPing into the affected asset(s). You need to watch the progress being made on the agent to ensure that a "failure" state is not being reported. I.e. "(HIPS install tag) has been applied and will be updated at (scheduled time)." followed closely behind by "Agent failed to update (HIPS version number)"

  2. Remove any Install or Uninstall tags that might be currently applied to the affected machine(s). Ensure that the agent reports that the tags have been removed. If it does not report this, there could be a communication problem between the agent and the server that can be fixed by manually uninstalling the McAfee Agent: frminst.exe /forceuninstall

  3. Tag the affected machines with an uninstall tag for the specific product (HIPS or Policy Auditor, for example). Again, ensure the agent reports the uninstall tag has been applied and will be performed on the next update.

  4. Select the machine(s) and choose "Wake Up Agents". I leave the defaults on "Agent Wake-up Call", 0 minutes, Get full product properties, 0 attempts, 30 seconds retry (automatically retries after failing), abort after 5 minutes.

  5. Watch the agent log. After a minute or two you should see activity being reported back. If this doesn't happen, it should be safe to assume there is a problem with the agent or the machine is having network connectivity problems.

  6. Chose the machine(s) and run: Actions -> Agent -> Update Now.

  7. Again, watch the logs for a few minutes. If there were remnants of the product, you should see messages confirming that the tag successfully removed it.

  8. Clear the uninstall tag.

  9. Run Wake Up Agents and Update Now again to ensure the uninstall tag has been removed completely.

  10. Tag the machine(s) for the install tag and repeat again with "Wake Up Agents", you should see a similar report to Step 3 about it being applied on the next update. Run "Update Now".

  11. If you are lucky, the agent should register that the tag has been applied and the product has been successfully installed. Refresh ePO and it should now list having that product installed. If it does not, wait a few minutes and refresh ePO again. If it's still not listed, do steps 1-11 again until it changes.

Typically, I have to do 3 to 4 cycles of all of the above steps to get the machines to react properly. I don't know why this occurs the way it just does.

If you check the machine's "About" listing individually, it will probably properly list the product, but it wont be listed in ePO. I don't know WHY it doesn't list in ePO, I just know that constantly forcing ePO to acknowledge the product being uninstalled/reinstalled manages to fix it. Sometimes.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.