3 Replies Latest reply on Jul 18, 2011 4:23 AM by SergeM

    Install second ePO server.

      Hi there!

      Since our first ePO server is currently half destroyed, we decided to install a new one.

      No cluster between them

      So, can someone provide us a little walkthrough in order to do this correctly?

      Do we need to stop service on the first server before installing the new one and after do a AD synchronization and make a wake up call for all McAfee agent?


      Many thanks!!


      PS: we have saved a Groupshield 7.0 SP1 .xml configuration file. Can we push it in the new ePO server?

        • 1. Re: Install second ePO server.
          Laszlo G

          Hi john_matrix, if you've installed a new ePO server then you'll have to deploy the agent from this server to any computer you want to manage from him.


          As it's a new server it's totally independent from the old one so no need to stop services.

          • 2. Re: Install second ePO server.

            hi Ulyses31,

            Thank your for your answer

            I'll try to redeploy McAfee agent from this new server.

            Keep you in touch!



            • 3. Re: Install second ePO server.



              Our set-up so far is probably somewhat different from yours, since we're not using any AD yet.


              Here's what we did (twice already, for different reasons)

              - have one server running, or crawling (as you say yours is dying)

              - installed a second server without touching the first one

              - copy the Security Keys from old-server to new server if you can (see KB51438)


              then what we did was to give new-server the DNS name & IP of old-server.

              Most (95%) of our agents didn't see a difference.

              If you're using AD I believe you ought to be able to push a new agent on those that do have a problem.


              We did this twice, once was in 2008 when upgrading from ePO 3.6 to ePO 4 while switching to a new server and new SQL DB, the second time was last year when upgrading servers and SQL servers from ePO 4 to ePO 4.5 (new hardware, new OS, new ePO).


              Hope it helps


              1 of 1 people found this helpful