지금 지원 담당자와 채팅
지원 담당자와 채팅

Active Roles 8.1.1 - Administration Guide

Introduction 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
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 Configure 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 Azure AD, Microsoft 365, and Exchange Online Management
Configuring Active Roles to manage Hybrid AD objects Managing Hybrid AD users
Creating a new Azure AD user with the Web Interface Viewing or updating the Azure AD user properties with the Web Interface Viewing or modifying the manager of a hybrid Azure user Disabling an Azure AD user Enabling an Azure AD user Deprovisioning of an Azure AD user Undo deprovisioning of an Azure AD user Adding an Azure AD user to a group Removing an Azure AD user from a group View the change history and user activity for an Azure AD user Deleting an Azure AD user with the Web Interface Creating a new hybrid Azure user with the Active Roles Web Interface Converting an on-premises user with an Exchange mailbox to a hybrid Azure user Licensing a hybrid Azure user for an Exchange Online mailbox Viewing or modifying the Exchange Online properties of a hybrid Azure user Creating a new Azure AD user with Management Shell Updating the Azure AD user properties with the Management Shell Viewing the Azure AD user properties with the Management Shell Delete an Azure AD user with the Management Shell Assigning Microsoft 365 licenses to new hybrid users Assigning Microsoft 365 licenses to existing hybrid users Modifying or removing Microsoft 365 licenses assigned to hybrid users Updating Microsoft 365 licenses display names
Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Microsoft 365 roles management for hybrid environment users Managing Microsoft 365 contacts Managing Hybrid AD groups Managing Microsoft 365 Groups Managing cloud-only distribution groups Managing cloud-only dynamic distribution 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 cloud-only shared mailboxes
Modern Authentication 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 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

Steps for configuring a User Logon Name Generation policy

To configure a User Logon Name Generation policy

  1. On the Policy to Configure page, select User Logon Name Generation, and then click Next.

  2. On the User Logon Name (pre-Windows 2000) Generation Rules page, do the following:

    • Click Add, and complete the Configure Value dialog by using the procedure outlined later in this topic, to create a name generation rule.

    • Select a rule and click Remove to delete the rule.

    • Select a rule and click View/Edit to modify the rule.

    • Select a rule and click Up or Down to move the rule higher or lower in the list, in order to give the rule a higher or lower priority, respectively.

    • Click Advanced to set some options that apply to all rules within the policy. Complete the Advanced dialog by using the procedure outlined later in this topic.

      • If you want the logon name to be allowed for manual edit, select Allow manual edits of pre-Windows 2000 logon name. Then, do one of the following:

        • Click Always to authorize the operator who creates or updates the user account to modify the pre-Windows 2000 logon name.

        • Click Only if a unique name cannot be generated by this policy to allow manual changes only in the situation where a policy-generated name is already assigned to a different user account.

      Click Next.

  3. On the Enforce Policy page, you can specify objects to which this Policy Object is to be applied:

    • Click Add, and use the Select Objects dialog to locate and select the objects you want.

  4. Click Next, and then click Finish.

To complete the Configure Value dialog

  1. Click Add.

  2. Configure an entry to include in the value. For more information, see Steps for configuring entries.

  3. In the Configure Value dialog, add more entries, delete or edit existing ones, and then click OK.

To complete the Advanced dialog

  1. In Maximum length, in characters, set the maximum length of the generated name.

  2. Optionally, select Adjust the case of characters to configure case formatting:

    • Click All UPPERCASE to format the name as the uppercase string.

    • Click All lowercase to format the name as the lowercase string.

  3. Specify the scope in which you want the generated name to be unique:

    • Click Domain to make the name unique within the domain.

    • Click Forest to make the name unique within the forest.

    • Click All managed domains to make the name unique across all managed domains.

  4. Optionally, in the Restricted characters area, specify the characters you want the policy to remove from the generated name.

    The policy always removes the following characters: " @ * + | = \ : ; ? [ ] , < > /

    To specify additional characters, type them one by one, without any separator character, in the provided text box.

Scenario 1: Using uniqueness number

The policy described in this scenario generates the pre-Windows 2000 user logon name in accordance with this rule: the first character of the user first name, optionally followed by a uniqueness number, followed by the user last name. The length of the policy-generated name is at most eight characters. If the name is longer, trailing characters are truncated as needed. Examples of names generated by this policy are as follows:

  • JSmitson

  • J1Smitso

  • J2Smitso

The policy generates the name J1Smitso for the user John Smitson if the name JSmitson is in use. If both JSmitson and J1Smitso are in use, the policy generates the name J2Smitso, and so on.

To implement this scenario, you must perform the following actions:

  1. Create and configure the Policy Object that defines the appropriate policy.

  2. Apply the Policy Object to a domain, OU, or Managed Unit.

As a result, when assigning a pre-Windows 2000 user logon name to a user account in the container you selected in Step 2, the Active Roles user interfaces provide a Generate button to create a name in accordance with the policy rule. In the event of a naming conflict, clicking Generate causes the policy to add a uniqueness number to the name.

The following two sections elaborate on the steps to implement this scenario.

Step 1: Creating and configuring the Policy Object

You can create and configure the Policy Object you need by using the New Provisioning Policy Object Wizard. For information about the wizard, see Creating a Policy Object.

To configure the policy, click User Logon Name Generation on the Select Policy Type page of the wizard. Then, click Next.

On the User Logon Name (pre-Windows 2000) Generation Rules page, click Add. Then, complete the Configure Value dialog as follows:

  1. Click Add.

  2. Configure the entry to include the first character of the user first name:

    1. Under Entry type, click User Property.

    2. Under Entry properties, click Select.

    3. In the Select Object Property window, click First Name in the Object property list, and then click OK.

    4. Under Entry properties, click The first, and make sure the box next to that option reads 1.

    5. Click OK.

  3. Click Add.

  4. Configure the entry to optionally include a uniqueness number:

    1. Under Entry type, click Uniqueness Number.

    2. Under Entry properties, click Add if the property value is in use, and make sure the Fixed-length number, with leading zeroes check box is cleared.

    3. Click OK.

  5. Click Add.

  6. Configure the entry to include the user last name:

    1. Under Entry type, click User Property.

    2. Under Entry properties, click Select.

    3. In the Select Object Property window, click Last Name in the Object property list, and then click OK.

    4. Click OK.

After you complete these steps, the list of entries in the Configure Value dialog should look like the following figure.

Figure 60: Configure Value

Click OK to close the Configure Value dialog.

You also need to set up the limitation on the length of the name. On the User Logon Name (pre-Windows 2000) Generation Rules page, click Advanced. In the Advanced dialog, in the Maximum length, in characters box, type 8, and then click OK.

Click Next and follow the instructions in the wizard to create the Policy Object.

Step 2: Applying the Policy Object

You can apply the Policy Object by using the Enforce Policy page in the New Provisioning Policy Object Wizard, or you can complete the wizard and then use the Enforce Policy command on the domain, OU, or Managed Unit where you want to apply the policy.

For more information on how to apply a Policy Object, see Applying Policy Objects and Managing policy scope.

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택