Specifications

Confirm you deleted the agent GUID before freezing the image
If you choose option 1, Include the agent in your Windows image it can cause one of the most
common problems seen in ePolicy Orchestrator, not resetting the Agent GUID. This causes the systems
to not appear in the ePolicy Orchestrator directory.
To solve this problem, you must make sure you delete the agent GUID before freezing the image when
you make the agent part of your image. If this registry key is not deleted, countless machines will use
the same GUID. This has a very negative effect in your environment. See McAfee ePolicy Orchestrator
4.5 Product Guide and McAfee KnowledgeBase article KB56086.
Failure to delete the McAfee Agent GUID from the registry before finalizing your image can be difficult
to manage in larger environments because there may be several imaging teams involved or an
outsourcing organization building the images. Make sure your imaging teams understand how to follow
the procedure outlined in KB56086. If you have a suspicion that there is a duplicate GUID problem in
your environment, see Determining if you have a duplicate GUID problem.
McAfee Agent
Deploying agents
6
McAfee
®
ePolicy Orchestrator
®
4.0 and 4.5 Best Practices Guide
49