Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 1624 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 upgrade and migration advice please

nisuj

Hi

I'm super new to sophos antivirus and looking for advice in regards to migrating and upgrading Sophos SEC. The current SEC verison is 4.5.0.9 and it sits on a win 2003 box.

I want to move everything sophos onto a new machine with Win 2008 R2 64bit and upgrade to 5.2 in the process.  

The current setup has about 40 clients with End Point Security and control v10 and very little configuration like policies etc.

What is the best option for this process?

Can I just install SEC 5.2 on the new server and point all the clients to it with the migration tool? I'm just trying to avoid upgrading  from 4.5.0.9 -> 5.1 -> 5.2  then migrating across servers. 

Thanks

:44001


This thread was automatically locked due to age.
  • 0

    Hello nisuj,

    if you are not interested in historical data and you think the little configuration you've made won't justify the necessary two-step migration a clean install is IMO the best way.

    Sounds like you've read the docs (if not, Sandy's post has the relevant links). Note that you have basically three options:

    1. export the certificates from the old server, import them before installing 5.2.1 and configure RMS in the CID(s)
    2. set up the new server (with or without the old certificates) and use the Endpoint Migration Utility
    3. set up the new server (with or without the old certificates) and re-protect them from the new console (or otherwise re-install the endpoint software)

    Option 3 is, if re-protect is possible, the simplest (if your license includes one of the newer features - Patch,  Web Control or Encryption - you have to use it anyway). Option 2 requires that you can run remote tasks (if you don't want to visit each computer). Personally I prefer 1, as it requires some knowledge it's probably not efficient  if you are not familiar with CID configuration.

    Christian

    :44033
  • 0

    Nisuj,

    We are in the process of migrating 15,000 or so machines from an older install to a new install.

    We chose to go with a new db/ec server and not to migrate any data from the DB.

    The easiest thing that we have seen to do so far is to set up the new db/ec and design your policies per your prefrence.

    Then simply get a list of all of your machines put them in a text file, and then import them using the import feature.

    Once you import them select the protect option and they will come into the new console and go red in the old.

    :44111
  • 0

    Thanks for the advice. This gives me some ideas on where to head.

    Thanks again.

    :44141