cancel
Showing results for 
Search instead for 
Did you mean: 
apoling
Level 14
Report Inappropriate Content
Message 1 of 3

Auto GUID regeneration does not seem to happen

Hello,

we have an ePO 4.5 patch 3 system with McAfee Agent 4.0 P3 and 4.5 P1 (number of the latter is growing) clients. We have been having the classic duplicate agentGUID problems on quite a few systems. I was aware of the fact that with the new ePO 4.5 system and agents with versions listed above are eligible and capable of doing this guid regeneration automatically so no manual intervention was needed. I just did not know why this is not happening.

So to find out the details on how to resolve this in the new environment quickly, we had a support chat session with McAfee , and we made known that we need to enable a server task so that many of these guid duplicates can be resolved automatically. KB article 67473 details these server tasks.

According to this information, once a Duplicate Agent GUID - remove systems with potentially duplicated GUIDs task is run, the GUID will also be marked as "problematic" and "as a result the agent is forced to generate a new GUID". Very good.

We enabled this server task and run it, too.

Now we have an example in which auto guid regeneration does not seem to happen. The client has MA 4.5 P1, has a duplicate GUID and as a result of running the above server task, was removed from system tree but never since tried to regenerate its own guid and never appeared again in the system tree.

All we see in the agent debug log when doing an ASCI is similar to this:

2010-11-30 13:44:14 I #2016 naInet HTTP Session initialized
2010-11-30 13:44:14 I #2016 imsite Connecting to site: <removed> on port: 443
2010-11-30 13:44:14 I #2016 naInet HTTP Session closed
2010-11-30 13:44:14 I #2016
Agent Agent communication failed, result=-2147467259
2010-11-30 14:06:00 I #228 LstnSvr CAsyncSocket:Smiley Very HappyoAccept for event: FD_ACCEPT
2010-11-30 14:06:00 E #228 Logging isAgentEnabled GUID query error 2
2010-11-30 14:06:00 I #280 LstnSvr 'GET' request received from Host: <removed>:28994
2010-11-30 14:06:00 I #228 LstnSvr CAsyncSocket:Smiley Very HappyoAccept for event: FD_ACCEPT
2010-11-30 14:06:00 E #228 Logging isAgentEnabled GUID query error 2
2010-11-30 14:06:00 I #316 LstnSvr 'GET' request received from Host: <removed>:28995
2010-11-30 14:06:46 I #228 LstnSvr CAsyncSocket:Smiley Very HappyoAccept for event: FD_ACCEPT
2010-11-30 14:06:46 E #228 Logging isAgentEnabled GUID query error 2
2010-11-30 14:06:46 I #280 LstnSvr 'GET' request received from Host: <removed>:28997

The higlighted error is listed in KB under a different reason.

I would be grateful is someone could describe me what is really should take place when such a server task is run and what to expect from a client that has support for such auto guid regeneration.

Why is that not happening automatically ? What is that we are missing?

Thank you in advance for any useful piece of advice.

Attila

Message was edited by: Attila Polinger on 11/30/10 2:33:13 PM CET
2 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: Auto GUID regeneration does not seem to happen

Check the server.log for the corresponding time - is anything listed?

HTH -

Joe

apoling
Level 14
Report Inappropriate Content
Message 3 of 3

Re: Auto GUID regeneration does not seem to happen

Checking today's status on client and server:

Client:

2010-12-01 06:59:26 I #2024 Agent ASCI is not done yet ...Please wait for ASCI!
2010-12-01 06:59:26 I #2016 Agent Collecting IP address using Internet Manager
2010-12-01 06:59:26 I #2016 naInet HTTP Session initialized
2010-12-01 06:59:26 I #2016 imsite Connecting to site: <removed> on port: 443
2010-12-01 06:59:26 I #2016 naInet HTTP Session closed
2010-12-01 06:59:26 I #2016 Agent Agent communication failed, result=-2147467259
2010-12-01 07:10:48 I #228 LstnSvr CAsyncSocket:Smiley Very HappyoAccept for event: FD_ACCEPT
2010-12-01 07:10:48 E #228 Logging isAgentEnabled GUID query error 2

ePO Server:

20101201070658 I #3864 NAIMSRV  Processing agent props for D102049MOL({2BC917C0-A7FF-4FC7-BDDF-B3C8AF45602A})
20101201070658 I #3864 NAIMSRV  Sending props response for agent D102049MOL, policy files attached (Policy\Server.xml)
20101201070658 I #3864 mod_epo  Signing agent response package with key HMW9L9yM2AbJY8qrvmNCNJpYXAI=
20101201070659 I #3832 mod_eporepo Received request, uri=/Software/SiteStat.xml, remoteIP=10.65.8.32
20101201070659 I #4328 mod_eporepo Received request, uri=/Software/Current/VSCANENG1000/Engine/0000/PkgCatalog.z, remoteIP=<removed>
20101201070700 I #4200 mod_eporepo Received request, uri=/Software/SiteStat.xml, remoteIP=<removed>
20101201070700 I #0316 mod_eporepo Received request, uri=/Software/SiteStat.xml, remoteIP=<removed>

...

20101201070709 I #1852 mod_epo  Signing agent response package with key HMW9L9yM2AbJY8qrvmNCNJpYXAI=
20101201070710 I #4356 NAIMSRV  Received [PropsVersion] from D102712MOL:{E3798FA6-4989-4752-BA52-786501395059}
20101201070710 I #4356 mod_epo  Signing agent response package with key HMW9L9yM2AbJY8qrvmNCNJpYXAI=
20101201070710 I #3744 NAIMSRV  Received [PropsVersion] from L755637:{B3F59BD4-6C14-4158-B24C-CBEABED0E4B4}
20101201070710 I #3744 mod_epo  Signing agent response package with key HMW9L9yM2AbJY8qrvmNCNJpYXAI=
20101201070710 I #4180 NAIMSRV  Received [PropsVersion] from D59166:{E39D948A-0074-46A6-96CA-A46323EBD9CE}
20101201070710 I #4180 mod_epo  Signing agent response package with key HMW9L9yM2AbJY8qrvmNCNJpYXAI=
20101201070710 I #4152 NAIMSRV  Received [IncProps] from EXPLDT211:{9F42ACD9-0D42-4650-A6BD-685D939F63CA}
20101201070710 I #4152 NAIMSRV  Processing agent props for EXPLDT211({9F42ACD9-0D42-4650-A6BD-685D939F63CA})
20101201070710 I #0320 NAIMSRV  Received [IncProps] from D102712MOL:{E3798FA6-4989-4752-BA52-786501395059}
20101201070710 I #0320 NAIMSRV  Processing agent props for D102712MOL({E3798FA6-4989-4752-BA52-786501395059})

Attila