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 Vikas,

    I have tried to understand

    academic interest? An in-depth understanding is not necessary to successfully use and manage SESC.

    As far as practical use goes the following is IMO relevant:

    • If the CertAuthStore does not exist the server generates its keys, otherwise the existing ones are used
    • From these cac.pem and (parts of) mrinit.conf are generated for endpoint use
    • When an initial install is performed (i.e. setup.exe from the CID is run by whatever means - manually, Protect computers, or from a package) these data sets up the mutual trust (note that you can perform such an install regardless of the existing data)
    • From then on the endpoint verifies the server's identity with this information (both for RMS and AutoUpdate)
    • V.v. the endpoint proves it has been installed from a CID managed by this server

    So much for this week ... Christian

    :56168
Reply
  • 0

    Hello Vikas,

    I have tried to understand

    academic interest? An in-depth understanding is not necessary to successfully use and manage SESC.

    As far as practical use goes the following is IMO relevant:

    • If the CertAuthStore does not exist the server generates its keys, otherwise the existing ones are used
    • From these cac.pem and (parts of) mrinit.conf are generated for endpoint use
    • When an initial install is performed (i.e. setup.exe from the CID is run by whatever means - manually, Protect computers, or from a package) these data sets up the mutual trust (note that you can perform such an install regardless of the existing data)
    • From then on the endpoint verifies the server's identity with this information (both for RMS and AutoUpdate)
    • V.v. the endpoint proves it has been installed from a CID managed by this server

    So much for this week ... Christian

    :56168
Children
No Data