Chat now with support
Chat mit Support

Active Roles 7.6.1 - 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 Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users 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 distribution 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 cloud-only shared 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: Active Roles integration with other One Identity and Quest products Appendix F: Active Roles integration with Duo Appendix G: Active Roles integration with Okta

Modifying Replication Agent credentials

This section provides information on how to repair Active Roles replication if it fails due to insufficient permissions of Replication Agents. The credentials used by Replication Agents to access a given SQL Server depend on authentication mode of the Administration Service connection to that SQL Server:

  • Windows authentication In this mode, Replication Agents use the credentials of the SQL Server Agent service running on the Publisher SQL Server computer
  • SQL Server authentication In this mode, Replication Agents use the credentials of the SQL Server login specified for the Administration Service connection to SQL Server

The following sub-sections elaborate on each of these two options.

Windows authentication

If the Administration Service uses Windows authentication, Replication Agents connect to SQL Server in the security context of the SQL Server Agent service. Therefore, the SQL Server Agent logon account must have sufficient permissions for replication to work properly (see the “SQL Server permissions” section in the Active Roles Quick Start Guide.

If the SQL Server Agent logon account does not have the appropriate permissions, is deleted, or has the password changed, Active Roles replication fails. To resolve this problem, give the required permissions to the logon account, or configure the SQL Server Agent service to log on with a different account that has the appropriate permissions. For instructions on how to configure the SQL Server Agent service to log on with a given account, see Changing the SQL Server Agent logon account earlier in this document.

You can use the following instructions to verify that the Replication Agents are configured properly. The instructions vary depending on whether the SQL Server holds the Publisher or Subscriber role. In both cases, you should connect to the Publisher SQL Server using SQL Server Management Studio.

Replication Agent connection to Publisher

If the Administration Service connects to the Publisher SQL Server using Windows authentication, follow these steps to verify that the Replication Agents are configured properly:

  1. With SQL Server Management Studio, connect to the Publisher SQL Server.
  2. In the Object Browser, under the Publisher SQL Server, right-click the Replication folder, and then click Distributor Properties.
  3. In the left pane of the Distributor Properties window, click Publishers.
  4. In the Publishers list, select the entry representing the Publisher SQL Server, and click the button in that entry to display the Publisher Properties dialog box.
  5. In the Publisher Properties dialog box, under Agent Connection to the Publisher, verify that the Agent Connection Mode property is set to Impersonate the agent process account.

Replication Agent connection to Subscriber

If the Administration Service connects to the Subscriber SQL Server using Windows authentication, follow these steps to verify that the Replication Agents are configured properly:

  1. With SQL Server Management Studio, connect to the Publisher SQL Server.

    NOTE: You must have Management Studio connected to the Publisher SQL Server, regardless of whether you are managing Replication Agents for the Publisher or for a Subscriber.

  1. In the Object Browser, under the Publisher SQL Server, expand Replication | Local Publications | AelitaReplica.
  2. In the list under AelitaReplica, right-click the entry corresponding to the Subscriber SQL Server and click Properties.
  3. In the Subscription Properties window, in the Security section, expand the Subscriber connection entry.
  4. Verify that the Subscriber connection property is set to Impersonate agent process account (Windows Authentication).

SQL Server authentication

If the Administration Service uses SQL Server authentication, the Replication Agents connect to SQL Server in the security context of the SQL Server login specified for the Administration Server connection to SQL Server.

If the login does not have sufficient rights, is deleted, or has the password changed, Active Roles replication fails. To resolve this problem, do the following:

  1. Choose a SQL Server login with sufficient rights (see the “SQL Server permissions” section in the Active Roles Quick Start Guide).
  2. Configure the Administration Service to use that login (see Viewing database connection settings earlier in this document).
  3. Configure the Replication Agents to use that login.

The following sections elaborate on how to configure the Replication Agents to use a given SQL Server login. The instructions vary depending on whether SQL Server in question is the Publisher or a Subscriber.

Replication Agent connection to Publisher

If you have changed the SQL Server login for the Administration Service connection to the Publisher, use the following steps to configure the Replication Agents with that login:

  1. With SQL Server Management Studio, connect to the Publisher SQL Server.
  2. In the Object Browser, under the Publisher SQL Server, right-click the Replication folder, and then click Distributor Properties.
  3. In the left pane of the Distributor Properties window, click Publishers.
  4. In the Publishers list, select the entry representing the Publisher SQL Server, and click the button in that entry to display the Publisher Properties dialog box.
  5. In the Agent Connection to the Publisher area, click Login, and type the login name.
  6. Click Password, and then click the button in the Password entry.
  7. In the Enter Password dialog box, type and confirm by retyping the password of that login.
  8. Click OK to close the Enter Password dialog box.
  9. Click OK to close the Publisher Properties dialog box.

Replication Agent connection to Subscriber

If you have changed the SQL Server login for the Administration Service connection to a Subscriber, use the following steps to configure the Replication Agents with that login:

  1. With SQL Server Management Studio, connect to the Publisher SQL Server.

    NOTE: You must have Management Studio connected to the Publisher SQL Server, regardless of whether you are managing Replication Agents for the Publisher or for a Subscriber.

  2. In the Object Browser, under the Publisher SQL Server, expand Replication | Local Publications | AelitaReplica.
  3. In the list under AelitaReplica, right-click the entry corresponding to the Subscriber SQL Server and click Properties.
  4. In the Subscription Properties window, in the Security section, expand the Subscriber connection entry.
  5. Click the button in the Subscriber Connection entry.

This displays the Enter Connection Information dialog box.

  1. In the Login box, type the login name.
  2. In the Password and Confirm password boxes, type and confirm by retyping the password of that login.
  3. Click OK to close the Enter Connection Information dialog box.
  4. Click OK to close the Subscription Properties dialog box.

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.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen