Chatta subito con l'assistenza
Chat con il supporto

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

Promoting an SQL Server to Publisher

After demoting the previous Publisher, 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 using the Active Roles Console

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

  2. In the Console tree, expand Configuration > Server Configuration, and select Configuration Databases.

  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. To configure the SQL Server of an Administration Service as a Subscriber to this Publisher, specify the corresponding Administration Service in the Connect to Administration Service dialog. Click OK.

  10. In the New Replication Partner wizard, click Next, click Next, and then click Finish.

  11. Repeat the steps for adding a replication partner for each SQL Server you want to make a Subscriber.

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. For more information, see Monitoring replication.

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.

Solution

To verify that the SQL Server Agent service is started on the Publisher SQL Server

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

  2. In the Console tree, right-click SQL Server Agent, and then click Start.

    If the Start button is disabled, it means that the SQL Server Agent service is already started.

To ensure that the Merge Agents are started on the Publisher SQL Server

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

  2. In the Console tree, right-click Replication, and click Launch Replication Monitor.

  3. In Replication Monitor, in the left pane, browse the My Publishers branch to select the AelitaReplica publication.

  4. In Replication Monitor, in the right pane, right-click a subscription and click Start Synchronizing. Perform this step for each subscription of the AelitaReplica publication.

    If the Start Synchronizing command is unavailable, the agent is already started.

Verify that the Replication Agent is scheduled correctly at the Publisher. The Merge Agents must be configured to run continuously. The Snapshot Agent must be configured to start daily at 00:00. For more information, see Replication Agent schedule.

Replication Agent authentication problems

The following section describes the symptoms and solutions for Replication Agent authentication problems.

Symptoms

Replication fails with one of the following errors on the Snapshot Agent or Merge Agent (for more information, see Identifying replication-related problems):

  • The process could not connect to Publisher ‘<Server_name>’. Login failed for user ‘<User_name>’.

  • The process could not connect to Subscriber ‘<Server_name>’. Login failed for user ‘<User_name>’.

Solution

By using SQL Server Enterprise Manager or SQL Server Management Studio, verify that the Replication Agent credentials are set properly. The following conditions must be met:

Table 120: Conditions for Replication Agent credentials

Server role

Authentication mode

Replication Agent credentials

Publisher

Windows Authentication

Impersonate the SQL Server Agent account on the computer running the Publisher SQL Server (trusted connection). For more information on impersonating the SQL Server Agent account, see .

SQL Server Authentication

SQL Server login and password that the Publisher Administration Service uses to connect to its SQL Server

Subscriber

Windows Authentication

Impersonate the SQL Server Agent account on the computer running the Publisher SQL Server (trusted connection). For more information on impersonating the SQL Server Agent account, see Adding members to a replication group.

SQL Server Authentication

SQL Server login and password that the Subscriber Administration Service uses to connect to its SQL Server

For more information on how to view or modify the credentials that the Snapshot Agent and Merge Agents use to connect to the Publisher and Subscribers, see Modifying Replication Agent credentials.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione