Chat now with support
Chat with Support

We are currently experiencing an our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

Active Roles 8.1.4 - Administration Guide

Introduction Getting started with Active Roles Configuring rule-based administrative views Configuring role-based administration Rule-based autoprovisioning and deprovisioning
Provisioning Policy Objects Deprovisioning Policy Objects How Policy Objects work Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning Exchange Mailbox AutoProvisioning AutoProvisioning in SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Microsoft 365 and Azure Tenant Selection E-mail Alias Generation User Account Deprovisioning Office 365 Licenses Retention 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
Using rule-based and role-based tools for granular administration Workflows
Key workflow features and definitions About workflow processes Workflow processing overview Workflow activities overview Configuring a workflow
Creating a workflow definition for a workflow 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
Approval workflow Email-based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic groups Active Roles Reporting Management History Entitlement profile Recycle Bin AD LDS data management One Identity Starling Join and configuration through Active Roles Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users Migrating Active Roles configuration with the Configuration Transfer Wizard Managing Skype for Business Server with Active Roles
About Skype for Business Server User Management Active Directory topologies supported by Skype for Business Server User Management User Management policy for Skype for Business Server User Management Master Account Management policy for Skype for Business Server User Management Access Templates for Skype for Business Server Configuring the Skype for Business Server User Management feature Managing Skype for Business Server users
Exchanging provisioning information with Active Roles SPML Provider Monitoring Active Roles with Management Pack for SCOM Configuring Active Roles for AWS Managed Microsoft AD Azure AD, Microsoft 365, and Exchange Online Management
Configuring Active Roles to manage Hybrid AD objects Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Changes to Active Roles policies for cloud-only Azure objects
Managing the configuration of Active Roles
Connecting to the Administration Service Managed domains Using unmanaged domains Evaluating product usage 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
SQL Server replication Using regular expressions Administrative Template Configuring federated authentication Communication ports Active Roles and supported Azure environments Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

Management History configuration

The configuration of Management History includes the following elements:

  • Change-tracking Policy: Builds the data pertinent to history of changes made to directory objects, and specifies what changes are to be included in the reports on change history and user activity.

  • Change Tracking Log Configuration: Specifies how many change requests are to be stored in the log.

  • Replication of Management History Data: Specifies whether to synchronize Management History data between Administration Services that use different databases.

IMPORTANT: Consider the following when migrating the Management History and Configuration databases:

  • The Management History Migration Wizard is designed to perform one-to-one database migration during Active Roles updates, to speed up the upgrade process. This is because migrating the Management History database can take a long time, depending on the size of the deployment history and the particularities of the Active Roles environment.

  • The Management History Migration Wizard was not tested to migrate and merge several Management History databases to a single database instance. Such scenarios are not supported.

  • However, you can re-run the Management History Migration Wizard several times from the same source database. In such cases, the Wizard can merge the changes that occurred in the source database since the last import to the target database.

  • Importing a Configuration database results in the source configuration replacing the target Configuration database, overwriting the current settings of the target system. As Active Roles stores its configuration data in the Configuration SQL database, One Identity strongly recommends backing up the target Configuration database before import.

  • For more information on the supported upgrade paths of Active Roles 8.1.4, see Upgrade and installation instructions in the Active Roles Release Notes. For more information on supported upgrade paths in general, see Knowledge Base Article Active Roles upgrade paths in the One Identity support portal.

Change-tracking policy

The behavior of the Management History feature is defined by the policy held in the build-in Policy Object called Built-in Policy - Change Tracking. The policy determines the object types and properties for which to gather the Management History information.

To view or modify the policy, display the Properties dialog for the Built-in Policy - Change Tracking Policy Object (located in container Configuration/Policies/Administration/Builtin), navigate to the Policies tab, select the policy, and click View/Edit. This displays the Policy Properties dialog. The Object Types and Properties in that dialog lists the object types and properties included in Management History. Each entry in the list includes the following information:

  • Object Type: If an object of this type is modified via Active Roles, information about that action is recorded in the Change Tracking log on condition that the modification affects a property specified in the Properties column.

  • Properties: Information about changes to these properties is recorded in the Change Tracking log.

You can manage the list on the tab by using the buttons beneath the list:

  • Add: Displays the dialog where you can select the object type and properties you want to include in Management History. You have an option to either select individual properties or select all properties.

  • Remove: Deletes the selected entries from the list.

  • View/Edit: Displays the dialog where you can view or modify the properties for the selected list entry.

Change Tracking log configuration

One more configuration setting for Management History determines the size of the Change Tracking log. The log stores information about requests to change directory data, one record per request. Each record includes information about the changes to a certain object that were made in accordance with a certain change request.

You can configure the maximum number of records by managing properties of the Change Tracking Log Configuration object, located in the Configuration/Server Configuration container.

On the Log Settings tab in the Properties dialog for that object, you can select one of the following options:

  • All requests that occurred during last <number> days: Information about change requests is written to the log so that new requests replace those that are older than the specified number of days.

  • This total number of most recent requests: The log stores not more than the specified number of change requests. When the limit is reached, each new request to make changes to directory data replaces the oldest request in the log.

  • This number of most recent requests per object: For every object, the log stores at most the specified number of change requests. When the limit is reached for a certain object, each new request to make changes to the object replaces the oldest request related to that object. The total number of requests depends on the number of objects that are modified via Active Roles.

By default, the Change Tracking log is configured to store information about requests that occurred within last 30 days. Information about change requests is written to the log so that new requests replace those that are older than 30 days. If you increase this number, do it carefully. Increasing this number significantly increases the size of the log. For more information, see Management History considerations and best practices.

NOTE: The Change Tracking log is used as the source of information on both Change History and User Activity. The volume of requests held in the log equally determines the Change History retention time and the User Activity retention time.

NOTE: The limit duration specified in Change Tracking Log Configuration impacts undo-deprovisioning user accounts: you can only undo the deprovisioning of user accounts within the set time duration (the last 30 days by default).

On the Log Record Size tab, you can choose from the options that allow you to reduce the size of the Change Tracking log by logging detailed information about a limited number of change requests, having only basic information about the other change requests logged and thus included in the reports. If the log record of a given change request contains detailed information, then the report on that request provides information about all changes made, along with all policies and workflows performed, by Active Roles when processing the request. Otherwise, the report provides information only about the changes to the object properties made in accordance with the request. Although storing only basic log records results in fewer details in the reports, doing so may considerably decrease the size of the Management History database. The following options are available:

  • All requests: The Change Tracking log contains detailed information about all requests stored in the log.

  • Requests that occurred during last <number> days: Detailed information about requests is written to the log so that new requests with detailed information replace those that are older than the specified number of days.

  • This number of most recent requests: The log stores not more than the specified number of requests containing detailed information. When the limit is reached, each new request with detailed information replaces the oldest request in the log.

  • Don’t log detailed information about any requests: The Change Tracking log contains only basic information about all requests stored in the log.

Replication of Management History data

NOTE: Active Roles does not support replication on Azure SQL databases.

In Active Roles version 7.4 and later, the Management History data is stored in the Active Roles Management History database. So, if you have Active Roles replication configured as described in Configuring replication, the Management History data is replicated between Administration Services along with the configuration data. Given a large volume of the Management History data, this may cause considerable network traffic.

You can turn off replication of Management History data so as to reduce network traffic. However, doing so causes each database server to maintain a separate Management History data store. The result is that you can use Management History to examine the changes that were made only through the Administration Services that use the same database as the Administration Service you are connected to.

To sum up, the implications of turning off replication of Management History data are as follows:

  • The reports produced by the Change History or User Activity command include information only about the changes that were made using a certain group of Administration Service (those Services that share a common database).

    As the Active Roles Console or Web Interface automatically selects the Service to connect to, you may encounter different reports for the same target object or user account during different connection sessions.

  • The features of Active Roles such as Approval Workflow, Temporal Group Memberships, and Undo Deprovisioning may not work as expected. Some operations that rely on those features may not be processed or displayed in a consistent way by client interfaces connected to different Administration Services.

    Active Roles uses the Management History storage to hold approval, temporal group membership, and deprovisioning tasks. Without synchronizing information between Management History storages, such a task created by one of the Administration Services may not be present on other Administration Services. As a result, behavior of the Active Roles Console or Web Interface varies depending on the chosen Administration Service.

Turning off replication of Management History data has no effect on replication of the other data pertinent to the configuration of Active Roles. Only the Management History-related portion of the configuration database is excluded from Active Roles replication.

The instructions on how to turn off replication of Management History data depend upon whether Active Roles replication is already configured.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating