Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 764 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

New Sophos server / retiring old problem

Pielander

Hello

We have a scenario that I haven't been able to find any information on and I'm hoping I can get some guidance here.

We currently have Sophos Enterprise Console 3.0 running on a Windows 2003 server with approximately 700 endpoints and Sophos AV version 7.6.  Our aim is to build a brand new server and set it up from scratch with a new database etc and retire the old server i.e this won't be a migration but it will be a new side by side installation.

We built a new Windows Server 2008 R2 box and installed Sophos Endpoint Security 9.5.  This is a clean installation with a new SQL Express 2008 database.

We have tried pushing new Sophos to computers that are currently protected by the 'old' server.  The new verion of Sophos doesn't install over the top of the old one and we get a 'RMSNT installation skipped' error and the computer name appears in the Enterprise Console with a green 'hourglass' that doesn't go away.  If we uninstall the old version of Sophos first then the new installs fine.

I have a few questions:

1. Is there any documentation on the scenario that I have described above.

2. Should the new version install over the top of the old version?

3. Is there an easy way to uninstall the old version?

Any help or guidance that you can give would be much appreciated.

Cheers!

:7467


This thread was automatically locked due to age.
  • 0

    Hello Pielander,

    as it has been said several times in this forum (for example ) the easiest way is to use the "old" server's certificates on the new server. You'll find also some suggestions how to "move" your clients to the new one without pushing the installation. It works (for the majority of our clients it was from 7.6.19 to 9.0.x and but in several instances also to 9.5).

    I haven't tested (with 9.5) what exactly happens when the certificates don't match and whether "Protect computers" would fail the way you describe as there is no need to do this.

    To summarize:

    1. Make sure the new server uses the same certificates (if needed reinstall SEC)
    2. Set up the groups and policies on the new server
    3. Make sure the clients' RMS will use the new server (either in the 7.6 or the 9.5 CID)
    4. If you changed the 7.6 CID the clients will "appear" in the new server from where you assign the new updating policy. In the other case modify the old updating policy to point to the new CID. 

    If you have more questions please ask

    Christian

    :7471
Unfiltered HTML