サポートと今すぐチャット
サポートとのチャット

Active Roles 8.2 - Administration Guide

Introduction Getting started with Active Roles Configuring rule-based administrative views Configuring role-based administration Configuring rule-based autoprovisioning and deprovisioning
Configuring Provisioning Policy Objects
User Logon Name Generation E-mail Alias Generation Exchange Mailbox AutoProvisioning Group Membership AutoProvisioning Home Folder AutoProvisioning Property Generation and Validation Script Execution O365 and Azure Tenant Selection AutoProvisioning in SaaS products
Configuring Deprovisioning Policy Objects
User Account Deprovisioning Group Membership Removal User Account Relocation Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Permanent Deletion Office 365 Licenses Retention Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Script Execution Notification Distribution Report Distribution
Configuring entry types Configuring a Container Deletion Prevention policy Configuring picture management rules Managing Policy Objects Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Configuring policy extensions
Using rule-based and role-based tools for granular administration Workflows
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
Azure tenant types and environment types supported by Active Roles Using Active Roles to manage Azure 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 and URLs used by Active Roles Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

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 the last 30 days. Information about change requests is written to the log so that new requests replace those that are older than 30 days.

CAUTION: Increase this value carefully, as increasing this number significantly increases the size of the log. For more information, see Management History considerations and best practices in the Active Roles Best Practices Guide.

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.

Replication is not yet configured

When initially configuring Active Roles replication, you can ensure that the Management History data will not participate in Active Roles replication by assigning the Publisher role as follows (for definitions of the replication roles, see Configuring replication):

  1. With the Active Roles Console, connect to the Administration Service whose SQL Server you want to hold the Publisher role.

  2. In the Console tree, expand Configuration > Server Configuration and select the Configuration Databases container.

    NOTE: The Replication Support column is added under configuration databases container to indicate the replication support.

    If the value of this column is Supported, it indicates that the replication is allowed for the database. If the value of this column is Unsupported value indicates that the database does not allow replication.

  3. In the details pane, right-click the database, and click Promote.

  4. Wait while the console performs the Promote operation.

  5. In the Console tree, under Server Configuration, select the Management History Databases container.

  6. In the details pane, right-click the database, and click Demote.

  7. Wait while the Console completes the Demote operation.

Then, you can configure Active Roles replication by using the Active Roles Console as described in Configuring replication: Use the Add Replication Partner command on the database in the Configuration Databases container to add Subscribers to the Publisher you have configured.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択