Does anyone know how to get servers to report to the console. The services were restarted, and the servers were restarted, but they will now show up in the console. Is there a command that can be run to make the agents on the server report back to the ePO console?
Solved! Go to Solution.
Hi DJones,
Execute the below command to initiate ASCI from client machine. What is the ePO version are you using. Ensure you have relevant Agent version checked in.
/opt/mcafee/agent/bin/cmdagent -p
Switch | Description |
-p | Collect and send properties to the ePO server |
-e | Enforce policies locally |
-c | Check for new policies. The agent contacts the ePO server for new or updated policies, then enforces them immediately on receipt. |
-f | Forward events to the ePO server |
-i | Display McAfee Agent information |
-h | List all switches with their description |
-l | Set the location of the log file |
Was my reply helpful?
If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a Solution" if this reply resolves your query!
Hi DJones,
Execute the below command to initiate ASCI from client machine. What is the ePO version are you using. Ensure you have relevant Agent version checked in.
/opt/mcafee/agent/bin/cmdagent -p
Switch | Description |
-p | Collect and send properties to the ePO server |
-e | Enforce policies locally |
-c | Check for new policies. The agent contacts the ePO server for new or updated policies, then enforces them immediately on receipt. |
-f | Forward events to the ePO server |
-i | Display McAfee Agent information |
-h | List all switches with their description |
-l | Set the location of the log file |
Was my reply helpful?
If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a Solution" if this reply resolves your query!
Thanks for the reply, but this didn't work for us. Can it be a policy issue?
Did you check the logs I gave you to look at? Without knowing what errors there are, we can only guess. There are many reasons for communication failures. Since communication is a 2-way street, you need to look at both server and client logs.
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?
Good Afternoon. I don't have access to the logs, but I am trying to get access to the server to look at those log.
If you at least have access to the agent logs, that is the first error to look at, whether it is even reaching the server or not. The masvc log will show it failing in 2 manners. Either it can't get there at all for one reason or another, or it gets a response back from server that possibly rejects the agent for some reason, or some firewall in between. That log will give you a lot of clues.
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?
We had to do the wake up agent from the client server, after deleting the RHEL6 agent on it.
They should connect back on their own. You would need to look at the masvc log on the client to see what errors there might be for connecting to epo. That is located in /var/McAfee/agent/logs folder. Depending on the error also, you might want to check the server log on the epo server or agent handler the system is talking to for same time frame of communication attempt. Those are located in epo install directory db\logs.
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?
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA