Security Controls

Post-Migration Tasks

In order to complete the migration, you must perform the following tasks on the new Security Controls console. The sooner you perform these tasks the sooner you can permanently retire your old console. You want to retire your old console as soon as possible to eliminate duplicate and time-consuming tasks from being performed by both consoles.

Manually Migrating Items Not Moved by the Tool

If you are in a proxy environment or a disconnected environment:

The Security Controls license is not automatically activated in these environments. To activate your license, from the Security Controls menu select Help > Enter/refresh license key.

If you had an agent running on the local console:

This agent will not be migrated and must be reinstalled after the migration.

If you are using custom patch XML files:

Custom patch XML files must be moved manually because they are saved to a location that cannot be referenced by the Migration Tool.

If you are using a data rollup configuration:

Rollup (central) console: After the migration, go to Tools > Options > Data Rollup and confirm that Accept and import results from a rollup sender is enabled.

Remote console: After the migration, go to Tools > Options > Data Rollup, confirm the rollup server information and then click Register.

If you are using a distribution server that resides on the local console:

The distribution server configuration and the files contained on the distribution server will be moved. The folder representing the distribution server, however, must still be defined as a shared folder, the Windows permissions to access the shared folder must be updated, and the path to the folder must be updated in the distribution server configuration on the new console.

If you were using customized user-specific options:

Go to Tools > Options and reset any custom setting that was not migrated.

Verification Checklist

Perform the tasks in this checklist to verify that your new Security Controls console is operating properly.

Select Help > Refresh files and make sure no errors occur.

Select Help > About Ivanti Security Controls and verify that your license key data is valid and that the correct product capabilities are enabled.

Run a scan and a patch deployment to verify that your credentials can access the machines in your machine groups.

Download a patch and verify that the download is successful.

If you are configured to use the Database Maintenance feature, select Tools > Options > Database Maintenance and click Run now to verify that the feature is working properly.

If you are using agents, check that they have all checked in with the new console. You can do this from Machine View by using the Has an Agent Policy filter and then sorting by the Last Agent Check In column. All check-in dates should be after the date you modified the Console Alias list on the old console.

If you have enabled the use of Protect Cloud synchronization in an agent policy, you must register the new console and force a full update. To do this, select Tools > Options > Protect Cloud Sync and click This console is registered (the text on the button in this case is misleading because it is referring to the old console). When the registration is complete, click Force full update now.

If you are using the distribution server synchronization feature, verify that it succeeds the first time it is scheduled to execute.

If you have multiple consoles and are using data rollup, check that the rollup succeeds on the proper schedule.

If you have scheduled tasks such as patch scans or patch deployments, watch closely the first time through to make sure the tasks are successfully completed.

Use the Tools > Console alias editor menu to remove the old console’s information from the Console Alias list. Also, if the new console is on a domain-joined machine, you will need to add the fully qualified name of the new machine to the alias list.

When and How to Retire Your Old Console

You can retire your old console when the migration is complete and all of your agents are successfully checking in with the new console. The recommended steps are:

1.Verify that the Security Controls Console Service is stopped on the old console.

This will effectively disable the old console and route all traffic to the new console.

2.Go through one or more maintenance cycles.

Do this to verify that everything is working properly on the new console.

3.Retire the old console.

How exactly you retire the console is up to you and your organization’s policies. You might simply power off the machine, or you might perform a backup and then uninstall Security Controls.

Related Topics

Requirements for Using the Migration Tool

Commonly Asked Questions

Before You Begin

Creating Your Backup Files

Restoring Your Console on a New Machine


Was this article useful?