Regarding the Secondary Public IP in Sophos Safeguard 8.1 or above server to communicate roaming users

Question

Dear Team, 
 
 One of our client is having the below environments: 
 Server --- Sophos Safeguard 8.1 Server ,SQL Database , IIS Server & Management Center are both installed on the single Server. 
 
 Client --- Win 7, Win 8 & Win 10 Professional ,pro editions are enrolled in the Safeguard 8.1 Server & total around 2500 users are enrolled on this server. 
 
 Currently due to COvid 19 ,90% of users using the laptop system to do the office work & due to this scenarios we are facing the multiple issues like Unable to Sync the client policy to the Server,Unable to recreate the new Client certificate once the user is changed password out of Active Directory network,Unable to login ;etc

To avoid this issue, 
 Can we create & configure the Secondary Server where PubliC IP/HostName to Private IP/Hostname(Office Network) we mapped ,Please share us the steps if this scenario is possible 
 
 Currently below packages are installed on the client systems: 
 1.Safeguard Preinstall 
 2. Safeguard CLient 
 3.Safeguard Client Confgiuration(Register on Primary SGN Server with SSL certificate)

In this scenario of roaming User (WFH), 
 how client is communicating with the public IP of secondary server to sync the policy in the datacard

MichaelMcLannahan · Answer

1 - Yes, that's the standard setup with one SSL cert for the server. However each and every server needs its own cert. 
 2 - You can use an internal cert. The certs are included within the configuration created by the server. You may find a public one easier however - but it's personal preference. 
 3 - The secondary server just needs the one MSI installing (SGNServer.msi found in Installers - Backend Installers) - and then the configuration that's generated by the primary applied. 
 You can do most of this work using the Configuration Package Tool - You may need to log on as MSO to access this.

MichaelMcLannahan · Answer

Yes, just one DB needed. You do not need to set this up on the secondary server. It communicates with the primary server and the primary server has the relationship with the database (or database server)