1 2 Previous Next 18 Replies Latest reply on Feb 9, 2012 9:58 AM by JoeBidgood

    Problems with clients refusing to connect to EPO after restaging server with new hostname


      We staged a new server with EPO 4.6 patch 1 after the previous server database got corrupt with installing patch3 on EPO 4.5

      The new server is fresh installed on Win 2008 R2, has EPO version 4.6 patch 1 and a new hostname.

      The old server was running on Win 2003 with EPo version 4.5 patch 4.


      In our staging disks we still use agent 4.5 from the initual server.

      These clients refuse to connect to the new server even that we :

      * checked in the agen-server key's from the old server into the new server

      * redirected the old hostname to the new server.


      We opened a McAfee case for this and got the feedback that this is just because the hostname is different.

      This could be possible but I still find this a strange answer because the key's are checked in.  Why should the connection also check the hostname.


      Anyone who can help us ?

      This information is very important to know for DRP situations or like in our case an SQL database becomes corrupt.

        1 2 Previous Next