Chat now with support
Chat mit Support

Active Roles 8.2 - Administration Guide

Introduction Getting started with Active Roles Configuring rule-based administrative views Configuring role-based administration Configuring rule-based autoprovisioning and deprovisioning
Configuring Provisioning Policy Objects
User Logon Name Generation E-mail Alias Generation Exchange Mailbox AutoProvisioning Group Membership AutoProvisioning Home Folder AutoProvisioning Property Generation and Validation Script Execution O365 and Azure Tenant Selection AutoProvisioning in SaaS products
Configuring Deprovisioning Policy Objects
User Account Deprovisioning Group Membership Removal User Account Relocation Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Permanent Deletion Office 365 Licenses Retention Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Script Execution Notification Distribution Report Distribution
Configuring entry types Configuring a Container Deletion Prevention policy Configuring picture management rules Managing Policy Objects Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Configuring policy extensions
Using rule-based and role-based tools for granular administration Workflows
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
Azure tenant types and environment types supported by Active Roles Using Active Roles to manage Azure 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 and URLs used by Active Roles Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

Configuring the use of Exchange Web Services

Perform the following steps in the Active Roles Console to configure the default mail settings with the option to use Exchange Web Services:

  1. In the Active Roles Console tree, select Configuration > Server Configuration > Mail Configuration.

  2. In the Details pane, double-click Default Mail Settings.

  3. In the Default Mail Settings Properties dialog, configure the settings on the Mail Setup tab:

    1. From the Settings for list, select Exchange Web Services.

    2. In the Exchange Web Services address box:

      1. For on-premises Exchange mailbox, supply the URL of the Exchange Web Services endpoint. This URL locates the exchange.asmx file on the Exchange server that is running the Client Access server role. For example, https://CAServer.domain.com/EWS/exchange.asmx.

      2. For the Exchange mailbox on the cloud, use https://outlook.office365.com/EWS/Exchange.asmx.

    3. From the Authentication type drop-down, select the authentication method you want to use.

      NOTE: Basic authentication is only available for on-premises Exchange Server services, Exchange Online mail resources should be configured with Modern authentication, as Microsoft does not support Basic authentication in Exchange Online mail resources.

    4. Under Active Roles' mailbox credentials:

      1. For an on-premises Exchange mailbox with Basic authentication, specify the user name and password of the mailbox through which Active Roles will send and receive email.

      2. For a cloud Exchange Online mailbox or an on-premises Exchange mailbox with Modern authentication, specify the Azure user credentials of the Azure mailbox:

        • Tenant ID: The ID of the Azure tenant. To check the ID, on the Azure Portal, navigate to Azure Active Directory > Overview.

        • Client ID: The application client ID. To check the ID, on the Azure Portal, navigate to App registrations > All applications > ActiveRoles.

        • Certificate thumbprint: The most recent certificate thumbprint. To check the thumbprint, on the Azure Portal, navigate to Certificates & secrets > Certificates.

        • Impersonated mailbox: The mailbox that appears to be the sender of the email.

      This mailbox must be created on a server running a supported Exchange Server version, reserved for the exclusive use of Active Roles. For more information on the Microsoft Exchange Server versions supported by Active Roles, see System requirements in the Active Roles Release Notes.

    5. Verify the settings you have configured. Click Verify Settings, supply a valid email address, and then click Send.

    This causes Active Roles to send a diagnostic email message to the address you supplied. The message is attempted to be delivered from Active Roles’ mailbox by using Exchange Web Services. You can check the mailbox with the address you supplied to see if the diagnostic message has been received.

  4. Verify that the Send approval response by email option is selected on the Mail Setup tab.

  5. Select Approve or reject via Web Interface to manage emails through the Web Interface.

  6. When finished, click OK to close the Default Mail Settings Properties dialog.

Automation workflow

An Active Roles "Workflow" is a sequence of actions that leads to the completion of a certain task. The sequence is carried out according to a set of rules or policies. A workflow can be configured to start upon a change request that satisfies the start conditions of the workflow. An example is a workflow that coordinates the process of approving certain changes to directory data such as creation of new users or population of security groups. In Active Roles, this kind of workflow is referred to as a change workflow.

A workflow can also perform routine administrative tasks either on a scheduled basis or on user demand. In these cases, the workflow is not attached to any change request. With Active Roles, you can configure a workflow to perform certain actions at a specific time. You can also allow users to run a workflow at any time on demand. This workflow category is referred to as an automation workflow.

Automation workflows can automate the completion of complex administrative tasks to help you manage large task volumes. It also allows you to build checks or restrictions in directory administration processes to ensure consistency and compliance with your company policies and legal requirements. By using automation workflow, you can ensure that directory administration tasks are performed in a consistent and efficient manner.

Automation workflow options and start conditions

The start conditions of an automation workflow determine the trigger that causes the workflow to start. You can use a time-based trigger or an event-based trigger to start an automation workflow. It is also possible to allow an automation workflow to be started on user demand.

With a time-based trigger, you can configure an automation workflow to start at a specific time of a day or you can schedule an automation workflow to start multiple times on a daily, weekly, or monthly basis. An event-based trigger allows you to start an automation workflow upon startup of the Active Roles Administration Service. Each automation workflow can have only one trigger.

To enable a time-based trigger, an automation workflow must be configured with the option to run the workflow on a schedule. This option is available on the Workflow Options and Start Conditions page in the Workflow Designer of the Active Roles Console.

Run the workflow on a schedule

If you select the Run the workflow on a schedule option, then you can choose from the following options to run the workflow:

  • One time: Lets you choose the date and time to run the workflow.

  • Hourly: Lets you choose the date and time to run the workflow for the first time, and the recurrence interval (in hours and minutes) for the workflow. Thus, an interval of one hour causes the workflow to run every hour and an interval of two hours causes the workflow to run every other hour.

  • Daily: Lets you choose the date to run the workflow for the first time, the time of the day to run the workflow, and the recurrence interval (in days) for the workflow. Thus, an interval of one causes the workflow to run every day and an interval of two causes the workflow to run every other day. The workflow will start at the specified time each day.

  • Weekly: Lets you choose the date to run the workflow for the first time, the time of the day to run the workflow, the days of the week on which to run the workflow, and the recurrence interval (in weeks) for the workflow. Thus, an interval of one causes the workflow to run every week and an interval of two causes the workflow to run every other week. The workflow will start at the specified time on each of the specified days.

  • Monthly: Lets you choose the date to run the workflow for the first time, the time of the day to run the workflow, the months in which to run the workflow, and the day of the month on which to run the workflow. You can choose either the number of the day, or the first, second, third, fourth, or last occurrence of a certain day of the week day during the month. The desired day of the week can be selected from a list.

  • When the Administration Service starts: Causes the workflow to start immediately after the Active Roles Administration Service has started up. This option applies to the Administration Service identified by the Run the workflow on setting.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen