When upgrading to the latest version of Identity Finder Console, it may not be possible to directly upgrade from an existing version to the latest version. In order to preserve existing data while providing new functionality, it may be necessary to upgrade in steps. Please consult the chart below to determine if an upgrade path is necessary.
The following upgrade paths exist:
|If the current version is
||It can be upgraded to
|7.0 or later||9.1 or later||Identity Finder Console|
|4.1.2 - 6.2.1||8.2||Identity Finder Console|
|4.0.2 - 4.1.2||4.1.3||Console 4.1.3|
|2.0 - 4.0.1||4.0.2||Console 4.0.2|
As noted above, all installations of version 4.1.2 and newer can be directly upgraded to the latest version. For future versions, direct upgrading from these versions will be maintained.
If the current version of an existing console is, for example, version 2.1, it will be necessary to first upgrade to version 4.0.2, then to upgrade to version 4.1.3, and then finally to upgrade to version 4.5.
Note: Before each upgrade is initiated, a backup of the console database must be performed. If necessary, consult an experienced database administrator (DBA) for assistance.
Note: Only Endpoint for Windows version 4.0 and later can communicate with versions 4.0.2 and later of the console. Therefore, during the upgrade process from console versions prior to 4.0, it will be necessary to uninstall any version 3.x Windows clients and install clients version 4.0 or later. There is no settings upgrade path from client versions 3.x to 4.x.
Note: Only Endpoint for Mac version 3.0 and later can be managed (accept policies and scheduled) by version 4.5 of the console. Mac 2.x clients can communicate with version 4.5 of the console but cannot be managed.
To upgrade, locate the currently installed version of console in the table above and upgrade to each console version necessary by executing the corresponding installer. To identify the currently installed console, log in to the console and navigate to Settings > Resources to view the installation version. In all cases, the known issues outlined below must be reviewed to ensure that upgrades have completed successfully.
Upgrading to 4.1.3
When upgrading to console version 4.1.3, it is possible for the database update to succeed but for the IIS configuration to fail to complete. To ensure that the 4.1.3 upgrade completed successfully, perform the following steps:
- Log in to the Console and navigate to Settings > Resources and review the version number, which should read 4.1.3.
- Access the Windows desktop of the console server and open the Programs or Add/Remove Programs control panel item. For the Identity Finder Enterprise Console entry, view the properties and ensure that the version reported is 4.1.3.
If the version information in one or both locations does not display 4.1.3, please contact support by opening a new ticket. In the ticket, please include screen shots of both version locations listed above and identify the issue as a failed 4.1.3 console upgrade.
Upgrading to 4.0.2
The 4.0.2 upgrade contains data migration scripts that manipulate data into a new database schema. These scripts run during the installation of version 4.0.2 and must not be interrupted. For large databases, depending on the hardware configuration, this operation can take a few minutes, a few hours, or a few days. If the scripts are interrupted, it may be necessary to restore the database backup and start the upgrade process again.