Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 3544 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

Upgrading 4.7 to 5.2

WS123

Hi everyone.   I wsa taksed with upgrading our Sophos Enterpirse console form 4.7 to 5.2.  I  have been reading thru the upgrade guides but i have a few questions.   I've been asked to have Sophos installed on one VM and the database installed on another VM.    I was looking thru the upgrade guide and was wondering what the best course of action hould be.  Should i just install a fresh coipy of 5.2 on the new server?   If so is there a way to migrate over settings from 4.7 for all of the users that have endpoint installed?   In the install will I have the option of installing the database oin a seperate sql server?

Thanks in advance for your replies

:54657


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

    Hello WS123,

    first off, there is no direct path from 4.7 to 5.2, thus of you want to keep/migrate the group structure and policies (it's all or nothing) you have to go through 5.1.

    Sophos installed on one VM and the database installed on another VM

    SQL Server already installed on another VM? Otherwise I don't see a significant advantage in using two VMs. Installing the DB on a separate server is described in the advanced startup guide.

    Whether it's worth the effort to perform the required two-step migration in order to keep the settings naturally depends on the amount of configuration data. And - if you start with a new 5.2 installation you lose all "historical data" as well.

    Christian

    :54661
Reply
  • 0

    Hello WS123,

    first off, there is no direct path from 4.7 to 5.2, thus of you want to keep/migrate the group structure and policies (it's all or nothing) you have to go through 5.1.

    Sophos installed on one VM and the database installed on another VM

    SQL Server already installed on another VM? Otherwise I don't see a significant advantage in using two VMs. Installing the DB on a separate server is described in the advanced startup guide.

    Whether it's worth the effort to perform the required two-step migration in order to keep the settings naturally depends on the amount of configuration data. And - if you start with a new 5.2 installation you lose all "historical data" as well.

    Christian

    :54661
Children
No Data