지금 지원 담당자와 채팅
지원 담당자와 채팅

Active Roles 7.4.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 License Management Office 365 Roles Management 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_Overview
Config ARS to Manage Hybrid AD Objects Managing Hybrid AD Users Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Azure O365 or Unified Groups
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 delegation for Federated Authentication

Removing members from a replication group

You can remove Subscribers from a replication group by using the Active Roles console:

  1. Connect to the Publisher Administration Service.
  2. Select a Subscriber from the Configuration Databases container, right-click the Subscriber, and click Delete.

If Active Roles does not have sufficient rights to perform the operation on SQL Server, then the Active Roles console prompts you to supply an alternative account for that operation (see “Permissions for adding or removing a Subscriber” in the Active Roles Quick Start Guide).

Using this method, you can remove only Subscribers. The Publisher cannot be removed from its replication group when the group includes Subscribers.

To remove the Publisher, you must first remove all Subscribers, and then demote the Publisher. This action deletes the entire replication group.

After you remove all Subscribers, you can demote the Publisher: in the Configuration Databases container, right-click the Publisher and click Demote.

If Active Roles does not have sufficient rights to perform the Demote operation on SQL Server, then the Active Roles console prompts you to supply an alternative account for that operation (see “Permissions for creating or removing the Publisher” in the Active Roles Quick Start Guide).

Steps for removing members from a replication group

To remove Subscribers from a replication group

  1. Connect to the Publisher Administration Service.
  2. In the console tree, expand Configuration | Server Configuration, and click Configuration Databases.
  3. In the details pane, right-click the Subscriber, and then click Delete.

To remove the Publisher from a replication group

  1. Connect to the Publisher Administration Service.
  2. In the console tree, expand Configuration | Server Configuration, and click Configuration Databases.
  3. In the details pane, right-click the Publisher, and then click Demote.

NOTE:

  • For information on how to connect to an Administration Service, see Connecting to the Administration Service earlier in this chapter.
  • The Publisher cannot be removed from its replication group when the group includes Subscribers. To remove the Publisher, you must first remove all Subscribers, and then demote the Publisher. This action deletes the replication group. After you remove all Subscribers, you can demote the Publisher.
  • The Demote command is not displayed unless the Publisher is the only member of the replication group.
  • If Active Roles does not have sufficient rights to perform the operation on SQL Server, then the Active Roles console prompts you to supply an alternative account for that operation (see “Replication configuration permissions” in the Active Roles Quick Start Guide).

Monitoring replication

Active Roles makes it possible to monitor the status of replication partners. Monitoring allows you to determine whether Active Roles replication is working efficiently and correctly. You can view the status of a replication partner via the Active Roles console:

  1. Connect to any Administration Service within the replication group.
  2. Open the Properties dialog box for the replication partner and go to the Replication Status tab.

To connect to the Administration Service, use the instructions provided earlier in this chapter (see Connecting to the Administration Service).

Once connected to the Administration Service, perform the following steps to open the Properties dialog box for a replication partner:

  1. In the console tree, expand Configuration | Server Configuration, and select Configuration Databases.
  2. In the details pane, right-click the replication partner, and click Properties.

The Replication Status tab in the Properties dialog box provides information about the last replication action of the partner and indicates whether the action completed successfully, failed, or is in progress.

If there are any replication failures in Active Roles, the Active Roles console provides a visual indication of this issue by modifying the icon of the Server Configuration and Configuration Databases containers in the console tree. This allows you to detect a replication failure without examining individual databases.

For more information on how to monitor the health of Active Roles replication, refer to the Active Roles Replication: Best Practices and Troubleshooting document.

Using AlwaysOn Availability Groups

You can improve the availability of the Active Roles Administration Service by using the AlwaysOn Availability Groups feature introduced in Microsoft SQL Server 2012. With the AlwaysOn Availability Groups feature, SQL Server provides a failover environment, known as an availability group, for a set of availability databases that fail over together from one SQL Server instance to another. You can add the Active Roles database to an availability group, and have the Administration Service automatically reconnect to the database when the availability group fails over to another SQL Server instance.

An availability group defines a set of availability replicas to host copies of each availability database. Each availability group has at least two availability replicas: the primary replica and a secondary replica. The primary replica hosts the read-write copy of each availability database held in the availability group; a secondary replica hosts a read-only copy of each availability database, and serves as a potential failover target for the availability group. During a failover, a secondary replica transitions to the primary role, becoming the new primary replica. The new primary replica brings its databases online as the primary databases for read-write access.

Adding the Active Roles database to an availability group helps ensure uninterrupted operation of the Active Roles Administration Service. If a server or software failure occurs on the SQL Server side, the availability group can instantly switch the database to a secondary replica, enabling the Administration Service to reconnect seamlessly to the database in the new location.

For detailed information about the AlwaysOn Availability Groups feature, see “AlwaysOn Availability Groups (SQL Server)” at http://go.microsoft.com/fwlink/p/?LinkId=245660.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택