Chat now with support
Chat with Support

Active Roles 7.2.1 - Quick Start Guide

Introduction System Requirements Deploying the Administration Service Deploying user interfaces Installing additional components Upgrade of an earlier version Separate Management History database Performing a pilot deployment Deployment considerations Silent installation of Active Roles components Configuring Active Roles to Manage Hybrid Active Directory Objects Active Roles on Windows Azure VM

Upgrading other components

Upgrade of an earlier version > Upgrading other components

This section covers upgrade options for the following components of Active Roles:

  • Console (MMC Interface)
  • Management Shell
  • ADSI Provider
  • SDK
  • Collector and Report Pack

Upgrade of the Active Roles console

You can install the Active Roles console of version 7.2 side-by-side with the Active Roles console of version 6.9, on the same computer. Another option is to install the new console on a different computer. For installation instructions, see Steps to install the console earlier in the document.

If you no longer need the console of version 6.9 or earlier, you can uninstall it using Programs and Features in Control Panel: Right-click MMC Interface in the list of installed programs, and then click Uninstall.

Upgrade of the Shell, ADSI Provider and SDK

The Active Roles Management Shell, ADSI Provider and SDK of version 7.2 are packaged into a single component referred to as management tools. You can install management tools side-by-side with Active Roles version 6.9, on the same computer. Another option is to install management tools on a different computer. Active Roles Setup installs management tools by default. You can install management tools without installing other components (see Steps to install only the Shell, ADSI Provider and SDK earlier in this document).

If you no longer need the Management Shell that ships with Active Roles 6.9, you can uninstall it using Programs and Features in Control Panel: Right-click Management Shell in the list of installed programs, and then click Uninstall. Note that the Administration Service requires the Management Shell. Do not uninstall the earlier version of Management Shell from the computer running the Administration Service of version 6.9.

The Active Roles SDK is packaged as a feature of the Administration Service installation. You can uninstall it by using the Administration Service Setup wizard in maintenance mode: In Programs and Features, right-click Administration Service, and then click Change to start the Setup wizard. On the Select Features page in the wizard, choose the option to remove the SDK and Resource Kit feature.

The Active Roles ADSI Provider of version 6.9 is normally installed together with any of the Active Roles core components, such as the Administration Service, Web Interface or MMC Interface, and is removed once you have uninstalled the core components.

Upgrade of Collector and Report Pack

The Active Roles reporting components should be upgraded in the following order:

  • Collector
  • Report Pack
  • Collector’s database
Collector

To upgrade, first uninstall your earlier version of Collector and then install the new version. You can uninstall Collector by using Programs and Features in Control Panel. Once you have uninstalled your earlier version of Collector, install the new version. For installation instructions, see Steps to install Collector and Report Pack earlier in this document.

Report Pack

To upgrade, first uninstall your earlier version of the Report Pack and then install the new version. The Report Pack should be uninstalled on the computer that was initially used to install the Report Pack. You can uninstall the Report Pack by using Programs and Features in Control Panel.

Once you have uninstalled your earlier version of the Report Pack, deploy the new version. For instructions, see Steps to install Collector and Report Pack earlier in this document.

Collector’s database

The new version of the Report Pack is incompatible with the database of an earlier Collector version. To create reports based on the events held in that database, you need to import the events to the database of the new Collector version, and then specify the database of the new Collector version as the data source for the reports of the new Report Pack version. For instructions on how to configure the data source, see “Working with reports” in the Active Roles Administrator Guide.

To import events from the database of an earlier Collector version

  1. Start the Collector wizard.

    You can start the Collector wizard by selecting Active Roles 7.2 Collector and Report Pack on the Apps page or Start menu, depending upon the version of your Windows operating system.

  1. On the Select Task page, click Import events from an earlier database version, and then click Next.
  2. On the Source Database page, click Specify, and supply the name and SQL Server of the database used by your Collector of an earlier version. Click Next.
  3. On the Target Database page, click Specify, and supply the name and SQL Server of the database used by your Collector of the current version.
  4. Click Next, and wait while the wizard performs the import.

Separate Management History database

Separate Management History database

After you have installed and configured the Administration Service, Configuration Center allows you to specify a separate database for storing Management History data. This configuration option is intended to support Active Roles deployments where it is impractical to use the same database for both the Management History data and Configuration data. The use of a separate Management History database could reduce replication traffic when multiple Administration Service instances synchronize their configuration data via Active Roles replication, and decrease database size when multiple Administration Service instances share the same Configuration database.

It is important to note that multiple Administration Service instances can be configured to share the same Management History data only if they share the same Configuration data. Data sharing may be achieved by means of Active Roles replication or by having multiple Administration Service instances use the same Configuration or Management History database. For example, if you want two instances of the Administration Service to use the same Management History database, you have to ensure that any one of these conditions is fulfilled: (1) both instances use the same Configuration database or (2) if each of the two instances uses its own Configuration database, the two databases are synchronized by using Active Roles replication; otherwise, you may encounter issues with change history reports or approval workflow.

The Management History data includes:

  • Information about the changes to directory data that were made by Active Roles users. This information is used to prepare change history reports.
  • Information about the approval, temporal group membership, and deprovisioning tasks. This information is used by the Active Roles features such as approval workflow, temporal group memberships, and undo deprovisioning.

Many important features and functions of Active Roles heavily rely on consistency and availability of Management History data. With multiple Administration Service instances sharing the same configuration, it is highly advisable for the Administration Service instances to share the same Management History data. The default configuration of the Administration Service meets this requirement by using a single database to store both Configuration data and Management History data.

However, if you decide to separate the Management History data store from the Configuration data store, you can do this by using Active Roles Configuration Center after initially configuring the Administration Service: The option to store Management History data in a separate database is available on the Connection to Database page in the Change Active Roles Database wizard.

Creating a new database

Separate Management History database > Creating a new database

After you have initially configured the Administration Service instance with the option to create a new Active Roles database, the new database is used to store both the Configuration and Management History data. You can use Configuration Center to create a separate database for storing the Management History data:

  1. Start Configuration Center on the computer running the Administration Service instance you want to configure.

    You can start Configuration Center by selecting Active Roles 7.2 Configuration Center on the Apps page or Start menu, depending upon the version of your Windows operating system.

  1. On the Dashboard page in the Configuration Settings main window, click Manage Settings in the Administration Service area.
  2. On the Administration Service page that opens, click Change in the Active Roles database area.
  3. On the Connection to Database page in the Change Active Roles Database wizard that appears, review the database connection settings for the Configuration database. If the Administration Service uses the SQL Server authentication option, type the password of the SQL login used for connection to the database.
  4. Select the Store management history data in a separate database check box on the Connection to Database page, and then click Next.
  5. On the Management History Database Options page, click New Active Roles database, and then click Next.
  6. On the Connection to Management History Database page, in the SQL Server and Database fields, specify the SQL Server instance and the name of the database in which you want this Administration Service to store its Management History data.
  7. On the Connection to Management History Database page, under Connect using, select the appropriate authentication option:
    1. To have the Administration Service connect to the Management History database using the service account, click Windows authentication.
    2. To have the Administration Service connect to the Management History database using a SQL Server login, click SQL Server authentication and type the login name and password.
  8. Click Next, and follow the instructions in the wizard to complete the configuration.

Using an existing database

Separate Management History database > Using an existing database

If you already have an Administration Service instance that stores its Management History data in a separate database, and want an additional instance to store the Management History data in that same database, you can configure the additional instance as follows:

  1. Start Configuration Center on the computer running the Administration Service instance you want to configure.

    You can start Configuration Center by selecting Active Roles 7.2 Configuration Center on the Apps page or Start menu, depending upon the version of your Windows operating system.

  1. On the Dashboard page in the Configuration Settings main window, click Manage Settings in the Administration Service area.
  2. On the Administration Service page that opens, click Change in the Active Roles database area.
  3. On the Connection to Database page in the Change Active Roles Database wizard that appears, review the database connection settings for the Configuration database.

    If the Administration Service uses the SQL Server authentication option, type the password of the SQL login used for connection to the database.

  1. Select the Store management history data in a separate database check box on the Connection to Database page, and then click Next.
  2. On the Management History Database Options page, click Existing Active Roles database, and then click Next.
  3. On the Connection to Management History Database page, in the SQL Server and Database fields, specify the SQL Server instance and the name of the database in which you want this Administration Service to store its Management History data.
  4. On the Connection to Management History Database page, under Connect using, select the appropriate authentication option:
    • To have the Administration Service connect to the Management History database using the service account, click Windows authentication.
    • To have the Administration Service connect to the Management History database using a SQL Server login, click SQL Server authentication and type the login name and password.
  5. Click Next, and follow the instructions in the wizard to complete the configuration.
Related Documents