Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 1 subscriber
  • Views 23371 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 Enterprise 5.2 migration

svdb

Hello,

We have:

Server1: (windows 2003) Database service (5.2)

Server2: (windows 2003) Sophos management server (5.2)

we want to migrate the Server 2 installation (w2k3) to a new server (Server3: W2K8), en i will keep the Server 1 installation.

I read the article "http://www.sophos.com/en-us/support/knowledgebase/28276.aspx" but the first note tells me:

  • These instructions apply only to installations that used the default settings. In particular, it does not apply to installations where the database and/or the management service are located on a different server to the console.  For further information on installing or upgrading a management server with a remote database see article 33980.

The article 33980 isn't in my opinion not the right one.

can anybody tell me how to migrate the Windows 2003 (Server 2) installation to Windows 2008 (server 3) ?

:38093


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

    Hello svdb,

    article 33980 is in my opinion not the right one

    you are correct that it does not describe the process of moving the management component. Basically you have two options (Note: the original server must be turned off before you install the new one and must stay turned off):

    1. Just make a fresh install (without the database component) and point the installer to the existing database. Make sure you have all the required credentials (e.g. database user) available. You'd then have to reprotect your clients from the new server
    2. Export (backup) everything except the database, import on the new server as specified in the migration guide, then install (again w/o the database component)

    If the new server does not inherit the old name/IP then the tricky part for option 2 is to "move over" the clients (unless you reprotect/reinit them). There are several ways. You could assign the new updating policies while the old server is still running. The clients would fail to update until the new server is active (although you could pre-load the CIDs there). The obvious drawback is that clients not online at this time will not receive the new policies. To overcome this you could configure the old CID for either AutoUpdate (using sauconf.xml with the new update location) or RMS (with an appropriate mrinit.conf). In any case the RMS components should be configured in the CIDs on the new server. Special considerations apply if you are using Patch Assessment

    Feel free to ask if you need more details.  

    Christian

    :38125
Reply
  • 0

    Hello svdb,

    article 33980 is in my opinion not the right one

    you are correct that it does not describe the process of moving the management component. Basically you have two options (Note: the original server must be turned off before you install the new one and must stay turned off):

    1. Just make a fresh install (without the database component) and point the installer to the existing database. Make sure you have all the required credentials (e.g. database user) available. You'd then have to reprotect your clients from the new server
    2. Export (backup) everything except the database, import on the new server as specified in the migration guide, then install (again w/o the database component)

    If the new server does not inherit the old name/IP then the tricky part for option 2 is to "move over" the clients (unless you reprotect/reinit them). There are several ways. You could assign the new updating policies while the old server is still running. The clients would fail to update until the new server is active (although you could pre-load the CIDs there). The obvious drawback is that clients not online at this time will not receive the new policies. To overcome this you could configure the old CID for either AutoUpdate (using sauconf.xml with the new update location) or RMS (with an appropriate mrinit.conf). In any case the RMS components should be configured in the CIDs on the new server. Special considerations apply if you are using Patch Assessment

    Feel free to ask if you need more details.  

    Christian

    :38125
Children
No Data