Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Always On Availability Groups

To improve the availability of the Active Roles Administration Service, you can use Always On Availability Groups introduced in Microsoft SQL Server 2012. With Always On Availability Groups, 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: a primary 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 ensures the 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 more information about Always On Availability Groups, see AlwaysOn Availability Groups (SQL Server) in the Microsoft SQL documentation.

Configuring AlwaysOn Availability Groups in Active Roles

If you have the Active Roles Administration Service installed, you can configure it to use a database belonging to an Always On availability group (also called an availability database). When configuring Active Roles, you must store the Management History data and Configuration data in separate databases. Each of the two databases (or both) can belong to an availability group.

NOTE: Active Roles does not support the replication of availability databases. Therefore, if the Administration Service is configured to use an availability database (either for the Management History Database or for the Configuration Database), then the data of that database cannot be replicated.

For more information on how to install and configure the Administration Service, see the Active Roles Quick Start Guide.

By using the availability group listener, the Administration Service can connect to the current primary replica of the availability group that holds the Active Roles database without knowing the name of the physical instance of the SQL Server that hosts the primary replica. The listener also enables support for failover redirection. This means that in case of a failover, the listener automatically redirects the Administration Service connection to the new primary replica.

Prerequisites

  • The Active Roles database is added to an Always On availability group on the SQL Server.

    For instructions on how to configure an availability group, and how to add a database to an availability group, see Getting Started with Always On Availability Groups (SQL Server) in the Microsoft SQL documentation.

  • Active Roles replication is not configured for the Configuration data and the Management History data.

To configure the Active Roles Administration Service to connect to the database via the availability group listener

  1. Start the Active Roles Configuration Center on the computer running the Administration Service, or connect the Active Roles Configuration Center to that computer.

  2. On the Active Roles Configuration Center Dashboard, in Administration Service, click Manage Settings.

    The Connection to Database page opens.

  3. To modify the database connection of the Administration Service, in Connection to Database > Active Roles databases, click Change.

  4. If either or both of the databases belong to an availability group in your Active Roles environment, specify the availability group listener. Otherwise, do not change the value of SQL Server.

    1. If the Configuration database belongs to an availability group, enter the DNS host name and, optionally, the TCP port of the listener of that availability group in Connection to Database > SQL Server.

    2. If the Management History database belongs to an availability group, enter the DNS host name and, optionally, the TCP port of the listener of that availability group in Connection to Management History Database > SQL Server.

    The value of SQL Server must be identical to the DNS host name and, optionally, the TCP port of the listener of the availability group to which the database belongs.

    Example: Specifying the availability group listener in the SQL Server

    If the DNS host name of the listener is AGListener and the TCP port used by this listener is 1234, the value is AGListener,1234. You can omit the port number in case of the default port, 1433.

  5. Click Next.

  6. To complete the configuration, follow the instructions of the wizard.

Using database mirroring

Active Roles can use the Microsoft SQL Server database mirroring technology to improve the availability of the Administration Service. Database mirroring provides a standby database server that supports failover. Once the current database server fails, the Administration Service can recover quickly by automatically reconnecting to the standby server.

Database mirroring increases database availability by supporting rapid failover. This technology can be used to maintain two copies of a single Active Roles database on different server instances of SQL Server Database Engine. One server instance serves the database to the Administration Service; this instance is referred to as the Principal server. The other instance acts as a standby server; this instance is referred to as the Mirror server.

Role switching

Within the context of database mirroring, the mirror server acts as the failover partner for the principal server. In the event of a disaster, the mirror server takes over the role of the principal server, bringing the mirror copy of the database online as the new principal database. The former principal server, if available, then assumes the role of the mirror server. This process, known as role switching, can take the form of:

  • Automatic failover: If the principal server becomes unavailable, quickly brings the mirror copy of the database online as the new principal database.

  • Manual failover: Allows the database owner to reverse the roles of the failover partners, if necessary.

  • Forced service: If the principal server becomes unavailable, allows the database owner to restore access to the database by forcing the mirror server to take over the role of the principal server.

In any role switching scenario, as soon as the new principal database comes online, the Administration Service can recover by automatically reconnecting to the database.

For more information about the database mirroring technology, and instructions on how to set up and administer database mirroring on SQL Server, see the Database Mirroring in the SQL Server product documentation.

NOTE: The Active Roles replication function is not supported for the databases that have mirroring set up. If you attempt to perform the Promote to Publisher or Add Subscriber operation on such a database, you receive an error.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation