is this under rdp?
the M only shows in a console session of RDP not others (unless you start it sepcifically), by design
yes it is through rdp, although it is a console connected via rdp.
Out of curiosity, why has it been designed to only display on a console session?
so you dont get dozens of instances of the same thing running i assume
Have you got a solution for this as this just recently occured on our system.
But there is no difference between dozens of instances of mcshield icon or dozens of instances of the agent icon and the mcshield icon displays in every rdp session.
In our environment agent icon disappears only on x64 systems (but this is a known bug, should be resolved in mcafee agent 4.5)
Only draw back is that it was working before.
Now the M only seems to be on the workstation but not the server based machine.
Did you manage to find a solution for this?
A year later and I seem to have the same issue. It's an annoyance, I can see the changes I make to the policy being applied but I'd be much more comfortable if I saw the Agent icon rather than the VSE one... It causes me to second guess whether or not a server is being managed or has been installed standalone.
This is happening to us as well accross our entire network. The ePO server is claiming to be communicating to the 4.5 agents, but in the agent logs, it is failing...
When this happens on our workstations, the VSE icon goes away and is replaced with the MA Red icon, which also causes a loss of focus if the user is typing, so it is extremely annoying. The updates continue to work, but the machines are unreachable for a good portion of every day.
Here is what is logged on the server for example;
7/13/10 9:21:31 AM Starting agent wakeup for NNNNN 7/13/10 9:21:31 AM Waking up agent NNNNN.DOMAIN.NAME using DNS name 7/13/10 9:21:31 AM Unknown error contacting agent 7/13/10 9:21:31 AM Waking up agent NNNNN using NetBIOS 7/13/10 9:21:31 AM Unknown error contacting agent 7/13/10 9:21:31 AM Waking up agent at IP address X.X.X.X 7/13/10 9:21:31 AM Unknown error contacting agent 7/13/10 9:21:31 AM Wakeup agent failed
It is disheartening to see that McAfee has issues like these that stick around for years, as if nobody is using their products!