Skip navigation
McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams
2199 Views 7 Replies Latest reply: Sep 17, 2013 7:53 AM by pboedges RSS
Ron Wintrob Newcomer 24 posts since
Aug 16, 2011
Currently Being Moderated

Sep 17, 2013 2:21 AM

changing ePo server name in site list XML

hi every everyone .

do anyone know how can i redirect the McAfee Agent 3.6 to a new ePo server with a difarent ip and name?

  • Laszlo G Veteran 1,213 posts since
    May 23, 2007
    Currently Being Moderated
    1. Sep 17, 2013 2:46 AM (in response to Ron Wintrob)
    Re: changing ePo server name in site list XML

    Hi Ron, I think the easiest way would be deploying McAfee Agent from your new ePO server to this computer so it will be automatically managed by it.

     

    Also be advised that McAfee Agent 3.6 was end of life some years ago so you should consider to upgrade at least to McAfee Agent 4.6

  • Laszlo G Veteran 1,213 posts since
    May 23, 2007
    Currently Being Moderated
    3. Sep 17, 2013 3:02 AM (in response to Ron Wintrob)
    Re: changing ePo server name in site list XML

    Hi Ron, you can do this by modifying the ePOServerList value under regedit at HKLM\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent

  • Tristan Veteran 790 posts since
    Dec 8, 2009
    Currently Being Moderated
    4. Sep 17, 2013 4:03 AM (in response to Laszlo G)
    Re: changing ePo server name in site list XML

    Don't forget you will need to import your Agent-Server communication keys from your old ePO server to your new one

     

    Or load new keys into the agent. The KB entry below is for version 4 of the agent so i'm not sure it it works for 3.6

     

    https://kc.mcafee.com/corporate/index?page=content&id=KB53808

     

    -- ========= from abot two thirds down the page ==========

     

    Changing server

    Use this task to change the server with which a client communicates.

    The security keys must be located in the same folder as the site list.

     

    frminst.exe /siteinfo=<full path of target servers sitelist.xml file>

     

    -- ==============================

  • Laszlo G Veteran 1,213 posts since
    May 23, 2007
    Currently Being Moderated
    5. Sep 17, 2013 4:31 AM (in response to Tristan)
    Re: changing ePo server name in site list XML

    If I'm right CMA 3.6 didn't use communication keys (it was not yet designed for) so if all computers are using this version then he shouldn't need to export security keys.

     

    In fact it's easy to test, he just needs to change the value at the registry key and launch a cmdagent /p command to see if it reports to new epo server.

  • rackroyd McAfee Mentor 953 posts since
    Feb 3, 2010
    Currently Being Moderated
    6. Sep 17, 2013 5:05 AM (in response to Laszlo G)
    Re: changing ePo server name in site list XML

    Going back to the EOL status, please take a look at support article: KB51573 - Supported environments for Common Management Agent and McAfee Agent 4.x

    This defines the scope of function of the agents, including CMA 3.6.x

     

    Note at the least that your agent version just won't work on recent OS such as Windows 7, Windows 8, Windows Server 2008 R2 and Windows Server 2012.

    Please also take a look at: KB51111 - Supported environments for VirusScan Enterprise on Microsoft Windows

    This version of the agent does not meet the minimum requirement for any currently supported version of VirusScan enterprise either.

     

    I appreciate the operational difficulties in rebuilding your image but you really do need to plan to move to a more recent, supported version.

  • pboedges Apprentice 71 posts since
    Jan 20, 2009
    Currently Being Moderated
    7. Sep 17, 2013 7:53 AM (in response to Ron Wintrob)
    Re: changing ePo server name in site list XML

    one thing you can try is to create an Alias record for the new epo server using the old servers ip address.  when the clients attempt to lookup the old server using DNS they will be forwarded to the new one.  Another issue you may encounter as Tristan stated is the security keys, if you do not have the old servers agent keys on the new server they will not be able to communicate with it.

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 5 points
  • Helpful Answers - 3 points