cancel
Showing results for 
Search instead for 
Did you mean: 

Computername is changing in EPO 3.6.1

I have this strange phenonimon that by time the name of 2 servers in my epo directory are changing from name, the servers name are icts-s-xxx-n1 and icts-s-xxx-n2. On both machines the CMA client has been installed, epo installed VS8.5i.
Now I see only 1 of the machines with the green flag, the other does nog give any information in the properties. Whenever I send a agent wake up call to the machine that has no properties and I refresh the screen after some time the names are changed in the Epo console, also the properties change. I get the same thing when sending the information by the cmdagent.exe on the client servers.
In the server.log file I see this info:



20080523162449 I #3420 EPOServer Receiving Agent public key from ICTS-S-XXX-N1
20080523162449 I #3420 EPOServer Computer Name has changed: Old Name = ICTS-S-XXX-N2; New Name = ICTS-S-XXX-N1
20080523162449 I #3420 EPOServer GUID has changed: Old GUID = 47DE07CB-987E-49AB-9BBC-1027059E277F; New GUID = F22B48D4-ED19-4B7C-8311-24747165AC52
20080523162449 I #3420 EPOServer DAL added agent public key for {F22B48D4-ED19-4B7C-8311-24747165AC52}(ICTS-S-XXX-N1) successfully!
20080523162449 I #3420 EPOServer Sending props response for agent ICTS-S-XXX-N1, policy files attached (EvtFiltr.ini,Policy\Server.xml)

Why is epo doing this, it are 2 different machines.
I already reinstalled the CMA agent on the servers but it is no solution.
4 Replies
gmc_za
Level 8
Report Inappropriate Content
Message 2 of 5

RE: Computername is changing in EPO 3.6.1

RE: Computername is changing in EPO 3.6.1

thanks for the reply but this is not the awnser as I already checked this out. You can also see in the logfile info that the GUID is different.

RE: Computername is changing in EPO 3.6.1

Strange thing is that I have the same problem on an other Epo machine that is on the production domain, previous was on the test domain.
Highlighted

RE: Computername is changing in EPO 3.6.1

The problem is due to the use of NLB, for the solution see https://knowledge.mcafee.com/SupportSite/search.do?cmd=displayKC&docType=kc&externalId=KB45372&slice... 0 30888473
More McAfee Tools to Help You

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community