Below is written for when the new Console server has a different URL than the previous Console server did and you are moving the Console application and the existing database to a new SQL Server while leaving the old installation operational until all the endpoints have been migrated to be communicating with the new Console.
The database has all the data in the Console. You can migrate the database to a new SQL Server on a new server, and then install the Console application on a new IIS server by running the installer using an existing database which would be the restored backup of the database from your old SQL Server.
You will need to know your Database Encryption Passphrase that you entered during the original install before performing the below. If you do not have that passphrase please let us know and we will send you the process to retrieve it.
Before you start this process you may want to cancel any Scheduled Tasks scheduled for the endpoints since they will be sending results to the old Console until they are migrated to the new Console and those results would not be in the new Console's database as it was backed up before they were sent to it.
Backup the current database
Restore the database into the new SQL server creating a new database with the restore. You can restore from a lower version of SQL to a higher version SQL, but not the other way around.
On the new Console server run the console installer using the instructions linked to below, selecting use an existing database, and entering the restored database location and login credentials. Please ensure that the Console Administrator Tool, Server Manager, and any instance of SSMS connected to the database is not open when running the installer.
The following article has instructions for running the installer. Please ensure that you follow all of the steps, including all of step #15 'Additional Steps':
Following is instructions to migrate the endpoints from one Console to another:
Source Console == Original Console
Target Console == The Console you are migrating the endpoints to.
On the Source Console, the Console the endpoints are currently communicating with, you would configure the following setting with the new Console URL in a System Policy that is only applied to the endpoints you wish to migrate to the new Console.
The System Policy on the Source Console needs to be a higher priority than any other Policy that may have those settings configured.
Please also ensure that you do not have that setting configured with the Source Console URL in any policy on the new Target Console or the old Source Console.
The Console\serverUrl should be configured on the System Policy on the Source Console with the URL of the Target Console's Services page which can also be found in the clientsettings.reg file downloaded from the Target Console's Services page. Please ensure you use a URL that can be reached from any of the endpoints you are migrating. The serverUrl is the URL to the console Services location which is the HTTP or HTTPS URL to the console web service (e.g. https://yourserver/Services).
Please just apply to System Policy on the Source Console to just a couple endpoints of each platform (Windows, Mac, Linux) first to test your settings before applying it to many endpoints.