Chat now with support
Chat with Support

Active Roles 7.5.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 AutoProvisioning for SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Office 365 and Azure Tenant Selection 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
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 One Identity Starling Management One Identity Starling Two-factor Authentication for Active Roles Managing One Identity Starling Connect Azure AD, Office 365, and Exchange Online management
Configuring Active Roles to manage hybrid AD objects Managing Hybrid AD Users Unified provisioning policy for Azure O365 Tenant Selection, Office 365 License Selection, and Office 365 Roles Selection, and OneDrive provisioning Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Office 365 Groups Managing Azure Security Groups Managing cloud-only Azure users Managing cloud-only Azure guest users Managing cloud-only Azure contacts Changes to Active Roles policies for cloud-only Azure objects Managing room mailboxes
Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing 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 Appendix A: Using regular expressions Appendix B: Administrative Template Appendix C: Communication ports Appendix D: Active Roles and supported Azure environments Appendix E: Enabling Federated Authentication Appendix F: Active Roles integration with other One Identity and Quest products Appendix G: Active Roles integration with Duo Appendix H: Active Roles integration with Okta

Database Mirroring setup in Active Roles

Database Mirroring setup in Active Roles

Here we assume 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\7.5.2\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\7.5.2\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 (such as 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 the Restart button at the top of the Administration Service page in the Configuration Center main window. For instructions on how to run Configuration Center, see Running Configuration Center later in this document.

In the Active Roles console, you can view the mirroring status of the Configuration or Management History database that is used by a particular instance of the Administration Service:

  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 box, click the Configuration Database or Management History Database tab, and observe 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 the “Mirroring States” topic at http://msdn.microsoft.com/en-us/library/ms189284.aspx

    If no information is displayed in the Database Mirroring area, then 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 box for the object representing that database in the Configuration/Server Configuration/Configuration Databases or Configuration/Server Configuration/Management History Databases container, respectively.

Best practices

This section provides instructions on how to monitor replication and perform administrative tasks to resolve replication-related problems. The following topics are covered:

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 the Troubleshooting Replication failures section later in this document.

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

Table 111: 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 12:00 a.m. at the Publisher.

You can use the following instructions to examine these settings using SQL Server Management Studio.

It is advisable not to change these settings. Replication may not be functioning correctly if you manually modify replication settings with the use of SQL Server tools.

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 box to connect to the instance of the SQL Server Database Engine that holds the Publisher role.

Open the Publication Properties dialog box:

  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 box, you can review the Active Roles publication settings.

Open the Subscription Properties dialog box:

  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 box, you can review the Active Roles subscription settings.

Replication Agent schedule

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

  • The Snapshot Agent starts every day at 12:00 a.m. at the Publisher.
  • The Merge Agents start automatically when SQL Server Agent starts, and runs continuously at the Publisher.

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. Click the Edit button to examine the replication agent schedule settings in detail.

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. Click the Edit button to examine the replication agent schedule settings in detail.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating