Converse agora com nosso suporte
Chat com o suporte

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

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 that are 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 that is running on the PublisherSQL Server computer.

  • SQL Server authentication: In this mode, Replication Agents use the credentials of the SQL Server login that is specified for the Administration Service connection to SQL Server.

The following sections describe 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. For more information, 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.

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, 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.

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 in that entry to display the Publisher Properties dialog.

  5. In the Publisher Properties dialog, 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:

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.

  2. In the Object Browser, under the Publisher SQL Server, expand Replication > Local Publications > AelitaReplica.

  3. In the list under AelitaReplica, right-click the Subscriber SQL Server and click Properties.

  4. In the Subscription Properties window, in the Security section, expand the Subscriber connection entry.

  5. 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 toSQL Server in the security context of the SQL Server login that is specified for the Administration Service connection to SQL Server.

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

To avoid replication fail

  1. Choose an SQL Server login with sufficient rights. For more information, see the “SQL Server permissions” section in the Active Roles Quick Start Guide.

  2. Configure the Administration Service to use that login. For more information, see Viewing database connection settings.

  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:

To configure the Replication Agent to connect to the Publisher

  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 in that entry to display the Publisher Properties dialog.

  5. In the Agent Connection to the Publisher area, click Login, and type the login name.

  6. Click Password, and then click in the Password entry.

  7. In the Enter Password dialog, type and confirm by retyping the password of that login.

  8. To close the Enter Password dialog, click OK.

  9. To close the Publisher Properties dialog, click OK.

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:

To configure the Replication Agent to connect to the Subscriber

  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 in the Subscriber Connection entry.

    This displays the Enter Connection Information dialog.

  6. In the Login box, type the login name.

  7. In the Password and Confirm password boxes, type and confirm by retyping the password of that login.

  8. To close the Enter Connection Information dialog, click OK.

  9. To close the Subscription Properties dialog, click OK.

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 might 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. Because 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. The increased volume of requests 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 which has a database server currently holding the Publisher role (Publisher Administration Service).

NOTE: The Publisher Administration Service must be up and running. If the Publisher is unavailable, you can assign the Publisher role to a different SQL Server. For more information, see Promoting an SQL Server to Publisher.

To connect to the Publisher Administration Service via the Active Roles Console

  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.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação