Upgrade Enterprise Console

Hi,

I would suggest 2008 R2 if possible, rather than 2008.  TBH, I'd probably leave it on 2003 rather than 2008 if there is no particular reason to move it.

The migration guide is the main thing you'll need:

http://www.sophos.com/en-us/medialibrary/PDFs/documentation/sec_51_mgeng.pdf

Make sure the new OS is running the same locale as the old SEC server before installing so the SQL install is of the same collation.  That is one tip that will save you some time. 

It'll proabably take (for a straight forward setup) about 1 hour to complete the migration of the server component.  Migrating the clients is another thing entirely.  You can reprotect the clients using SEC, setup a deployment script (to re-run setup) or use the VBScript HTA generator mentioned in KBA http://www.sophos.com/en-us/support/knowledgebase/116737.aspx to hlep redirect the clients.

Regards,

Jak

Hello Joetobai,

[meanwhile Jak has posted his version - sorry if there are repeats]

general advice: Make sure you have the necessary backups (and that they are usable)

general answer: it depends

general tip: document the steps you take (not only with SEC but also Windows configuration), try to make them repeatable (e.g. if possible take a snapshot "just before install"). In case it does not work as expected it's often easier to "take a step back" than uninstalling.

It depends on whether you just want to replace the server  (or upgrade the server OS) or seize the opportunity to "clean up" or to restructure your environment. You could "switch" to the new server in one step or run both in parallel. This depends on your infrastructure, the number of clients, "service times"  and other factors.

We could give more specific advice if you'd describe your setup and the intended approach in detail.

Christian

The current SEC is working fine on current Server, I was more looking from the point of view of keeping the OS current. If its more hassle than its worth I might leave it. It would be a clean install of Windows 2008 on a new Server rather than an upgrade.

Advantages/Disadvantages of having 2 SEC working in parallel ?

Just a bit of background.

1500 clients in 24/7 environment

SEC on Windows 2003 Server

2nd Update Manager running on Windows 2008 Server

Hello Joetobai,

first you'd have to decide what to do with your second SUM. Does it provide the primary update location for a part of your clients and what's its source location - Sophos or the master server?

If you use the same "identity" for the new server (certificates and IP/name) you naturally can't run them in parallel. While there is no change required on the clients they won't be able to update during the migration (unless they have Sophos as Secondary update location).

If you you use the same certificate you can "move" the clients to the new server by pointing them to the new update location (you'd have to configure the CID with the appropriate mrinit.conf) but an extra step is required if using Patch. The usual method (which also works if the certificates are different) is re-protecting the clients, running setup.exe or employ the migration utility Jak has mentioned.

Whether you import the database on the new server or start with an empty one you'll lose (at least some of) the clients' history with a parallel approach.

Christian