Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 35 replies
  • Subscribers 1 subscriber
  • Views 30428 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? Need advice? Let us know!

lilhavoc

I want to ask you, our esteemed customers, what information Sophos could provide to make upgrading easier. This applies to upgrades from any version, but I'd love to be able to address people's concerns about the upgrade from Enterprise Console version 3 to version 4 especially.

We've got a great couple of upgrade guides, but what else can we do? What would you like to know more about?

Want to tell us how to do our jobs?? :smileyvery-happy: We'd love to hear to your suggestions, so let's talk!!

Thanks,

Lil

:1039


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

    Hi,

    No problems, we'll be sure to update our kba to reflect the upgrade of 64-bit servers.

    In the meantime, please do follow article 28276 (please note that v4 is not supported on Windows Server 2008 R2); however, on a 64-bit installation: 

    • the path to the Sophos programs is: C:\Program Files (x86)\Sophos
    • the registry keys on 64-bit servers can be found at: "HKEY_LOCAL_MACHINE\Software\WOW6432Node\Sophos...".

    There is no need to upgrade the existing Enterprise Console, however, because the new server is running Windows Server 2008, you will need to install Enterprise Console version 3.1.1 on it.

    I would also advise that you disconnect the new server until all of the steps have been performed. If that is not possible, we recommend that you disconnect the old server once you have installed Enterprise Console 3.1.1 on the new server. Probably best to do it when you don't need access to the console for a while :).

    Please also ensure that you take note of the following points before upgrading:

    • 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 Enterprise Console.
    • The hostname and IP address of the new server MUST match the original server’’’’s hostname and IP, otherwise you will have to redeploy the client software to your endpoints.
    • The target server should be in the same domain as the existing one is/was.
    • Ensure that you are running only one Console on the network at a time, otherwise you will experience problems.
    • If you are migrating to a server running Windows Server 2008, please be aware that you will need to use a message relay for network communications if you have more than 5,000 endpoints. See Enterprise Console: configuring message relay computers for more information.
    • Before you start, read the Warning about editing the windows registry.

    Hope it all goes well!

    Cheers,

    Lil

    :1601
Reply
  • 0

    Hi,

    No problems, we'll be sure to update our kba to reflect the upgrade of 64-bit servers.

    In the meantime, please do follow article 28276 (please note that v4 is not supported on Windows Server 2008 R2); however, on a 64-bit installation: 

    • the path to the Sophos programs is: C:\Program Files (x86)\Sophos
    • the registry keys on 64-bit servers can be found at: "HKEY_LOCAL_MACHINE\Software\WOW6432Node\Sophos...".

    There is no need to upgrade the existing Enterprise Console, however, because the new server is running Windows Server 2008, you will need to install Enterprise Console version 3.1.1 on it.

    I would also advise that you disconnect the new server until all of the steps have been performed. If that is not possible, we recommend that you disconnect the old server once you have installed Enterprise Console 3.1.1 on the new server. Probably best to do it when you don't need access to the console for a while :).

    Please also ensure that you take note of the following points before upgrading:

    • 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 Enterprise Console.
    • The hostname and IP address of the new server MUST match the original server’’’’s hostname and IP, otherwise you will have to redeploy the client software to your endpoints.
    • The target server should be in the same domain as the existing one is/was.
    • Ensure that you are running only one Console on the network at a time, otherwise you will experience problems.
    • If you are migrating to a server running Windows Server 2008, please be aware that you will need to use a message relay for network communications if you have more than 5,000 endpoints. See Enterprise Console: configuring message relay computers for more information.
    • Before you start, read the Warning about editing the windows registry.

    Hope it all goes well!

    Cheers,

    Lil

    :1601
Children
No Data
Unfiltered HTML