Review these special considerations before running an upgrade.
Upgrading a coordinator that is using Azure SQL Managed Instance for the database configuration
Starting with Change Auditor 6.0, on the coordinator startup the database collation is checked against SQL server collation. If they are different, the coordinator stops and logs the “Database collation differs from server collation” warning. If it is not possible to update collation of the SQL server, use the AllowCollationSwitch registry key to allow proceeding with rebuilding Change Auditor database according to the new collation. However, using this in environment with large number of events in the database significantly increases the load on SQL server. See the Change Auditor Technical Insight Guide for more information about setting this registry key.
HKLM\SOFTWARE\Quest\ChangeAuditor\Coordinator
To ensure success, upgrade the Change Auditor components in the following order:
2 |
Log on to the coordinator server to upgrade and browse to the folder where the Change Auditor package was downloaded, and run the Quest Change Auditor Coordinator (x64).msi file to open the Change Auditor Coordinator Setup wizard. |
1 |
From a workstation, laptop, or member server, browse to the folder where the Change Auditor package was downloaded, and run the Quest Change Auditor Client (x64).msi file to open the Change Auditor Client Setup wizard. |
1 |
On the IIS server, browse to the folder where the Change Auditor package was downloaded, and run the Quest Change Auditor Web Client (x64).msi file to open the Change Auditor Web Client Setup wizard. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center