Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 9 subscribers
  • Views 4769 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

Sophos migration

SecureIA Ltd

Good Morning all,

 

I am new to the discussion boards so sorry if this is in the wrong place, I am also not a tech savvy person I am more first line support so bare with me on this!

 

Currently I have been tasked with researching how to migrate our Sophos AV from one server to another. Everything is currently situated on one management server so it is getting that from old build to the new build (These are Virtual Machines).

 

For me I am unsure which guide I would need to look at in order to make sure the process is correct and runs smoothly.

 

Our old build which currently has Sophos on is a Windows 2012 R2 64 bit and Sophos is Version 5.3.1 running on a Sequel Express database - the new build is running Windows 2016 Standard with 64 bit processor.

Any guidance/tips will be appreciated as it will be a first time for me doing something like this (We have a development network where I will be trying this first before doing the real thing to make sure we are all comfortable)

 

Thank you.

 

James



This thread was automatically locked due to age.
Parents
  • +1

    Hi,

    The SEC docs are here:

    https://www.sophos.com/en-us/support/documentation/enterprise-console.aspx#

    The question then might be, do I upgrade the current install to the latest SEC version and then migrate that or migrate the current version and upgrade to the latest version after the move? 

    Possible upgrade paths are as follows: https://community.sophos.com/kb/en-us/119105

    So from 5.3.1 you can go straight to 5.5 which saves extra upgrades.

    It used to be that with each version of SEC it got more components and it was easier to migrate the older version.  If you're starting from 5.3.1 I don't think it matters so much.

    The migration guides for the various versions can be found in the SEC docs above.  There is a PDF for each.

    Note:
    Before performing a migration, I would always manually backup the registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\Sophos\Certification Manager
    and take a backup of the databases for the version in use.  Details of the database names are here: https://community.sophos.com/kb/en-us/17323. With the aforementioned registry key and database you can always recover an install without the need to redeploy the clients.

    The other option, which might be simpler, as a SEC migration is quite involved is to just perform a fresh installation of the latest version on the new server and then either:

    1. Re-protect the clients.  This could include push deployments from SEC (requires the computers to be on) or AD Startup scripts to run setup.exe from the distribution point on the new server.

    2. Re-initialise the clients using this script - https://community.sophos.com/kb/en-us/116737 

    This really depends on how many managed clients you have and how accessible they are.  It also assumes you don't really care to much about previous reporting data and the configured policies are minimal such that it wouldn't take long to re-create them.

    Regards,

    Jak

Reply
  • +1

    Hi,

    The SEC docs are here:

    https://www.sophos.com/en-us/support/documentation/enterprise-console.aspx#

    The question then might be, do I upgrade the current install to the latest SEC version and then migrate that or migrate the current version and upgrade to the latest version after the move? 

    Possible upgrade paths are as follows: https://community.sophos.com/kb/en-us/119105

    So from 5.3.1 you can go straight to 5.5 which saves extra upgrades.

    It used to be that with each version of SEC it got more components and it was easier to migrate the older version.  If you're starting from 5.3.1 I don't think it matters so much.

    The migration guides for the various versions can be found in the SEC docs above.  There is a PDF for each.

    Note:
    Before performing a migration, I would always manually backup the registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\Sophos\Certification Manager
    and take a backup of the databases for the version in use.  Details of the database names are here: https://community.sophos.com/kb/en-us/17323. With the aforementioned registry key and database you can always recover an install without the need to redeploy the clients.

    The other option, which might be simpler, as a SEC migration is quite involved is to just perform a fresh installation of the latest version on the new server and then either:

    1. Re-protect the clients.  This could include push deployments from SEC (requires the computers to be on) or AD Startup scripts to run setup.exe from the distribution point on the new server.

    2. Re-initialise the clients using this script - https://community.sophos.com/kb/en-us/116737 

    This really depends on how many managed clients you have and how accessible they are.  It also assumes you don't really care to much about previous reporting data and the configured policies are minimal such that it wouldn't take long to re-create them.

    Regards,

    Jak

Children
Unfiltered HTML