Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 7076 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

Clean installation of Sophos Enterprise Console 5.2.1 R2

NikolaFBA

Hello to you all,

We would like to install Sophos Enterprise Console 5.2.1 R2 on Windows Server 2012.

We have an old installation on Windows Server 203. One of the Sophos Update Managers is

installed on Windows Server 2008. Which are the main steps to perserve protection

with "old" system before connecting endpoint computers to new installation?

Is that possible at all? If it is not, what are the best practices for this type of, let's write, "migration"?

We would like to skip importing of Sophos database in any way  from Server 2003 to Server 2012.

Will there be a problem with Console updating in any sense if we have these two parallel

systems running until "old" one is "shut down"?

Thank you very much in advance for your help!

Regards,

Nikola

:45641


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

    Hello Nikola,

    We would like to skip importing of Sophos database in any way

    so you want to start with an empty database and create everything (groups, policies) from scratch? Note that you lose all history this way.

    The servers are independent so it's no problem running both in parallel (and perhaps "moving" the clients and their SUMs in groups over some period). You've probably read the Migration Guide - if not, you should do so. Even if you start with an empty database you should export/import the certificate registry key.

    In short you install the new server, configure subscriptions and create initial policies. You'd then have to plan by which method you'll "move" your clients. If you don't use Patch you can do this by simply configuring the CID(s) - otherwise How to redirect Windows endpoints to a new management server gives an overview of alternate methods. If the former you create appropriate updating policies pointing to the new server (this could be tricky if you use more than one subscription though). I suggest you test it on a few clients and then tackle a SUM/Message Relay and its clients.

    You'll likely have some more questions - feel free to ask.

    Christian

    :45643
Reply
  • 0

    Hello Nikola,

    We would like to skip importing of Sophos database in any way

    so you want to start with an empty database and create everything (groups, policies) from scratch? Note that you lose all history this way.

    The servers are independent so it's no problem running both in parallel (and perhaps "moving" the clients and their SUMs in groups over some period). You've probably read the Migration Guide - if not, you should do so. Even if you start with an empty database you should export/import the certificate registry key.

    In short you install the new server, configure subscriptions and create initial policies. You'd then have to plan by which method you'll "move" your clients. If you don't use Patch you can do this by simply configuring the CID(s) - otherwise How to redirect Windows endpoints to a new management server gives an overview of alternate methods. If the former you create appropriate updating policies pointing to the new server (this could be tricky if you use more than one subscription though). I suggest you test it on a few clients and then tackle a SUM/Message Relay and its clients.

    You'll likely have some more questions - feel free to ask.

    Christian

    :45643
Children
No Data