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

Active Roles 7.5 - 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 One Identity Starling Two-factor Authentication for Active Roles Managing One Identity Starling Connect 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 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 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 Federated Authentication Appendix F: Active Roles integration with other One Identity and Quest products Appendix G: Active Roles integration with Duo MFA Appendix H: Active Roles integration with Okta MFA

Troubleshooting

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 (see Monitoring replication earlier in this document).

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

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 command is unavailable, the SQL Server Agent service is already started.

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 schedule is correct. The Merge Agents must be configured to run continuously at the Publisher. The Snapshot Agent must be configured to start daily at 12:00 a.m. at the Publisher. For details, see Replication Agent schedule earlier in this document.

Replication Agent authentication problems

Symptoms

Replication fails with one of the following errors on the Snapshot Agent or Merge Agent (see Monitoring replication earlier in this document):

  • 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>’.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation