Upgrade is supported for the following InTrust versions:
This guide describes upgrading extended InTrust deployments, not default InTrust deployments.
To upgrade a default deployment, simply close all running InTrust client components and run the Default InTrust Suite on a computer where a previous version is installed in the default configuration.
|
Caution:
|
To upgrade your installation of InTrust, you have to upgrade all InTrust servers in your organization using the InTrust suite setup. Below are several recommendations on the steps you should take before starting the upgrade procedure.
InTrust configuration objects are never overwritten during upgrade, so in some cases you need them to be recreated. Due to Syslog message parser modifications in the "Redhat Linux Syslog" data source, this data source needs to be deleted before the upgrade so that setup can install its updated version. Note that renaming the data source is not a substitute for this, because it is not identified by name. The updated data source will become available as soon as the first InTrust server in the organization has been upgraded.
If you have customized the "Redhat Linux Syslog" data source and want to keep your modifications, make a copy of the data source before deleting it. After the upgrade, you can use the copy to transfer your modifications to the updated predefined data source.
For predefined configuration objects (such as tasks, real-time monitoring rules and data sources), it is InTrust policy not to overwrite their existing versions with the updated versions during upgrade. This approach ensures that your configuration, which is most likely customized, keeps working without changes during and after the upgrade, but it also means that in the usual course of an upgrade, these changed objects do not end up in your InTrust infrastructure.
InTrust releases newer than your current version may include fixed or enhanced versions of out-of-the-box configuration objects. If an InTrust version introduces any significant changes to such objects, the details are described in the Release Notes for that version, in the Enhancements and Resolved Issues topics. Check these topics to find out what exactly has changed in the configuration objects.
If you want the newer versions of such objects and you find that the upgrade has not deployed them, contact Quest Support for recommendations on the procedure that will best suit you.
If you plan to work with InTrust accessing the databases under a dbo account, you can proceed to Step 2.
Otherwise (that is, if your InTrust databases were accessed using a non-dbo account or you plan to use such an account when working with InTrust), take the following steps:
|
Caution: These scripts are shipped with the distribution of your new InTrust version in the Scripts\Database Scripts folder. The scripts must be run using an account with the dbo role. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center