Note: The Console should be upgraded to the current version before any clients are upgraded to the current version.
Note: A valid license is required for any new version. An updated license can also be obtained from your Customer Portal.
Upgrade the Console before upgrading the clients.
To upgrade the console, please follow the instructions below:
Note: If the database recovery mode is set to FULL then it may take much longer for the upgrade to be performed on the database and it may timeout. To avoid this possible issue it is now required that the database recovery mode is set to SIMPLE.
Note: When upgrading the Console, if there is a Service Task running it may need for that Service Task to complete and could timeout in the process so stopping the Server Service before running the installer to upgrade can avoid that issue.
a) Backup the database. It is also good to have screenshots of all the CAT screens saved in a document for your reference.
b) Ensure that the system requirements listed in the following article are met as they may have changed since the previous version you are on.
c) Ensure that all the required IIS Roles and Services that are needed are installed.
d) Ensure that the CAT (Console Administrator Tool) and the Server Manager are not opened when you are running the installer to upgrade the console. Also ensure that SSMS (SQL Server Management Studio) is not open with a connection to the database.
e) Ensure that you have downloaded your new license for the current version from the licensing portal.
f) Remove all Client Updates from the tabs on the Console's>Admin>Client Updates (Endpoint Updates on version 10.x and above) screens before running the installer to upgrade as shown in the following linked user guide: http://www.identityfinder.com/Help/EnterpriseConsole/index.htm#3483.htm
g)The user logged into the server to run the installer must have sa privileges to perform the upgrade as explained in the following linked article: https://support.spirion.com/hc/en-us/articles/115000827251
Ensure that all the steps in the following article concerning upgrading the console are followed, including the 'Important Notes' at the beginning of the article, and step #16 'Additional Steps':
Ensure that any warnings received during the Pre-Deployment Validation rules are addressed. When a warning is received the details of the warning can be viewed by clicking on the Warning link. More information about any warning can be found here: https://support.spirion.com/hc/en-us/articles/115000019051
Ensure that if you receive warnings about insufficient disk space that you do not continue the upgrade until that issue is resolved.
Ensure that at the end of the installer running that you receive the screen showing that the upgrade was successful, not showing that it failed.
h) After the installer is finished the upgrade then the Console web application must be opened and logged into as that completes the upgrade process.
After Upgrading please follow the instructions in the following linked article:
After upgrading to version 10 Console when opening the Console from a browser on another machine other than the Console server you get error 403, or if when opening the Console from the localhost/console you get the error 403.14, you will need to run the following hotfix
After upgrading the Console, please navigate in a browser to the URL of the Console server/services page. Once on that page select the Test Services Connection link. If when testing that link you receive the following error, that is caused by the CAT being configured to allow https connections for the Services application however there is no binding for https configured in IIS Manager.
If you do receive the following error when testing the Services connection please either change the configuration in the CAT to only allow http connections or add the binding for https in IIS Manager.
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace: [InvalidOperationException: Could not find a base address that matches scheme https for the endpoint with binding...
Upgrading Windows Clients/Endpoints:
To upgrade the Windows Clients please build a MSI using the Identity Finder MSI Builder for the version you are upgrading to. The following article has instructions and a download link for the various versions of the MSI Builder at the bottom of the article.
Identity Finder MSI Builder.
Please ensure you configure the following setting as "Check and Fail" in a System Policy applied to the endpoint to avoid any issues where the plugin files are not able to be written over when upgrading because the Office applications are open at the time of the upgrade:
Please see the Details tab of that setting when editing it to see the full explanation of the setting.
Upgrading Mac clients:
The following article has instructions and a download link for the Identity Finder Package Builder scripts:
Once the new version MSI or PKG is built with your new license in it, then it should be run manually on a couple of machines to ensure that there are no issues. The Client should upgrade, the Client should be able to be opened interactively, the endpoint should be shown on the Console as polling the Console and results of a search that found matches should be able to be uploaded and imported into the Console and then viewed on the endpoint's Results screen. The Test Data can be used for that test.
Then if that is all good then you can upgrade the Clients by adding the MSI to the Console's>Admin>Endpoint Updates page as explained in the following linked user guide: