1 Reply Latest reply on Jan 26, 2014 11:32 PM by hem

    ePolicy not detecting Agent


      I installed ePolicy 5.1 on one of my servers and McAfee Agent on another and syncronized the System Tree to the Active Directory domain they are both part of (By the way, is there a way to do this using the WebAPI?), but the server with the Agent on it is still listed as Unmanaged after repeated Wake Up attempts 



      I have confirmed that the McAfee Framework service is running on the target server, so the Agent is running.


      The error I get in the Server Task Log is:


      1/24/14 9:17:36 AM  Waking up agent Testbed2 using NetBIOS 

      1/24/14 9:17:36 AM  Unexpected HTTP response code 500 received from remote computer 

      1/24/14 9:17:36 AM  Wakeup agent failed 

      1/24/14 9:18:16 AM  Expired. The task will be stopped. 


      Message was edited by: apnelson - Added Server Task Log on 1/24/14 11:32:06 AM CST
        • 1. Re: ePolicy not detecting Agent

          If the machine is showing 'unmanaged' then wakeup agent will not work.


          If you already have McAfee agent installed on the client machine then what if you intiaited agent server communication from the client machine (CmdAgent.exe /s and click on the tabs 1-collect and send props, 2- enforce policies etc). Do you see any error message there? If communicating successfully to the ePO server then please look for the duplicate entry for the machine in the ePO server.

          1 of 1 people found this helpful