Chat now with support
Chat with Support

Active Roles 7.5.3 - 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

Moving the Publisher role

In the Active Roles replication model, a replication group includes the Publisher and may include several Subscribers. The Publisher plays a special role in the replication group: it synchronizes data changes between Subscribers. In some scenarios, you may want to move the Publisher role to another SQL Server.

For example, you might need to move the Publisher role to a different SQL Server if the service level becomes insufficient. Given that the Publisher receives and synchronizes data changes from all Subscribers, the volume of requests being serviced by the Publisher increases as the number of Subscribers grows. Respectively increases the workload for SQL Server that holds the Publisher role so its performance can suffer. To resolve this problem, you can transfer the Publisher role to another, more powerful server.

This section provides instructions on how to reconfigure the existing replication group so that the Publisher role is assigned to SQL Server other than the current Publisher. You can perform this task using the Active Roles console connected to the Administration Service whose database server currently holds the Publisher role (Publisher Administration Service).

 NOTE: The Publisher Administration Service must be up and running. If the Publisher is unavailable, you can move the Publisher role using the instructions outlined in the next section of this document.

Open the Active Roles console and connect to the Publisher Administration Service:

  1. Look for the Active Roles Console application, and then click to start that application.
  2. Right-click the console tree root, click Connect, and then select the Administration Service whose database server currently holds the Publisher role.

Use the Active Roles console to remove all Subscribers and to demote the Publisher as follows:

  1. In the console tree, expand Configuration | Server Configuration, and select Configuration Databases.
  2. In the details pane, right-click a Subscriber, and click Delete.
  3. In the confirmation message box, click Yes.
  4. Repeat Steps 2–3 for each Subscriber.
  5. In the details pane, right-click the Publisher, and click Demote.
  6. In the confirmation message box, click Yes.
  7. Wait while Active Roles demotes the Publisher.

After these steps, you can promote the appropriate SQL Server to Publisher and designate the other SQL Servers as Subscribers to the new Publisher, thus configuring the new replication group.

 TIP: After you add a Subscriber, the configuration data stored on the Publisher is replicated to the Subscriber, overriding the data on that Subscriber. Therefore, in order to retain your existing Active Roles configuration, it is advisable to assign the Publisher role to SQL Server that belonged to the old replication group. This ensures that each Administration Service in the new replication group inherits the configuration that was in place when you removed the Subscribers and demoted the Publisher.

To configure the new replication group, perform the following steps using the Active Roles console:

  1. Right-click the console tree root, click Connect, and then select 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.
  3. In the details pane, right-click the database and click Promote.
  4. In the confirmation message box, click Yes.
  5. Wait while Active Roles performs the operation.
  6. In the details pane, right-click the Publisher, and click Add Replication Partner.
  7. On the Welcome page in the New Replication Partner wizard, click Next.
  8. On the Database Selection page, click Browse.
  9. In the Connect to Administration Service dialog box, select the Administration Service whose SQL Server is to be configured as a Subscriber to this Publisher. Click OK.
  10. In the New Replication Partner wizard, click Next, click Next, and then click Finish.
  11. Repeat Steps 6–10 for each SQL Server you want to make a Subscriber.

Recovering replication if Publisher is not available

Once the Publisher becomes unavailable, Subscribers cannot synchronize configuration data. The only way that replication can be recovered is by restoring the current Publisher or making another SQL Server the Publisher.

If the current Publisher cannot be restored, you need to transfer the Publisher role to SQL Server that holds the Subscriber role, and reconfigure the other Subscribers to use the new Publisher. This requires that you first remove all Subscribers from the replication group.

Given that the Publisher is unavailable, you can remove a Subscriber from the replication group by using the Active Roles console as follows:

  1. Right-click the console tree root, click Connect, and then select the Administration Service that uses the Subscriber SQL Server.
  2. In the console tree, expand Configuration | Server Configuration, and select Configuration Databases.
  3. In the details pane, right-click the Subscriber and select All Tasks | Advanced Properties.
  4. In the Advanced Properties window, select both the Show all possible attributes and Include attributes with empty values check boxes.
  5. In the list of attributes, double-click the attribute edsvaReplicationForceStandalone.
  6. In the Edit Attribute window, type TRUE in the Value box. Click OK.
  7. In the Advanced Properties window, click OK.

Once you have removed all Subscribers from the replication group, you can promote one of the former Subscribers to Publisher and add Subscribers to the new Publisher by using the Active Roles console as follows:

  1. Right-click the console tree root, click Connect, and then select the Administration Service whose SQL Server you want to hold the Publisher role.

    TIP: After you add a Subscriber, the configuration data stored on the Publisher will be replicated to the Subscriber, overriding the data on that Subscriber. Therefore, in order to retain your existing Active Roles configuration, assign the Publisher role to one of the former Subscribers. This ensures that each Administration Service in the new replication group inherits the configuration that was in place when you removed the Subscribers from the replication group.

  1. In the console tree, expand Configuration | Server Configuration, and select Configuration Databases.
  2. In the details pane, right-click the database and click Promote.
  3. In the confirmation message box, click Yes.
  4. Wait while Active Roles performs the operation.
  5. In the details pane, right-click the Publisher, and click Add Replication Partner.
  6. On the Welcome page in the New Replication Partner wizard, click Next.
  7. On the Database Selection page, click Browse.
  8. Use the Connect to Administration Service dialog box to specify the Administration Service whose SQL Server is to be configured as a Subscriber to this Publisher. Click OK.
  9. In the New Replication Partner wizard, click Next, click Next, and then click Finish.
  10. Repeat Steps 6–10 for each SQL Server you want to make a Subscriber.

Troubleshooting

Troubleshooting Replication failures

If there are any replication failures in Active Roles, the Active Roles console provides a visual indication of this issue by placing a red triangle on the Server Configuration and Configuration Databases containers in the console tree. To get more information on a replication failure, you can use SQL Server Management Studio (see Monitoring replication earlier in this document).

The following sections discuss specific actions to take if you encounter a replication problem in Active Roles.

Replication Agent malfunction

Symptoms

Replication stops synchronizing changes to configuration data, that is, changes made on a replication partner are not propagated to other replication partners. Replication Monitor in SQL Server Enterprise Manager or SQL Server Management Studio does not indicate any error.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating