1 Reply Latest reply on Jun 13, 2008 10:26 AM by MilleRJ

    Migarting From 3.6 to 4.0

      I have a EPO 4.0 and EPO 3.6 servers online. I have migrating the computers from 3.6 to 4.0. Been successful for almost 800 computer but about 20 are giving me issues.

      If I send an install agent from the 4.0 server to the computers (pointing to 3.6), I can see the install works but the computers continue to point to the 3.6 server.

      If I delete the agent from the computer and send an agent install from the 4.0 server, I can see the install works but the computers continue to point to the 3.6 server.

      If on the 3.6 server I set the repository to point to that of the EPO 4.0 server, I can see in the agent logs that they update from the 4.0 repository but continue to point to the 3.6 server. In 4.0 repository I have updated to the 4.0 McAfee Agent.

      If I install the agent manually same results

      I used all the methods above to move the majority of my computers to the 4.0 server. I need to keep the 3.6 online since I have computers updating to.

      It feels like I've missed something obvious. I've check all the standard stuff (privs, etc) but for these remaining computers I can't get them to move.

      Any thoughts would be appreciated.
        • 1. RE: Migarting From 3.6 to 4.0
          Just spotted your post - Hopefully you've found the problem by now, but if you haven't....

          AFAIK, the client knows which server to 'point to' becuase of the 'Sitelist.xml' file in 'C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework'

          Have you tried removing / renaming this file, so it can be recreated when you send out the agent - you shouldn't need to but perhaps something is preventing it being overwritten?

          Have you tried simply switching off the 3.6 server while you send out from the 4.0 server - perhaps sitelist has both servers, but it will always try 3.6 FIRST...?

          Just a couple of thoughts - Good luck
          Bob