Chat now with support
Chat with Support

Active Roles 7.2 - 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 Home Folder AutoProvisioning Script Execution User Account Deprovisioning 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 Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing managed domains Using unmanaged domains Evaluating product usage Configuring replication Using AlwaysOn Availability Groups Using database mirroring 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
Using regular expressions Administrative Template Communication ports

Steps for configuring an E-mail Alias Generation policy

Rule-based AutoProvisioning and Deprovisioning > Policy configuration tasks > E-mail Alias Generation > Steps for configuring an E-mail Alias Generation policy

To configure an E-mail Alias Generation policy

  1. On the Policy to Configure page, select E-mail Alias Generation, and then click Next.
  2. On the E-mail Alias Generation Rule page, do the following, and then click Next:
    • Select one of the pre-configured generation rules, or create a custom alias-generation rule. To create a custom rule, click Other combination of user properties, click Configure, and complete the Configure Value dialog box by using the procedure outlined later in this topic.
    • If you want the e-mail alias to be allowed for manual edit, select Allow manual edits of e-mail alias. Then, do one the following:
      • Click Always to authorize the operator who creates or updates the user account to modify the e-mail alias.
      • Click Only if a unique alias cannot be generated by this policy to allow manual changes only in the situation where a policy-generated alias is already assigned to a different user account.
  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 box to locate and select the objects you want.
  4. Click Next, and then click Finish.

To complete the Configure Value dialog box

  1. Click Add.
  2. Configure an entry to include in the value (for instructions, see Steps for configuring entries).
  3. In the Configure Value dialog box, add more entries, delete or edit existing ones, and then click OK.

Scenario: Generating e-mail alias based on user names

The policy described in this scenario generates the e-mail alias in accordance with this rule: user first name, optionally followed by a three-digit uniqueness number, followed by a period, followed by the user last name. Examples of aliases generated by this rule are as follows:

  • John.Smith
  • John001.Smith
  • John002.Smith

The policy generates the alias John001.Smith for the user John Smith if the alias John.Smith is in use. If both John.Smith and John001.Smith are in use, the policy generates the alias John002.Smith, 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 an e-mail alias to a user account in the container you selected in Step 2, the Active Roles user interfaces provide a Generate button to create the alias in accordance with the policy rule. In the event of an alias naming conflict, clicking the Generate button causes the policy to add a uniqueness number to the alias.

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

Step 1: Creating and configuring the Policy Object

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 in the Policy Object management tasks section earlier in this chapter.

To configure the policy, click E-mail Alias Generation on the Select Policy Type page of the wizard. Then, click Next.

On the E-mail Alias Generation Rule page, click Other combination of user properties, and then click Configure.

Complete the Configure Value dialog box as follows:

  1. Click Add.
  2. Configure the entry to include 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. 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, set the entry options:
      • Click Add if the property value is in use.
      • Select the Fixed-length number, with leading zeroes check box.
      • In the box next to Length of the number, in digits, type 3.
    3. Click OK.
  5. Click Add.
  6. Configure the entry to include the period character:
    1. In Text value under Entry properties, type the period character.
    2. Click OK.
  7. Click Add.
  8. 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 box should look as shown in the following figure.

  1. Click OK to close the Configure Value dialog box. Then, click Next and follow the instructions in the wizard to create the Policy Object.

Step 2: Applying 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 earlier in this chapter.

Related Documents