Computers on your network are part of a workgroup or a domain?
They are all on a Domain. They are on a few different subnets though.. One machine, I can't ping from the Agent Deployment UI, even though a simple ping from my machine (which is on a different subnet than the machine, but same IP as the EPO server) resolves.
Firewall turned off (temporarily), and network discovery turned on
I don't know how your network admin do the upgrade to epo 5.3 ( keep the same name is not enough to do successful upgrade) Agent - > server keys must be imported also.
I think is better to deploy new agent on your network.
I've been trying that every few days, but there are some machines that just fail to have an agent pushed to them. Is there a log to where I can read the exact reason it failed?
Before deploying new agent u can ask from your network admin to :
- Download and install Rogue systems detection (RSD) module on Epo
- Deploy RSD sensor on some computers of your network ( For ex : 1 computer /sybnet)
- Register the AD server on Epo server
- Synchronize your epo with your AD
You can use Epo automatic Répnse to deploy Mcafee Agent.
using CMD can you ping those machines ? ( by name and by ip ) ?
The actual Agent deployment tasks should have some logs to indicate why the deployments failed, but you will often find more useful logs on the client side (primarily Windows event logs).
Are you sure that the account you're using is an administrator on the target systems in question? Is the situation improved if you uninstall the Agent from one of those systems, and *then* try to push from ePO?
^ Yes. I'm using a domain admin account, which by default is on every machine on the network, unless someone is smart enough to go in and remove it from the Admin group on the machine.
What sucks is I can't remove the agent, because it can't talk to the server. This is where the managed mode becomes a real PITA sometimes. No easy way for me to remove the agent. There really should be some sort of uninstall tool, that can be downloaded from the EPO that has a special key to allow uninstallation during these events.
Failure to force-install the McAfee agent over an existing copy happens to us occasionally.
The cause is invariably that the "C:\ProgramData\McAfee\Common Framework\MFEAgent.msi" file does not match the release version of "C:\Program Files\McAfee\Common Framework\FrameworkService.exe", and thus the old agent uninstall fails. Copying in the right MFEAgent.msi into the PrgogramData\McAfee\Common Framework directory fixes this.
But I guess that Access Protection might be turned on preventing modification of key McAfee files, which makes your task nigh on impossible.