Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 1640 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Moving EC 4.7 (Db on seperate server) to new server.

pm_10

Hi,

I am moving EC 4.7 to a new server with a different name, db is running on a seperate SQL server & have only been able to find information on moving the console when it is running on the same server as db, the EC system is also a primary update source for a number of endpoints & other update managers.

Apart from following the migration guide  (except for the part about backing up & restoring db) , are there any suggestions for making this as painless as possible?

Thanks,

:18703


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    Being in the same domain and member servers all makes it simpler so that's good news as is knowing the SUM account and password.  In that case you should be able to something similar to the document here which will be extracted here:

    C:/sec_sua_471/docs/Eng/sec_47_ua46eng.html

    if you download and run:
    https://secure.sophos.com/support/updates/dp/full/sec_sua_47_sfx.exe

    You could just unpack this SFX to get the file.


    This document describes the steps you need to do to migrate a SEC 4.5 server running Windows 2000 to a different machine when using a remote database before upgrading.  Which in someway is what you are doing as the "move" steps for 4.5 and 4.7 are the same.  It certainly touches on the main points you need, e.g.:

    1. Backup the cert key and inport it on the new server (do this before installing the new server

    2. Backup the private store on the old server to an XML file using exportprivatestore.exe running as system (use psexec).

    3. Install on the new server
    4. Import the private store XML file using exportprivatestore.exe running as system (use psexec).

    5. Redirect endpoints to the new server.

    The reason I ask about how easy it is to run scripts is that I created a tool to redirect endpoints at a new server (step 5):
    /search?q= 8939 might be an easier way to point your clients at the new server location rather than updating the CIDs with batch files.  Please test the generated script on a few clients first :)

    I would strongly suggest taking a backup of the SOPHOS47 database on the DB machine before starting and ideally a backup of the current SEC server, maybe a snapshot if it's virtual.

    I hope that helps.


    Regards,

    Jak


     


     

    :18715
Reply
  • 0

    Hi,

    Being in the same domain and member servers all makes it simpler so that's good news as is knowing the SUM account and password.  In that case you should be able to something similar to the document here which will be extracted here:

    C:/sec_sua_471/docs/Eng/sec_47_ua46eng.html

    if you download and run:
    https://secure.sophos.com/support/updates/dp/full/sec_sua_47_sfx.exe

    You could just unpack this SFX to get the file.


    This document describes the steps you need to do to migrate a SEC 4.5 server running Windows 2000 to a different machine when using a remote database before upgrading.  Which in someway is what you are doing as the "move" steps for 4.5 and 4.7 are the same.  It certainly touches on the main points you need, e.g.:

    1. Backup the cert key and inport it on the new server (do this before installing the new server

    2. Backup the private store on the old server to an XML file using exportprivatestore.exe running as system (use psexec).

    3. Install on the new server
    4. Import the private store XML file using exportprivatestore.exe running as system (use psexec).

    5. Redirect endpoints to the new server.

    The reason I ask about how easy it is to run scripts is that I created a tool to redirect endpoints at a new server (step 5):
    /search?q= 8939 might be an easier way to point your clients at the new server location rather than updating the CIDs with batch files.  Please test the generated script on a few clients first :)

    I would strongly suggest taking a backup of the SOPHOS47 database on the DB machine before starting and ideally a backup of the current SEC server, maybe a snapshot if it's virtual.

    I hope that helps.


    Regards,

    Jak


     


     

    :18715
Children
No Data