サポートと今すぐチャット
サポートとのチャット

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

Delegating full control of automation workflows

By giving full control of an automation workflow to a user or group, you authorize the user or group to perform the following tasks:

  • View the workflow definition.

  • Make changes to the workflow.

  • Run the workflow.

  • View the workflow run history reports.

You can delegate full control of all automation workflows held in a certain container by applying the Automation Workflow - Full Control Access Template to that container.

To delegate full control of all automation workflows held in a certain container

  1. In the Active Roles Console tree, right-click the desired container under Configuration > Policies > Workflow, and then click Delegate Control.

  2. In the Active Roles Security dialog, click Add to start the Delegation of Control Wizard.

  3. On the Users or Groups page in the wizard, click Add, and then use the Select Objects dialog to select the desired users or groups.

  4. On the Access Templates page in the wizard, under Access Templates > Configuration, select the Automation Workflow - Full Control check box.

  5. Follow the instructions in the wizard and accept the default settings.

  6. Click OK in the Active Roles Security dialog.

It is also possible to delegate full control of a single automation workflow by applying the Access Template to the workflow definition object.

To delegate full control of a single automation workflow

  1. On the View menu, select Advanced Details Pane.

  2. In the Active Roles Console tree, under Configuration > Policies > Workflow, select the container that holds the desired workflow definition object.

  3. In the upper part of the Details pane, select the workflow definition object.

  4. In the lower part of the Details pane, on the Active Roles Security tab, right-click a blank area and click Add to start the Delegation of Control Wizard.

  5. On the Users or Groups page in the wizard, click Add, and then use the Select Objects dialog to select the desired users or groups.

  6. On the Access Templates page in the wizard, under Access Templates > Configuration, select the Automation Workflow - Full Control check box.

  7. Follow the instructions in the wizard and accept the default settings.

Delegating the task of running automation workflows

You can authorize users or groups to run all automation workflows held in a certain container by applying the Automation Workflow - View and Run Access Template to that container. This allows the users or groups to run the automation workflow without giving them the right to make any changes to the workflow.

To delegate the task of running all automation workflows held in a certain container

  1. In the Active Roles Console tree, right-click the desired Workflow container under Configuration > Policies > Workflow, then click Delegate Control.

  2. In the Active Roles Security dialog, click Add to start the Delegation of Control Wizard.

  3. On the Users or Groups page in the wizard, click Add, and then use the Select Objects dialog to select the desired users or groups.

  4. On the Access Templates page in the wizard, under Access Templates > Configuration, select the Automation Workflow - View and Run check box.

  5. Follow the instructions in the wizard and accept the default settings.

  6. Click OK in the Active Roles Security dialog.

It is also possible to authorize users or groups to run a single automation workflow by applying the Access Template to the workflow definition object.

To delegate the task of running a single automation workflow

  1. On the View menu, select Advanced Details Pane.

  2. In the Active Roles Console tree, under Configuration > Policies > Workflow, select the container that holds the desired workflow definition object.

  3. In the upper part of the details pane, select the workflow definition object.

  4. In the lower part of the details pane, on the Active Roles Security tab, right-click a blank area and click Add to start the Delegation of Control Wizard.

  5. On the Users or Groups page in the wizard, click Add, and then use the Select Objects dialog to select the desired users or groups.

  6. On the Access Templates page in the wizard, under Access Templates > Configuration, select the Automation Workflow - View and Run check box.

  7. Follow the instructions in the wizard and accept the default settings.

Delegating the task of viewing the run history of automation workflows

You can authorize users or groups to view the run history of all automation workflows held in a certain container by applying the Automation Workflow - View Access Template to that container. This enables the users or groups to view run history of the automation workflow without giving them the right to modify or run the workflow.

To delegate the task of viewing run history of all automation workflows held in a certain container

  1. In the Active Roles Console tree, right-click the desired container under Configuration > Policies > Workflow, and then click Delegate Control.

  2. In the Active Roles Security dialog, click Add to start the Delegation of Control Wizard.

  3. On the Users or Groups page in the wizard, click Add, and then use the Select Objects dialog to select the desired users or groups.

  4. On the Access Templates page in the wizard, under Access Templates > Configuration, select the Automation Workflow - View check box.

  5. Follow the instructions in the wizard and accept the default settings.

  6. Click OK in the Active Roles Security dialog.

It is also possible to authorize users or groups to view run history of a single automation workflow by applying the Access Template to the workflow definition object.

To delegate the task of viewing run history of a single automation workflow

  1. On the View menu, select Advanced Details Pane.

  2. In the Active Roles Console tree, under Configuration > Policies > Workflow, select the container that holds the desired workflow definition object.

  3. In the upper part of the details pane, select the workflow definition object.

  4. In the lower part of the details pane, on the Active Roles Security tab, right-click a blank area and click Add to start the Delegation of Control Wizard.

  5. On the Users or Groups page in the wizard, click Add, and then use the Select Objects dialog to select the desired users or groups.

  6. On the Access Templates page in the wizard, under Access Templates > Configuration, select the Automation Workflow - View check box.

  7. Follow the instructions in the wizard and accept the default settings.

Sample Azure Hybrid Migration

To create a remote mailbox for an existing user, you can convert the on-premises user to a hybrid Azure user with an Office 365 automation workflow and a hybrid migration script, based on the built-in Sample Azure Hybrid Migration script.

The Sample Azure Hybrid Migration script is available at the following location in the Active Roles Console:

Configuration > Script Modules > Builtin > Sample Azure Hybrid Migration

The remote mailbox workflow, on the other hand, is available at the following location in the Active Roles Console:

Configuration > Policies > Workflow > Builtin > Sample Azure Hybrid Migration

Prerequisites

To create remote mailboxes via hybrid migration with the Sample Azure Hybrid Migration script, your organization must meet the following requirements:

  • To enable remote mailboxes, the Exchange management tools of an on-premises Microsoft Exchange installation must be available. For more information on the Microsoft Exchange Server versions supported by Active Roles, see System requirements in the Active Roles Release Notes.

  • The Active Roles service account must be a part of the Recipient Management management role group to run Exchange hybrid commands.

To configure and run the Sample Azure Hybrid Migration script

  1. Depending on whether you want to enable or disable remote mailboxes, use one of the following functions:

    • EnableRemoteMailBox: Use this function to enable remote mailboxes for the users in the workflow scope. Select EnterExchangeCreds_params as the function to declare parameters in the script, then provide the Exchange user name and password to run the EnableRemoteMailBox function in workflow.

    • DisableRemoteMailBox: Use this function to disable remote mailboxes for the users in the workflow scope. Select EnterExchangeCreds_params as the function to declare parameters in the script, then provide the Exchange user name, password and Exchange recipient type details to run the DisableRemoteMailBox function in workflow.

  2. Make sure to specify the Fully Qualified Domain Name (FQDN) of the Exchange Server in the script, and that you modify the required code blocks. For more information on declaring script parameters, see Script activity.

  3. After the script is modified, enable or copy the default Sample Azure Hybrid Migration workflow and run it.

By default, a remote mailbox is created for users with a valid Exchange Online license and who have no on-premises Exchange mailbox. For more information on creating a remote mailbox for new users, see Creating a new hybrid Azure user with the Active Roles Web Interface in the Active Roles Web Interface User Guide.

NOTE: One Identity provides the Remote mailbox migration (RemoteMailbox.ps1) script as a sample script to illustrate the required steps of creating remote mailboxes.

Do not use the script in a production environment without the required modifications and enhancements. Using security credentials within a script in clear text is never secure. When testing the script, consider the appropriate authentication and use of credentials. After testing, do not leave any credentials in clear text in the script.

For more information, see Knowledge Base Article 310525.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択