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

Enterprise Console 5.0 to 5.2 Upgrade Questions

regulators

I'm upgrading our Sophos Enterprise Console from 5.0 to 5.2. At the same time, I'm upgrading our server from Server2008 R2 to Server 2012 R2.

I understand the best path for the upgrade is to migrate Enterprise Console 5.0 from 2008 to 2012 and do the upgrade from 5.0 to 5.2 on the 2012 server.

However, part of the migration guide indicated that I "Stop Sophos services" while I'm doing the backup on 5.0. 

I want to take the backup from the console on server 2008 and deploy it on the new server and then upgrade, but I want to do this before deploying it as I would like to test it with a small group of computers on the network before roilling it out.

So, if I stop the services and perform the backup, can I restart the services and keep that console working while I prepare the new console?

Also, how exactly will stopping these services affect the machines on my network? I want minimal interruptions while I do the backup.

Thanks.

:55056


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

    Hi regulators,

    I'm not sure what the differences between migrating 5.0 and 5.2 are, but I and a few others on this forum have recently battled with upgrading 5.2, so if you do encounter any problems it's more likely you'll get an acurate answer from one of us if you upgrade first.

    While the services on the server are stopped, your client machines won't receive any updates unless you have a secondary location specified, but this won't affect the users.  In general, assuming a successful migration, users of client machines probably won't even notice.  In the event of having to roll back, if you restart the services then everything will resume as normal.

    From my experience the upgrades all went smoothly on a server 2003 box - it was only the migration that caused problems.  If you're using VMs though, snapshots are your friend!

    :55063
Reply
  • 0

    Hi regulators,

    I'm not sure what the differences between migrating 5.0 and 5.2 are, but I and a few others on this forum have recently battled with upgrading 5.2, so if you do encounter any problems it's more likely you'll get an acurate answer from one of us if you upgrade first.

    While the services on the server are stopped, your client machines won't receive any updates unless you have a secondary location specified, but this won't affect the users.  In general, assuming a successful migration, users of client machines probably won't even notice.  In the event of having to roll back, if you restart the services then everything will resume as normal.

    From my experience the upgrades all went smoothly on a server 2003 box - it was only the migration that caused problems.  If you're using VMs though, snapshots are your friend!

    :55063
Children
No Data
Unfiltered HTML