Upgrading an Earlier Version
If an earlier version of the product is already installed, the Setup program first uninstalls the features of the old version, and then installs the features you have selected from the new version.
Setup allows you to import configuration data stored by the previous version. When upgrading the Administration Service, you have the option to copy all data from the old database to the new one. In this way, Setup ensures that the configuration settings, including all permission and policy definitions and assignments, are identical to those used in the earlier installation.
To ensure smooth upgrade to the new version, you should first upgrade the Administration Service and then upgrade the client components (Quest One ActiveRoles console and Web Interface) once you have upgraded the Administration Service.
When upgrading the Administration Service, you should check that the user interfaces are compatible with the new version of the Administration Service. The new Administration Service is only compatible with the Quest One ActiveRoles console (MMC Interface) and Web Interface of version 6.9. Earlier versions of the user interfaces may not work with the new Administration Service and thus need to be upgraded. The user interfaces of Quest One ActiveRoles 6.9 are only compatible with the Administration Service version 6.9. Therefore, to use the Quest One ActiveRoles console or Web Interface version 6.9, you first need to upgrade the Administration Service.
Impact on Quest One ActiveRoles Replication
The upgrade process of the Administration Service does not preserve the replication settings. An upgrade can only be performed if the Administration Service is not configured for replication.
Before upgrading the Administration Service, you should ensure that its database server is not configured as a Subscriber or Publisher. Replication for the new Administration Service needs to be configured after the upgrade.
Impact on Custom Solutions
An upgrade of Quest One ActiveRoles components may affect custom solutions, if any, that rely on the functions of Quest One ActiveRoles. Custom solutions (such as scripts or other modifications) that work fine with the earlier version of Quest One ActiveRoles may cease to work after the upgrade. Prior to attempting an upgrade, you should test the existing solutions with the new version of Quest One ActiveRoles in a lab environment to verify that the solutions continue to work.
Impact on Unmanaged Domains
Upgrade of the Administration Service to version 6.9 converts unmanaged domains to regular managed domains. If you have any domains registered as unmanaged domains with an earlier version of Quest One ActiveRoles, then, after the upgrade, you will need to make them unmanaged by applying the build-in Policy Object Exclude from Managed Scope. For further information and instructions, see “Configuring an Unmanaged Domain” in the ActiveRoles Administrator Guide for version 6.9.
Upgrading the Administration Service
You can upgrade the Administration Service of version 6.7 or 6.8. Direct upgrade of an earlier version to version 6.9. To upgrade an earlier version, you should first upgrade to version 6.8. This section covers the instructions on how to upgrade the Administration Service of version 6.7 or 6.8 to version 6.9. When upgrading the Administration Service, you must choose the option to create a new database along with the option to update that new database by importing data from the old database of the Administration Service you are upgrading. This requires the database server to act as a stand-alone server as applied to Quest One ActiveRoles replication. If the database server is the Subscriber or Publisher role holder, use the Quest One ActiveRoles console to change replication settings as follows:
- For a Subscriber, connect to the Administration Service whose database server holds the Publisher role and remove that Subscriber.
- For the Publisher, connect to the Administration Service that uses the Publisher database server, remove all of its Subscribers, and then demote the Publisher. Then, use the steps below to perform the upgrade.
To upgrade the Administration Service 6.7 or 6.8
- Run autorun.exe, located in the root folder of the Quest One ActiveRoles DVD.
- In the Autorun window, click Quest One ActiveRoles, and then click Administration Service in the list of the product components.
- Follow the instructions in the Setup Wizard.
- On the Service Account Information page, enter the name and password of the user account to be used as the Administration Service account.
- On the ActiveRoles Admin Account page, accept the default setting, or click Browse and select the group or user to be designated as ActiveRoles Admin.
- On the Configuration Storage Options page, verify that the New database, to be created by this setup option is selected.
- On the Database and Connection Settings page, in the Database area, configure the following settings:
- SQL Server Identifies the SQL Server instance on which the database for the new Administration Service will be created.
- Database name The name of the database to be created for the new Administration Service.
- Import data from this database Identifies the database of the Administration Service you are upgrading. To import data from that database to the database of the new Administration Service, select the Import data from this database check box.
The database from which to import data must be located on the SQL Server instance specified in the SQL Server box.
- On the Database and Connection Settings page, in the Connection area, select one of these options:
- Use Windows authentication Configures the Administration Service to connect to SQL Server using the Administration Service account.
- Use SQL Server authentication Configures the Administration Service to connect to SQL Server using a SQL Server login. Type in the login name and password.
- Follow the instructions in the wizard to complete the installation.
Importing Management History Data
A part of the Quest One ActiveRoles database, the Management History data storage is empty after the upgrade of the Administration Service if you choose the option to import data from the database of your existing installation. This behavior is due to the fact that the import operation performed by the Setup Wizard transfers only the configuration data—administrative right assignments, rule-based policy definitions, administrative view settings, and other parameters that determine the Quest One ActiveRoles work environment. The Management History data is excluded from the import operation in order to reduce the time it takes for the Setup Wizard to upgrade the Administration Service.
The Management History data describes the changes that were made to directory data via Quest One ActiveRoles. This includes information on who did what and when it was done as applied to the directory data management tasks. In Quest One ActiveRoles, the Management History data is used as a source of information for the Change History and User Activity reports.
After you have upgraded the Administration Service using the option to import data from the existing database, you need to take some additional steps to transfer the Management History data from your old Quest One ActiveRoles database to the new Quest One ActiveRoles database.The Administration Service installation includes the Management History Migration Wizard to help you perform this task.
To start the Management History Migration Wizard
- On the computer on which you have installed the new version of the Administration Service, click Start, and select All Programs | Quest Software | Quest One ActiveRoles | Management History Migration Wizard.
The wizard is intended to populate a new storage of Management History data with your existing Management History data, to make the data available to the Quest One ActiveRoles user interfaces after your upgrade to the new version of the Administration Service. The wizard merges the Management History data found in the source database with the data stored in the destination database. Note that the wizard only adds new data, keeping intact any data that already exists in the destination database. You may import your old data at any time after you have upgraded the Administration Service, without being afraid of losing any data.
To import Management History data
- Start the Management History Migration Wizard, and follow the instructions on the wizard pages.
- On the Choose the Source Database page, specify the database from which you want to import data (normally, this should be the database that was in use by your earlier version of the Administration Service):
a) Type the name of the SQL Server instance that hosts the database. Specify the name in the form computername for the default instance or computrname\instancename for a named instance.
b) Type the name of the database.
c) Specify the authentication mode. Depending on the option you select, either your Windows account or the SQL Server login you provide must have sufficient rights to retrieve data from the database.
- On the Choose the Destination Database page, specify the database to which you want to import data (normally, this should be the database that is in use by the newly installed Administration Service, which is the default setting on this page):
a) Verify the name of the SQL Server instance that hosts the database. If necessary, type a different name. The name should be in the form computername for the default instance or computrname\instancename for a named instance.
b) Verify the name of the database. If necessary, type a different name.
c) Specify the authentication mode. Depending on the option you select, either your Windows account or the SQL Server login you provide must have sufficient rights to update data in the database.
- On the Records to Migrate page, specify whether you want to import all the data records or a certain range of data records. You may choose not to import all the data records since importing a large volume of data may take hours or more.
- On the Ready to Start page, click Next to start the import operation.