Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 8 subscribers
  • Views 8784 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

Safeguard 8.1?

David Peterson

We recently purchased Sophos Central and Safeguard for full disk encryption. Looking at the Safeguard requirements for the server component, Server 2016 is currently not supported in 8.0 but I saw a reference back in September that 8.1 was coming soon, with support.

Ideally, I'd like to get us started on a 2016 box, is there any current timetable as to when 8.1 will be available?



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Karlos

    Thanks. If we start out on 8.0 and a 2012R2 box, would it be a simple migration over to a 2016 box when support is added? The database would be on a separate SQL server.

  • 0 in reply to David Peterson

    Hi David,

    This is our current KB article outlining the steps for migrating the database from one SQL server to another: How to migrate the SafeGuard Enterprise database and then perform the subsequent reconfiguration

    If these steps are to change for 8.1, we will update the KB accordingly.

    Thanks,
    Karlos

    Karlos
    Community Support Engineer | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'This helped me' link.
  • 0 in reply to Karlos

    No, I mean how difficult is it to move the Application server that runs on IIS if the database is on a separate server that isn’t moving.

    Basically, if we eventually do want it on a 2016 box, but moving would require decryption of clients etc. We’re coming over from a competitor where updating the AV client sometimes requires decryption/reencryption so trying to avoid pain points where possible.

  • 0 in reply to David Peterson

    All of the important business that the clients need is stored in the SQL database, and the SGN server's IIS, etc., is just the management and client window into the SQL db.

    I did this a little while back and it was pretty straightforward. Short version is you follow the process for setting up a new server but instead of generating new keys and certificates you import the ones from the old server, push out new client config MSI packages pointed at the new server, and done.

    There is no reason you can't set up your new SGN with the old one still running to be sure you have everything right when you start pushing out the new client config MSI that points to the new SGN server which is pointed at the same SQL database.

    You won't have to decrypt the clients.

Unfiltered HTML