Chat now with support
Chat with Support

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

Configuring replication

Active Roles uses the replication functionality of Microsoft SQL Server to copy and distribute configuration data from one Administration Service database to another, and to synchronize data among the databases for consistency.

Administration Service database servers synchronized by using the SQL Server replication function are referred to as replication partners. Each replication partner maintains a writable copy of the Service’s configuration and Management History data. Whenever changes are made to one replication partner, the changes are propagated to the other replication partners.

About replication groups

The Publisher and its Subscribers constitute a replication group. Every replication group must include a single Publisher and it can include any number of Subscribers. The members of a replication group are referred to as replication partners.

Each member of a replication group (replication partner) maintains a separate, writable copy of the Administration Service’s configuration and management history data. Replication copies and distributes data from one member database to another, and synchronizes data between the databases for consistency. When changes are made on the Publisher, the Publisher replicates these changes to each Subscriber. When data changes are made on a Subscriber, the Subscriber propagates the changes to the Publisher, which in turn replicates them to the other Subscribers.

This replication process ensures the same configuration for all Administration Services that use the database servers belonging to the replication group.

When it is initially set up, the Administration Service database server is configured as a standalone database. That is, it does not have replication partners and does not belong to any replication group. The Administration Service that uses a standalone database server is referred to as standalone Administration Service.

It is possible to add a standalone database server to any replication group that already exists. When you do that, the database server becomes a Subscriber. Each Administration Service database server can belong to only one replication group. Once removed from a replication group, it can be added to a different group.

To create a new replication group, you must designate a standalone database server as the Publisher. The new replication group will then have a single member—the Publisher. Later, you can add Subscribers to the group.

If there are any replication failures in Active Roles, the Active Roles Console provides a visual indication of this issue by modifying the icon of the Server Configuration and Configuration Databases containers in the Console tree: a label with the exclamation point appears next to each of the containers. This allows the administrator to detect a replication failure without examining individual replication partners.

Creating a replication group

To create a replication group, designate a standalone Administration Service database server as the Publisher. You can do that by using the Active Roles Console

To create a replication group

  1. Connect to a standalone Administration Service.

  2. Promote the Administration Service database server to Publisher.

For more information on how to connect to the Administration Service, see Connecting to the Administration Service.

Once connected to the Administration Service, perform the following steps to promote the Administration Service database server to Publisher.

To promote the Administration Service databse server to Publisher

  1. In the Console tree, navigate to the Configuration/Server Configuration/Configuration Databases container.

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

NOTE: The Promote command is only displayed if the Administration Service uses a standalone database server, that is, a database server that does not belong to any replication group.

After you click Promote, it takes several minutes to complete the operation. When the operation is completed, the new replication group has a single member—the Publisher. Once the replication group has been created, you can add replication partners—Subscribers.

After the Promote operation is completed, both the configuration and Management History databases are replicated.

If Active Roles does not have sufficient rights to perform the Promote operation on SQL Server, then the Active Roles Console prompts you to supply an alternative account for that operation. For more information, see “Permissions for creating or removing the Publisher” in the Active Roles Quick Start Guide.

Adding members to a replication group

To add a member to a replication group, designate a standalone database server as a Subscriber of the group’s Publisher.

CAUTION: Hazard of data loss!

The Publisher copies new data to the database, overwriting the existing data. If the database contains valuable information, such as custom Access Templates or Policy Objects, you should export those objects before designating the database as a Subscriber, and import them back after the operation is completed.

To add a replication partner to a replication group

  1. Connect to the Administration Service whose database server holds the Publisher role.

    For more information on how to connect to the Administration Service, see Connecting to the Administration Service.

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

  3. In the details pane, right-click the Publisher, and click Add Replication Partner.

  4. Follow the instructions in the New Replication Partner wizard.

  5. On the Database Selection page, click Browse.

  6. To configure the SQL Server of an Administration Service as a Subscriber to a Publisher, specify the corresponding Administration Service in the Connect to Administration Service dialog.

    If Active Roles does not have sufficient rights to perform the Add Replication Partner operation on SQL Server, then the wizard prompts you to supply an alternative account for that operation. For more information, see “Permissions for adding or removing a Subscriber” in the Active Roles Quick Start Guide.

    The next page of the wizard displays the database name and location retrieved from the specified Administration Service, and prompts you to select one of the following options that determine how the Replication Agent running on the Publisher SQL Server will connect to the Subscriber SQL Server.

  7. Choose one of these options:

    • Impersonate SQL Server Agent service account: Use this option if the SQL Server Agent service on the Publisher SQL Server is configured to log on as a Windows user account that has sufficient rights on the Subscriber SQL Server. If you select this option, the Replication Agent connects to the Subscriber SQL Server under the logon account of the SQL Server Agent service running on the Publisher SQL Server.
    • Use SQL Server Authentication with the following login and password: Use this option if the SQL Server Agent service logon account cannot be configured to have sufficient rights on the Subscriber SQL Server. You are prompted to specify the SQL Server login and password that the Replication Agent running on the Publisher SQL Server will use to connect to the Subscriber SQL Server.
    The account that the Replication Agent uses to connect to the Subscriber SQL Server must at minimum be a member of the db_owner fixed database role in the subscription database (Active Roles database on the Subscriber). For more information, see Replication Agent permissions in the Active Roles Quick Start Guide.

  8. Click Next, and the click Finish.

NOTE: Consider the following when adding a replication partner to a replication group:

  • After you click Finish, the database server is added to the replication group. The replication process updates the database of the new Subscriber with the data retrieved from the Publisher.

  • A database cannot be added to a replication group if it already belongs to another replication group. To add the database to another replication group, you must first remove it from its current replication group, and then add it to the other one.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating