DubberDan
asked on
McAfee ePO agent problem
Some of the pc's on my network aren't talking to my McAfee ePO server. They are picked up as being on the network by ePO but the agent is never installed to them. I've manually installed the agent (by copying framepkg.exe to the c: of the pc) and I can log on to http://pc-ip-address:8081 and get a log file up. But it's having problems connecting to the server:
15 January 2007 15:41:41 Info Agent Agent communication session started
15 January 2007 15:41:41 Info Agent Agent is sending PROPS VERSION package to ePO server
15 January 2007 15:41:41 Info Agent Agent is connecting to ePO server
15 January 2007 15:42:05 Error Internet Manager Failed to connect to server j83040-2k3.xgp-j83040.nhs. uk. Check the agent log for more details.
15 January 2007 15:42:05 Error Agent Agent failed to communicate with ePO Server
15 January 2007 15:42:05 Info Agent Agent communication session closed
15 January 2007 15:42:05 Info Agent Next communication retry in 522 seconds
Any suggestions?
15 January 2007 15:41:41 Info Agent Agent communication session started
15 January 2007 15:41:41 Info Agent Agent is sending PROPS VERSION package to ePO server
15 January 2007 15:41:41 Info Agent Agent is connecting to ePO server
15 January 2007 15:42:05 Error Internet Manager Failed to connect to server j83040-2k3.xgp-j83040.nhs.
15 January 2007 15:42:05 Error Agent Agent failed to communicate with ePO Server
15 January 2007 15:42:05 Info Agent Agent communication session closed
15 January 2007 15:42:05 Info Agent Next communication retry in 522 seconds
Any suggestions?
Hi dubberdan,
I see that frequently because some of my admins have no clue about re-naming workstations.
Depending on which screen you're looking at in ePO, you may have to drill down to the properties of these boxes to compare the 'Network Name' to the name registered in ePO.
I'm on the wrong computer right now, but I have a simple batch command I can post that will help you track down proper names.
Post back when you can.
Vic
I see that frequently because some of my admins have no clue about re-naming workstations.
Depending on which screen you're looking at in ePO, you may have to drill down to the properties of these boxes to compare the 'Network Name' to the name registered in ePO.
I'm on the wrong computer right now, but I have a simple batch command I can post that will help you track down proper names.
Post back when you can.
Vic
Another thing that you can try is changing the logging level of the ePO agent. Go to HKLM\Software\Network Associates\ePolicy Orchestrator and change the logging level to 8. This will give you a lot more detail in the agent log, which should help in diagnosing the issue. Can you post the detail from c:\documents and settings\all users\application data\network associates\common framework\db\agent_<PCNAME >.log around the error and will see if we can help.
ASKER
his has not been forgotten, it's just there have been more pressing things at work. Will look into it soon and report back
ASKER
It's looking like the problem is being caused by multiple pc's with the same SID as they were supplied from an image. I'm now in the process of sorting out new SIDs for them which will hopefully resolve the issue.
BTW - make sure you thank whoever did that to you.
You may have to go to (or remote into) each of those boxes - after the SID fix - and force it to 'Check In' with your ePO server.
Use your 'Reporting' function to track which box 'names' are checking in.
Then drill down in the ePO 'Properties' of that box to make sure that the ePO name and the Network name of that computer match up.
Been there too many times to count.
Vic
You may have to go to (or remote into) each of those boxes - after the SID fix - and force it to 'Check In' with your ePO server.
Use your 'Reporting' function to track which box 'names' are checking in.
Then drill down in the ePO 'Properties' of that box to make sure that the ePO name and the Network name of that computer match up.
Been there too many times to count.
Vic
One other thing you may need to do is to updated the registry key for the agent.
You will need to delete the registry key
HKLM/Software/Network Associates/ePolicy Orchestrator/Agent/GUID
Then restart the agent. Otherwise you will end up with 1 object in the directory that will be constantly updated.
You will need to delete the registry key
HKLM/Software/Network Associates/ePolicy Orchestrator/Agent/GUID
Then restart the agent. Otherwise you will end up with 1 object in the directory that will be constantly updated.
ASKER
Thanks for the comments folks.
Yep, will be using the NewSID app, just gotta find the time to do it, hopefully next week, but if not then the week after most likely.
I'll watch out for those gotchas ;-)
Yep, will be using the NewSID app, just gotta find the time to do it, hopefully next week, but if not then the week after most likely.
I'll watch out for those gotchas ;-)
It would sure be nice for the Author to check back for a status update.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER