Chat now with support
Chat with Support

Active Roles 7.4.1 - Quick Start Guide

Introduction Active Roles Setup package Active Roles uninstallation System Requirements Deploying the Administration Service Deploying user interfaces Installing additional components Upgrade of an earlier version 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

Deploying the pilot Web Interface

Once you have deployed the pilot Administration Service and updated its configuration, you can deploy the Web Interface for your pilot project. You have to ensure that your pilot instance of the Web Interface meets the following conditions:

  • Uses the Administration Service instance you have deployed for your pilot project (see Deploying the pilot Administration Service earlier in this document).
  • For each of your production Web Interface sites of the earlier Active Roles version, holds a site with the same customizations of the menus, commands, forms and other elements as the production site.

You can address these conditions as follows:

  1. For each of your production Web Interface sites of the earlier Active Roles version, identify and note down the name of the configuration object used by that site.

    You can identify your existing site configuration objects by using the Web Interface Sites Configuration wizard on the computer running your production Web Interface. For detailed instructions, see Upgrading the Web Interface earlier in this document.

  2. Create an instance of the new Web Interface, and configure it to use the Administration Service instance you have deployed for your pilot project. For details, see Upgrading the Web Interface earlier in this document.

    You can install the Web Interface of version Active Roles side-by-side with the Web Interface of version 6.9, on the same computer. Another option is to install the new Web Interface on a different computer.

  3. On the Web Interface instance you have created in Step 2, create Web Interface sites, importing site configuration data from the configuration objects you have identified in Step 1. For instructions, see Upgrading the Web Interface earlier in this document.

Optionally, delete the default sites that were created when you configured the Web Interface in Step 2. The default sites are unaware of your existing site customizations, and have the default configuration of menus, command, forms and other elements. For instructions on how to delete the default Web Interface sites, see Upgrading the Web Interface earlier in this document.

Installing the Active Roles console

Installing the Active Roles console

You need the Active Roles console of version 7.4 if you want the console to connect to the Administration Service of version Active Roles. As the console of version 7.4 does not connect to the Administration Service of earlier versions, the use of the console version Active Roles for your pilot project ensures that the console automatically connects to the pilot Administration Service.

For installation instructions, see Steps to install the console earlier in this document.

Deployment considerations

This section addresses issues concerning the deployment of the Active Roles Administration Service. Information for this section was collected from:

  • Feedback from our current customers who have enterprise class deployments with multiple sites/locations
  • Extensive testing of Active Roles in our software development labs
  • Comparisons and testing of Active Roles to competitors’ solutions

There are no technical requirements for installing many Administration Services in a location or in different locations. The number of Administration Services in a location and the number of locations with Administration Services depends on an organization’s needs and expectations, the current infrastructure and hardware, and the business workflow. When considering an To add the Active Roles console (MMC Interface) to the pilot deployment, simply install the new version of the console on an appropriate server and have the console connect to your pilot Administration Service. deployment, administrators should consider the following issues:

  • Business workflow
  • Hardware requirements
  • Need for availability
  • Replication traffic

When an organization has gathered and assessed the information above, it will be able to determine the locations and number of Administration Services to be installed. The last sub-section provides network diagrams that illustrate potential Active Roles deployments.

Business workflow

This factor focuses on Active Directory (AD) data management processes and practices, including who will perform these tasks and from where they access the management services. Generally, these tasks will be divided among several groups, which might include both high- and low-level administrators, a Help Desk, HR personnel, and work group managers.

Possible business workflows for AD data management processes might be:

  • Centralized at one location and performed by one group
  • Centralized at one location or LAN site and performed by multiple groups
  • Distributed at multiple sites but performed by one business group
  • Distributed at multiple sites and performed by multiple independent business groups

Organizations should diagram the locations/sites at which AD data management is done, their network connections, the number of users performing tasks, the type of work they do. For example, Help Desk personnel will make more use of the Administration Service than regular employees who are occasionally changing their personal information.

Finally, the number of users at each site should be added to the diagram. Current customers report that there has been no need to install additional services in order to improve Active Roles performance. Adding the number of users is not intended to indicate the workload on or the performance of the Administration Service. The number of users is intended to help organizations to estimate and understand their own administration workload and how Active Roles will fit into that workload.

Related Documents