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

Migrate server, keep same name?

We have Enterprise Console Server 5.2.2 running under Windows Server 2008 R2

We would like to migrate this to a new server running Windows Server 2012 R2

I have read through the migration guide which assumes the database is installed on the same server. Our database is housed on a separate SQL 2014 server. Our primary update server is a separate web server and our secondary update server is Sophos. We protect about 1,000 endpoints, 800 Win7 machines and 200 Macs

Is there any way to do this migration and keep the same hostname for the server? If we kept the same IP address and hostname wouldn't endpoints just work properly if certain things were migrated from the old server to the new server?

:55564


This thread was automatically locked due to age.
Parents
  • Hello HendersonD,

    in principle you can follow http://www.sophos.com/en-us/support/knowledgebase/27265.aspx. While it states that it applies to identical computers, of the same operating system and platform I think that there are no significant differences between 2008 R2 and 2012 R2. Backing up the databases is a good idea but - as they exist and are remote - you don't have to install or restore them, just tell the installer where to find them. The most important piece is IMO the CertAuthStore (backed up as CertificationManager.reg) as it contains the "identity" of the server (i.e. it contain the certificates by which the endpoints recognize the server as "their" known server).

    Short summary:

    1. Stop the services on old
    2. Take the backups (of old and the databases)
    3. Shot down old
    4. Set up new
    5. Import CertAuthStore
    6. Install SEC on new selecting Management Server and Console
    7. Import remaining registry keys

    HTH

    Christian   

    :55566
Reply
  • Hello HendersonD,

    in principle you can follow http://www.sophos.com/en-us/support/knowledgebase/27265.aspx. While it states that it applies to identical computers, of the same operating system and platform I think that there are no significant differences between 2008 R2 and 2012 R2. Backing up the databases is a good idea but - as they exist and are remote - you don't have to install or restore them, just tell the installer where to find them. The most important piece is IMO the CertAuthStore (backed up as CertificationManager.reg) as it contains the "identity" of the server (i.e. it contain the certificates by which the endpoints recognize the server as "their" known server).

    Short summary:

    1. Stop the services on old
    2. Take the backups (of old and the databases)
    3. Shot down old
    4. Set up new
    5. Import CertAuthStore
    6. Install SEC on new selecting Management Server and Console
    7. Import remaining registry keys

    HTH

    Christian   

    :55566
Children
No Data