Safeguard 8.1?

Hi David,

There is currently no release date set yet for SafeGuard 8.1. We will announce it both via the Community and Twitter once we have further information.

Thanks for your patience,

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.

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

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.

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.

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.