立即与支持人员聊天
与支持团队交流

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 control to users for accessing Active Roles Console

By default, on installing Active Roles, all users are allowed to log in to the Active Roles Console. To manage the Console access for a user, you must configure the options using Configuration Center > MMC Interface Access > Manage settings. Selecting this option restricts all non-Active Roles Administrators from using the Console. All delegated users are affected, however, it does not apply to Active Roles Administrators.

To be able to log in to the Active Roles Console, the user must be delegated with the User Interfaces access rights on the User Interfaces container under Server Configuration. User Interfaces Access Templates that provide the access rights are available as part of the Active Roles built-in Access Templates in the User Interfaces container.

To delegate the control to users in the User Interfaces container you must apply the User Interface Access Template

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

  2. Under Server Configuration, locate the User Interfaces container, right-click it, and click Delegate Control.

  3. On the Users or Groups page, click Add, and then select the users or groups to which you want to delegate the control. Click Next.

  4. On the Access Templates page, expand the Active Directory > User Interfaces folder, and select the check box next to User Interface Management-MMC Full control.

  5. Click Next and follow the instructions in the wizard, accepting the default settings.

  6. After you complete these steps, the users and groups you selected in Step 3 are authorized to log in to the Active Roles Console.

  7. Click OK to close the Active Roles Security dialog.

Managed domains

Active Directory domains registered with Active Roles are referred to as managed domains. Each Administration Service maintains a list of managed domains, and stores this list in the Administration Database as part of the service configuration.

In the Active Roles Console, the Add Managed Domain wizard is used to register domains for management. You can access the wizard as follows:

  1. Click the Console tree root.

  2. In the details pane, in the Domains area, click Add Domain.

The Add Managed Domain wizard prompts you for the following information:

  • The name of the domain you want to register.

  • The credentials that Active Roles will use to access the domain.

You have the option to use the default credentials (the service account of the Administration Service) or enter the user name and password of a different account (override account). In both cases, the account must have adequate rights in the managed domain. For more information, refer to the Access to Managed Domains section in the Active Roles Quick Start Guide.

NOTE: This option applies to all Administration Service in your environment. Each Administration Service in your environment will use its own service account to access the domain. Since different service accounts may have different levels of access to the domain, Active Roles may have different access rights to the domain, depending on which Administration Service is being used to manage the domain. The result is that the behavior of Active Roles may vary when you switch to a different Administration Service.

After you add a managed domain, the Administration Service retrieves the domain information, such as the Active Directory schema and the hierarchy of containers. This process is referred to as loading domain information.

It may take a few minutes for the Administration Service to load the domain information. Once this process is completed, the domain is available for management. Select the Active Directory item in the Console tree and press F5 to refresh the details pane and display the new domain. To start managing the domain, select it in the details pane and press Enter; or expand the domain item in the Console tree.

It is possible to remove a domain from the list of managed domains. Once removed, the domain and all directory objects contained in the domain can no longer be managed with Active Roles. To remove a managed domain, select the Console tree root and click Go to Managed Domains in the details pane, in the Domains area. This causes the details pane to display a list of managed domains. In the list, right-click the domain you want to remove, and click Delete.

Adding or removing a managed domain

The operation of adding a managed domain results in the creation of an object that holds the registration information about the domain. For this reason, it is also referred to as registering a domain with Active Roles.

To add a managed domain

  1. In the Console tree, expand Configuration > Server Configuration.

  2. Under Server Configuration, right-click Managed Domains, and select New > Managed Domain to start the Add Managed Domain wizard.

  3. On the Welcome page of the wizard, click Next.

  4. On the Domain Selection page, do one of the following, and then click Next.

    • Type the name of the domain you want to add.

    • Click Browse, and select the domain from the list.

  5. On the Active Roles Credentials page, click one of these options that determine the logon information that Active Roles will use to access the domain:

    • The service account information the Administration Service uses to log in.

    • The Windows user account information specified below.

    If you choose the second option, type the user name and password of the user account you want Active Roles to use when accessing the domain.

  6. Click Next, then click Finish.

To remove a managed domain

  1. In the Console tree, expand Configuration > Server Configuration.

  2. Under Server Configuration, click Managed Domains.

  3. In the details pane, right-click the domain you want to remove, then click Delete.

NOTE: Consider the following when managing managed domains:

  • You can use the Properties command on an object held in the Managed Domains container to view or modify the registration information for the respective managed domain. For example, it is possible to change the logon information that is used to access the domain:

    1. On the General tab in the Properties dialog, choose the appropriate option.

    2. Click Apply.

    You can choose one of the two options that are listed in Step 5 of the procedure above.

  • The Managed Domains container holds the registration objects for all domains that are registered with Active Roles. You can un-register domains by deleting objects from that container.

  • By default, no domains are registered with Active Roles. When you register a domain, the domain registration is saved as part of the Active Roles configuration.

Using unmanaged domains

After you’ve registered an Active Directory domain with Active Roles, you have the option to use the domain as an unmanaged domain. An unmanaged domain is a domain that is registered with Active Roles for read-only access. The use of the unmanaged domain option allows you to reduce licensing costs since the user count that corresponds to the unmanaged domains is not added to product usage statistics. For more information, see Evaluating product usage.

Unmanaged domains are instrumental in the following scenarios:

  • Group membership management: When used to add members to a group, by selecting the new members from a list of objects, Active Roles requires the domain that holds the objects to be registered. If you only use Active Roles for selecting member objects when managing group membership, you can configure the domain that holds the member objects as an unmanaged domain.

  • Exchange resource forest: When used to create Exchange mailboxes in a forest that is different from the forest that holds the accounts of the mailbox users, Active Roles requires the domain of the mailbox users (account domain) to be registered. If you do not use Active Roles for user management in the account domain, you can make that domain an unmanaged domain.

As applied to a registered unmanaged domain, the features and functions of Active Roles are limited to those that do not require write access to the objects held in that domain (including write access to the object data that is stored by Active Roles as virtual attributes). Thus, you can use Active Roles to:

  • Search for, list and select objects from unmanaged domains.

  • Populate groups in regular managed domains with objects from unmanaged domains.

  • Retrieve and view properties of objects held in unmanaged domains.

  • Assign users or groups from unmanaged domains to the role of manager, primary owner, or secondary owner for objects held in regular managed domains.

  • Delegate management tasks and approval tasks to users or groups held in unmanaged domains.

  • Run Active Roles policies against objects held in unmanaged domains, provided that the policies require only read access to those objects.

  • Provision users from unmanaged domains with linked Exchange mailboxes held in a separate managed forest.

  • Populate Managed Units with objects from unmanaged domains.

Since Active Roles has read-only access to unmanaged domains, it cannot:

  • Create, move, or delete objects in unmanaged domains.

  • Change any properties of objects held in unmanaged domains.

  • Run any group membership related policies against the groups in unmanaged domains, including the Group Family and Dynamic Group policies.

  • Run any auto-provisioning or deprovisioning policies against the users or groups held in unmanaged domains.

  • Run any workflow that makes changes to objects in unmanaged domains.

  • Restore objects from Active Directory Recycle Bin in unmanaged domains.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级