
Epo clients / virusscan DAT out of date
(1)
The reporting feature has seemed to always be a little out of whack, however now the entire system is out of whack. I have rebuilt a new server, and I know part of the problem is the GUID, due to the ghosted systems being deployed out in our network, for some reason the client support team didnt remove the agent from the image.
If you have the ePO agents running with the same GUID, you can try to generate it again. I had the same problem, and I created a scrip which performed the following steps:
1. stop ePO agent
2. Remove the AgentGUID key in
'HKLM\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent'
3. Start the ePO agent
When the ePO agent starts, it generates a new AgentGUID. Then you just have to wait for the agent to connect to the ePO server, or force a wakeup call at the end of your script.
Regards
Rajiv
(2) === ePO GUID issues
Hi,
This is a issue even I faced.
I made a separate group of machines which I knew were not displaying in the ePo server as updated. I performed a ePO server to client force install of the ePO clients. Gradually i got all the clients to the ePO fold.
Also if you check the clinets locally.. they would be getting updated from the designated repositories. it is only that they wont appear on the ePo console. If they would appear also.. they would appear momentarily and would vanish soon.
To avoid issues with duplicate GUID's: just befor imaging
1. Open the registry editor
2. Navigate to Go to HKEY_LOCAL_MACHINE--SOFTWARE--Network Associates--ePolicy Orchestrator--Agent
Delete the AgentGUID and reboot the machine.When rebooted the machine gets an other GUID from the ePO Server
Pull the machine out of the network and go ahead making the image. The next time the machine starts( Or when loaded to a new machine) the ePo agent would contact the ePo server and would obtain a new GUID.
Reply With Quote
Solution
IMPORTANT: These instructions are intended for use by ePO administrators only.
Step 1 - Verify the issue:
1.
Click Start, Run, type regedit then click OK.
2.
Compare the agent GUIDs on the affected client computers: if the GUIDs are the same, then this is the cause of the problem. An agent's GUID is stored as the data of the AgentGUID registry value:
[HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent\AgentGUID]
NOTE: The agent GUID is ePO primary method of uniquely identifying a computer. Matching AgentGUID values affect the process used when computers check in, prevent properties from being recorded correctly, and prohibit policy enforcement. For additional information on ePO Agent GUID creation and how it is used by the ePolicy Orchestrator server, refer to 8078252.
Step 2 - Resolve the issue:
On each affected client computer, delete the AgentGUID registry value and restart the McAfee Framework Service
1.>> Click Start, Run, type regedit then click OK.
2.>>Navigate to the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent\]
3.>> Right-click the AgentGUID value and select Delete.
4.>>Click Registry, Exit.
5.>>Click Start, Run, type services.msc then click OK.
6.>> Right-click McAfee Framework Service and select Restart.
Alternative Step 2 solution:
An alternative option is to reinstall the Common Management Agent (CMA), using the /forceinstall switch. This can cause issues with earlier versions of CMA. For more information on the Common Management Agent issue using the /forceinstall option, see 835619.
Reinstall the agent, by doing either of the following:
*
Installing the agent from the command line using the /forceinstall switch. For more information on this switch see the Agent Installation Command-Line Options section of the ePO Product Guide
*
Send an agent installation to the machine ensuring that you have selected Force Install over existing version.
For future deployments:
The ePO agent Global Unique Identifier (GUID) is created when the Framework service starts with the AgentGUID value missing. Usually this happens when the Framework is started during installation. Running SysPrep or changing the name of the client computer does not dynamically change this value. The information for including the ePO agent in an image is located in the Deploying Agents, Super Agents, and Sensors chapter under the Other ways to deploy the agent section of the ePO Product Guide.
Before creating the final image delete the AgentGUID value from the registry.
Cause
\The computers were imaged and deployed with the same AgentGUID and/or MACADDRESS registry value.