Chat now with support
Chat with Support

Active Roles 7.2 - Administration Guide

Introduction About Active Roles Getting Started Rule-based Administrative Views Role-based Administration
Access Templates as administrative roles Access Template management tasks Examples of use Deployment considerations Windows claims-based Access Rules
Rule-based AutoProvisioning and Deprovisioning
About Policy Objects Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning E-mail Alias Generation Exchange Mailbox AutoProvisioning Home Folder AutoProvisioning Script Execution User Account Deprovisioning Group Membership Removal Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Relocation User Account Permanent Deletion Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Notification Distribution Report Distribution
Deployment considerations Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Container Deletion Prevention policy Picture management rules Policy extensions
Workflows
Understanding workflow Workflow activities overview Configuring a workflow
Creating a workflow definition Configuring workflow start conditions Configuring workflow parameters Adding activities to a workflow Configuring an Approval activity Configuring a Notification activity Configuring a Script activity Configuring an If-Else activity Configuring a Stop/Break activity Configuring an Add Report Section activity Configuring a Search activity Configuring CRUD activities Configuring a Save Object Properties activity Configuring a Modify Requested Changes activity Enabling or disabling an activity Enabling or disabling a workflow Using the initialization script
Example: Approval workflow E-mail based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic Groups Active Roles Reporting Management History
Understanding Management History Management History configuration Viewing change history
Workflow activity report sections Policy report items Active Roles internal policy report items
Examining user activity
Entitlement Profile Recycle Bin AD LDS Data Management Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing managed domains Using unmanaged domains Evaluating product usage Configuring replication Using AlwaysOn Availability Groups Using database mirroring Creating and using virtual attributes Examining client sessions Monitoring performance Customizing the console Using Configuration Center Changing the Active Roles Admin account Enabling or disabling diagnostic logs Active Roles Log Viewer
Using regular expressions Administrative Template Communication ports

Re-configuring replication of Management History data

Management History > Management History configuration > Replication of Management History data > Re-configuring replication of Management History data

With replication of Management History data turned off, it is still possible to have multiple Administration Services maintain the same Change History log by configuring them to use the same database. Note that the Administration Service version 6.x allows you to install multiple Services with the option to connect to a single configuration database. Thus, you can install the first Service in your environment, having the Setup program create a database. Then, you can install one more Service, having the Setup program configure the new Service to use the same database as the existing Service.

However, if different Administration Services in your environment use different database servers, you may need to re-configure replication of Management History data in order to take full advantage of the Management History feature. You can do so by managing objects in the Management History Databases container as follows.

To re-configure replication of Management History data

  1. With the Active Roles console, connect to the Administration Service whose SQL Server holds the Publisher role for configuration data.
  2. In the console tree, expand Configuration | Server Configuration, and select the Management History Databases container.
  3. In the details pane, right-click the database, and click Promote.
  4. Wait while the console performs the Promote operation.
  5. Use the Add Replication Partner command on the Publisher database in the Management History Databases container to add Subscribers for Management History data.

The Add Replication Partner command starts the wizard that is similar to that discussed in the Adding members to a replication group section later in this document. The only difference is that the list of Administration Services whose database servers can be designated as Subscribers for Management History data is limited to those Services that share the configuration data hosted on the Publisher you have selected.

Centralized Management History storage

Management History > Management History configuration > Centralized Management History storage

With the default replication settings in Active Roles, the Management History data is synchronized between replication partners, along with the Configuration data. Given a large volume of Management History data, this behavior may result in high network traffic and may cause performance degradation of Active Roles in certain scenarios, such as when adding a new partner to the Active Roles replication group. Here you can find instruction on how to eliminate replication of Management History data by implementing a common storage of that data for all replication partners.

Synchronization of the Management History data can be removed from the Active Roles replication process by implementing a common storage of that data for all replication partners. The common storage ensures the consolidation of the portions of Management History data that are generated by different Administration Services, while eliminating the need to synchronize that data between multiple storages.

Active Roles provides the following options to implement a centralized, common storage for the Management History data:

  • Configure the Administration Services so that the Configuration database of one of them is used as the Management History storage by the others. In this way, all the Administration Services that share common configuration use the same Management History storage - the Configuration database you chose to hold this role.
  • Create a separate database to store the Management History data, and then configure the Administration Services to use that database rather than their Configuration databases as the Management History storage. In this way, all the Administration Services that share common configuration use the same Management History storage - the Management History database you created.

Option 1: Dedicated Configuration database to store the Management History data

Management History > Management History configuration > Centralized Management History storage > Option 1: Dedicated Configuration database to store the Management History data

By default, the Administration Service stores both its Configuration data and its Management History data in the same Configuration database. As a result, in case of multiple Configuration databases, the Management History data needs to be synchronized via replication, along with the Configuration data, in order to consolidate the Management History data.

Active Roles provides the option to re-configure the Administration Services that share common configuration so that a single Configuration database is used to store the Management History data for all Administration Services. This option gives you the flexibility of distributing the storage of Configuration data while centralizing the storage of Management History data. Use the following instructions to implement this scenario.

  1. Turn off replication of Management History data. You can do this by using the Active Roles console: Connect to the Administration Service whose database server holds the Publisher role in the replication group, go to the Configuration/Server Configuration/Management History Databases/ container, delete all the Subscriber objects from that container, and then run the Demote command on the Publisher object in that container.
  2. Decide on which Configuration database will be used as the common storage for the Management History data.
  3. Configure each of your Administration Service instances to store Management History data in the database you chose in the previous step. You can perform this task by using Active Roles Configuration Center as follows.

To store Management History data in a particular, existing database

  1. Start Configuration Center on the computer running the Administration Service, or connect Configuration Center to that computer.

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

  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.

Option 2: Separate database to store the Management History data

Management History > Management History configuration > Centralized Management History storage > Option 2: Separate database to store the Management History data

Active Roles also provides the option to store the Management History data in a separate Management History database instead of using the same database to store both the Configuration data and Management History data. With this option, multiple Administration Services can be configured to share a common Management History database on a dedicated SQL Server.

If you want a group of Administration Services to use the same Management History database, you should ensure that the Administration Services in the group have the same configuration. This may be achieved in one of these ways:

  • Use the Active Roles replication function to synchronize the Configuration databases that are in use by the Administration Services.
  • Have all the Administration Services in the group use the same Configuration database.

With the same configuration of all the Administration Services, including the configuration of the Web Interface and managed domains, you prevent any inconsistencies in the Management History data that is shared between the Administration Services.

Use the following steps to implement the scenario based on this option.

  1. Turn off replication of Management History data. You can do this by using the Active Roles console: Connect to the Administration Service whose database server holds the Publisher role in the replication group, go to the Configuration/Server Configuration/Management History Databases/ container, delete all the Subscriber objects from that container, and then run the Demote command on the Publisher object in that container.
  2. Create the Management History database and assign it to one of your Administration Service instances, and then configure the other instances of the Administration Service to store Management History data in the database you have created. You can perform these tasks in Active Roles Configuration Center by using the instructions that follow.
  3. Optionally, populate the new Management History database with the Management History data that already exists in your Active Roles environment. For instructions, see Importing data to the new Management History database later in his section.

To create a separate Management History database for the Administration Service

  1. Start Configuration Center on the computer running the Administration Service, or connect Configuration Center to that computer.

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

  1. On the Dashboard page in the Configuration Center 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 New 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.

After you have created the Management History database for one of your Administration Service instances, configure the other instances of the Administration Service to store Management History data in that database. The steps to perform this task are similar to the steps for creating the database, with the only difference that you should select the Existing Active Roles database option on the Management History Database Options page in the Change Active Roles Database wizard.

Related Documents