Probably the easiest approach is to include the agent in the image - make sure that you remove the agentguid registry value from the registry before taking the image. That way when the machine is reimaged it will get a new GUID, but as long as its MAC address stays the same ePO will be able to match the newly-imaged machine to the existing entry in the database, and the result from your point of view will be a seamless transition with no point at which the machine is unmanaged.
How many total client nodes are you managing?
Machines that are re-imaged; are you aware/notified that a machine is being rebuilt or are they showing up as "inactive" or ??
Go to the registries on clients pc HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK ASSOCIATES and delete agent guid and mac address and also
delete the keys folders and then deploy agents and then it shall work well.
deleting keys folder is not necessay , try deleting agent guid and mac address and then try if it fails then delete keys folder also try .
i faced this kind of issue earlier and i just did the same and it worked well for me
Thank you for all the answers.
The situation has changed a little... we will be moving to a new Hyper-V environment in which I want to install a new EPO 4.5 server from scratch The guest OS will be Server 2008 R2. The challenge is, to let the all client (when they are imported/discovered) agents talk to the new server.
So, the agent has to be updated on all clients to point to the new server.
Does anyone has experience with this?
You might want to read this KB70685 before starting installing anything.
tnx redbaron, finally a statement from McAfee regarding this.
I already decided to do a new install and not migrate anything.
Also I found the answer to my question, as to how to point the client agents to the new EPO server: https://kc.mcafee.com/corporate/index?page=content&id=KB66892