Before You Begin
Read through this entire section before using the Migration Tool.
Target Console Machine Considerations
The machine you are migrating to must:
•Contain one of the approved Windows operating systems
•The version of Security Controls that is on your target console must be equal to the version on your existing console.
You do not need to activate or configure anything on the newly installed (target) console. The migration tool will provide all of that information during the restore process.
•Not be an active console
The restore process will overwrite any data that exists on the new Security Controls console machine.
If You are Using Agents
Console Alias List
Important! Perform this step as far in advance of the migration as possible.
The Console Alias list on the existing console must be updated with the host name, IP address, FQDN, etc. of the new target console. This is done so your agents will know to use the new console for their check-ins when the existing console is turned off and becomes unavailable. Use the Tools > Console alias editor menu to update the alias list.
You should update the Console Alias list as far in advance of the migration as possible. This is so the agents will have time to check in with the existing console and retrieve the updated Console Alias list. A good rule of thumb is to update the Console Alias list several check-in periods prior to the actual migration.
Important! Any agents that do not check in with the old console and receive an updated alias list will be stranded when the old console is turned off.
Tip: You will avoid stranding any agents if you are using Protect Cloud synchronization as a fallback failover destination. If for some reason the agents cannot locate the new console, if you have enabled the use of Protect Cloud synchronization in the agent policy, the agents will have the ability to check in with the cloud.
Protect Cloud Synchronization
If you are using Protect Cloud synchronization, perform a full update by selecting Tools > Options > Protect Cloud sync and then clicking Force full update now. This will ensure that the agent policy data contained on the cloud service is up to date.
Upgrading to a More Current Version of SQL Server
If you want to upgrade to a more current version of SQL Server during this migration and you are using:
•A local SQL Server Express Edition: No actions are required (do not pre-install any version of SQL Server). The most current supported version of SQL Server Express Edition will be installed automatically when you install Security Controls.
•A local Full Edition of SQL Server: Install the desired edition of SQL Server on the new console machine BEFORE you install Security Controls. During the installation of Security Controls you will point to the new local SQL Server instance.
•SQL Server on a remote server: To perform the upgrade:
a. Install the desired edition of SQL Server on the remote server.
b. Backup your current Security Controls database and restore to the new SQL Server.
c. Use the Database Setup Tool to point all instances of Security Controls to the new instance.
To access the Database Setup Tool: Start > Ivanti Security Controls > Database Setup Tool.
d. Run the migration.
You can upgrade your remote SQL Server edition after the migration if you prefer, but the recommendation is to do it before the migration.
Create a Backup of Your Database Before Using the Migration Tool
This is strictly a precaution, but a smart one. If you are using an express edition of SQL Server, you can use the Database Maintenance tool within Security Controls to create the backup. If you are using a full edition of SQL Server, you should use the SQL Server Maintenance Plan Wizard to setup your maintenance plans as this wizard is more robust and provides additional functionality.
Record Your Current License Information
Select Help > About Ivanti Security Controls and record your current license key data and product capabilities. You will use this information after the migration is complete to verify that your license information was properly migrated.
If You Have Scheduled Patch Deployments
You should wait for the scheduled patch deployments to complete before you begin the migration. If a scheduled deployment does occur after you begin the migration, the new console will not receive the deployment results.
Was this article useful?
Copyright © 2019, Ivanti. All rights reserved.