If you build a new application server and give it the same name as the old server then you wouldn't have to change any settings. You should not have two console applications pointing to the same database so you would need to shut down the old server before running the installer on the new server. At the bottom of this reply we will include the uninstall instructions.
If you build a new Console server with a new name then you would need to have the serverUrl setting changed on the endpoints to point to the new server name before uninstalling.
The recommended method to use if you are building a new Console installation on a different named server as follows:
Backup the database
Restore the database to the SQL Server as a different name
Run the installer on the new server to use an existing database and use the newly restored database name
On the old Console change the following setting in a System Policy applied to a tag with just a few endpoints to ensure everything is working as expected
Console\serverUrl (that is the URL of your Console's services page, ie.. your-new-console/Services)
Once you have ensured that the new Console is up and running without issues, and that the couple test endpoints are able to send results to the new Console and the results are shown in the new Console, then you can migrate the rest of the endpoints to the new Console.
Ensure that you destroy any MSI or installer packages that were created to point to the old Console. You will need to build new installers for the new Console's URL.
Following are the uninstall instructions for the older versions that did not have the application in the Control Panel:
To uninstall the console you may perform the following from a command prompt opened as Administrator or if newer version you may use Windows Control Panel:
Navigate to %temp% folder, then go to IDFInstall, then to the newest folder (that’s where the installer extracts its files), then to Setup, then run this:
If the file is not deleted, you may need to stop IIS and repeat the process.