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

Database mirroring setup in Active Roles

This section is based on the assumption that mirroring for the database of Active Roles is already set up on the SQL Server side in accord with the recommendations and instructions found in Microsoft’s documentation, so that the following conditions are fulfilled:

  • The Administration Service is connected to the Configuration database on the principal database server.

  • Replication is not configured for the Configuration database (the database server acts as a stand-alone server as applied to Active Roles replication).

  • The Administration Service is connected to the Management History database on the principal database server (by default, the Management History database is the same as the Configuration database).

  • Replication is not configured for the Management History database (the database server acts as a stand-alone server as applied to Active Roles replication).

Under these conditions, the Administration Service can be instructed to automatically connect to the new principal database in the event of database server role switching. On the computer running the Administration Service, add a string value to each of these two registry keys, and then restart the Administration Service:

  • Key: HKLM\SOFTWARE\One Identity\Active Roles\8.1.4\Service\DatabaseConnectionString\

    Value Name: Failover Partner

    Value Data: <Identifies the SQL Server instance that currently owns the mirror server role for the Configuration database>

  • Key: HKLM\SOFTWARE\One Identity\Active Roles\8.1.4\Service\CHDatabaseConnectionString\

    Value Name: Failover Partner

    Value Data: <Identifies the SQL Server instance that currently owns the mirror server role for the Management History database>

If the default instance is used, the value data is the short name of the computer running SQL Server. Otherwise, the value data is the short name of the computer, followed by a backslash (\), followed by the name of the instance, for example, ComputerName\InstanceName.

By default, the same database is used for the Configuration and Management History data; therefore, the value data would be the same in the DatabaseConnectionString and CHDatabaseConnectionString keys.

To restart the Administration Service, open Configuration Center and click Restart at the top of the Administration Service page in the Configuration Center main window. For more information on how to run Configuration Center, see Running Configuration Center.

To view the mirroring status of the Configuration or Management History database that is used by a particular instance of the Administration Service in the Active Roles Console

  1. In the Console tree, select Configuration > Server Configuration > Administration Services.

  2. In the Details pane, double-click the name of the Administration Service whose database you want to examine.

  3. In the Properties dialog, click the Configuration Database or Management History Database tab, and view the information in the Database mirroring area:

    • Role: Current role of the database in the database mirroring session (Principal or Mirror).

    • Partner: The instance name and computer name for the other partner in the database mirroring session.

    • State: Current state of the mirrored database and of the database mirroring session. For more information about this field, see Mirroring States.

    If no information is displayed in the Database Mirroring area, it means that the database mirroring is not configured.

You can also view the mirroring status of a Configuration database or a Management History database on the General tab in the Properties dialog for the object representing that database in the Configuration/Server Configuration/Configuration Databases or Configuration/Server Configuration/Management History Databases container, respectively.

Viewing replication settings

When configuring replication, Active Roles automatically sets replication parameters to the appropriate values. This ensures that replication is functioning properly. Normally, there is no need to modify the replication settings except for some error situations outlined in Troubleshooting replication failures.

The following table lists the values that Active Roles assigns to certain replication parameters.

Table 119: Values assigned to Replication parameters

Replication Parameter

Value

Publication name

AelitaReplica

Replication type

Merge

Subscription type

Push

Subscription expiration

Subscriptions expire and may be dropped if not synchronized in 60 days.

Schedule

The Merge Agents are running continuously at the Publisher. The Snapshot Agent starts daily at 00:00 at the Publisher.

To view the replication parameters using SQL Server Management Studio,

CAUTION: Do not change these settings. Replication might not work correctly if you manually modify replication settings with the use of SQL Server tools.

  1. Start Management Studio and connect to the Publisher SQL Server:

    1. In Object Explorer, click Connect, and then click Database Engine.

    2. Complete the Connect to Server dialog to connect to the instance of the SQL Server Database Engine that holds the Publisher role.

  2. Open the Publication Properties dialog:

    1. In Object Explorer, under the Publisher SQL Server, expand Replication > Local Publications.

    2. In Object Explorer, under Local Publications, right-click AelitaReplica, and click Properties.

    In the Publication Properties dialog, you can review the Active Roles publication settings.

  3. Open the Subscription Properties dialog:

    1. In Object Explorer, under Local Publications, expand AelitaReplica.

    2. In Object Explorer, under AelitaReplica, right-click a Subscription, and click Properties.

    In the Subscription Properties dialog, you can review the Active Roles subscription settings.

Replication Agent schedule

By default, Active Roles schedules the Replication Agents to run at the Publisher as follows:

  • The Snapshot Agent starts every day at 00:00.

  • The Merge Agents start automatically when SQL Server Agent starts, and runs continuously.

To verify the Snapshot Agent schedule

  1. Open SQL Server Management Studio.

  2. In Object Explorer, connect to the instance of the SQL Server Database Engine that holds the Publisher role, and then expand that instance.
  3. Right-click the Replication folder, and click Launch Replication Monitor.
  4. In the left pane of the Replication Monitor window, expand your Publisher SQL Server, and click AelitaReplica.

  5. In the right pane of the Replication Monitor window, on the Warnings and Agents tab, right-click the Snapshot Agent in the Agents and jobs related to this publication list, and click Properties.

  6. In the left pane of the Job Properties window, click Schedules.
  7. Review the Replication Agent schedule settings in the right pane of the Job Properties window.
  8. To view the Replication Agent schedule settings in detail, click Edit.

To verify the Merge Agent schedule

  1. Open SQL Server Management Studio.

  2. In Object Explorer, connect to the instance of the SQL Server Database Engine that holds the Publisher role, and then expand that instance.
  3. Right-click the Replication folder, and click Launch Replication Monitor.
  4. In the left pane of the Replication Monitor window, expand your Publisher SQL Server, and click AelitaReplica.

  5. In the right pane of the Replication Monitor window, on the All Subscriptions tab, right-click the subscription whose Merge Agent you want to examine, and click View Details.

  6. In the Subscription window, on the Action menu, click Merge Agent Job Properties.

  7. In the left pane of the Job Properties window, click Schedules.
  8. Review the Replication Agent schedule settings in the right pane of the Job Properties window.
  9. To view the Replication Agent schedule settings in detail, click Edit.

Identifying replication-related problems

To identify replication-related problems, you can use the Active Roles Console connected to the Publisher Administration Service. If there are any replication failures, a red triangle is displayed on the Server Configuration and Configuration Databases containers in the Console tree. In the Details pane, the same icon is used to highlight the database affected by a replication failure.

If you have encountered a replication failure, you should ensure that the SQL Server Agent service is started on the computer that is running the Publisher SQL Server, and then use SQL Server Management Studio to get more information on that failure.

To ensure that the SQL Server Agent service is started on the computer that is running the Publisher SQL Server

  1. In Object Explorer, connect to the instance of the SQL Server Database Engine that holds the Publisher role, and then expand that instance.

  2. Right-click the Replication folder, and click Launch Replication Monitor.

  3. In the left pane of the Replication Monitor window, expand your Publisher SQL Server, and click AelitaReplica.

  4. In the right pane of the Replication Monitor window, on the Warnings and Agents tab, under Agents and jobs related to this publication, look for the icon. This icon indicates a Snapshot Agent error:

  5. Right-click the agent that has encountered an error and then click View Details.

  6. In the Snapshot Agent window, read the error description under Error details or message of the selected session.

  7. In the right pane of the Replication Monitor window, on the All Subscriptions tab, in the list of subscriptions, look for the icon. This icon indicates a Merge Agent error:

  8. On the All Subscriptions tab, right-click the subscription that has encountered an error and then click View Details.

  9. In the Subscription window, view the error description under Last message of the selected session.

For more information on typical errors and how to resolve them, see Troubleshooting replication failures.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating