Chat now with support
Chat with Support

Active Roles 7.6.1 - 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 AutoProvisioning for SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Office 365 and Azure Tenant Selection 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
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 One Identity Starling Management Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users Azure AD, Office 365, and Exchange Online management
Configuring Active Roles to manage hybrid AD objects Managing Hybrid AD Users Unified provisioning policy for Azure O365 Tenant Selection, Office 365 License Selection, and Office 365 Roles Selection, and OneDrive provisioning Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Office 365 Groups Managing Azure Security Groups Managing cloud-only distribution 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
Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing 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 Appendix A: Using regular expressions Appendix B: Administrative Template Appendix C: Communication ports Appendix D: Active Roles and supported Azure environments Appendix E: Active Roles integration with other One Identity and Quest products Appendix F: Active Roles integration with Duo Appendix G: Active Roles integration with Okta

Steps for administering a Group Family

This topic covers some task-specific procedures that you can use to change configuration and properties of an existing Group Family.

To open the property sheet for a Group Family

  • Right-click the Group Family configuration storage group, and then click Properties.

To view or modify grouping rules

  1. Open the property sheet for the Group Family (see instructions earlier in this topic).
  2. Click the Groupings tab, and then click Configure.
  3. Follow Steps 5 through 7 of the procedure for creating a Group Family (see Steps for creating a Group Family).
  4. On the Group-by Properties page, click Finish.
  5. Click OK to close the property sheet.

To view or modify group creation-related rules

  1. Open the property sheet for the Group Family (see instructions earlier in this topic).
  2. Click the Controlled Groups tab, and then click Manage Rules.
  3. Follow Steps 9 through 12 of the procedure for creating a Group Family (see Steps for creating a Group Family).
  4. On the Exchange-related Settings page, click Finish.
  5. Click OK to close the property sheet.

To manually add a group to a Group Family

  1. Open the property sheet for the Group Family (see instructions earlier in this topic).
  2. Click the Controlled Groups tab, and then click Capture Groups.
  3. In the Capture Groups window, click Add.
    1. In the Assign Group to Grouping dialog box, do the following, and then click OK:
    2. Click Select, and then select the group you want to add.
  4. In Group-by property, type a value of the group-by property. If multiple group-by properties are defined, type a value for each, so as to determine the grouping to which you want the group to be assigned.
  5. Click OK to close the Capture Groups window.
  6. Click OK to close the property sheet.

To remove a group from a group family

  1. Open the property sheet for the Group Family (see instructions earlier in this topic).
  2. Click the Controlled Groups tab, and then click Capture Groups.
  3. In the Capture Groups window, select the group you want to remove from the Group Family, click Remove, and then click OK.
  4. Click OK to close the property sheet.

To schedule a Group Family update

  1. Open the property sheet for the Group Family (see instructions earlier in this topic).
  2. Click the Schedule tab, and then click Configure.
  3. On the Group Family Scheduling page, do the following, and then click Finish:
    1. Select Schedule Group Family to run, and then set the appropriate date, time, and frequency of Group Family update.
    2. If you also want the Group Family to run one time immediately after you close the property sheet, select Run Group Family once after completing this page.
    3. From the Run on this server list, select the Administration Service you want to run the Group Family.
  4. Click OK to close the property sheet.

To view results of a Group Family update

  1. Open the property sheet for the Group Family (see instructions earlier in this topic).
  2. Click the Action Summary tab, and then click View Log.

To delete a Group Family

  • Right-click the Group Family configuration storage group, and then click Delete.

NOTE: Deleting a Group Family only deletes the configuration storage group of the Group Family. This operation does not delete the controlled groups of the Group Family. Later, you can configure another Group Family to take control of those groups.

Scenario: Departmental Group Family

Suppose the organizational unit (OU) named Users contains a number of user accounts. Also assume that for each of the values listed below there are one or more user accounts in the Users OU with the Department property set to that value. Thus, the following values of the Department property are encountered in the user accounts held in the Users OU:

  • Accounting
  • Executive Services
  • Facilities
  • Finance
  • Government Services
  • Human Resources
  • Information Technology
  • Operations

In this section, you can find the instructions on how to implement a Group Family that creates and maintains a separate group for users in each of those departments. The Group Family configuration storage group will be created in the organizational unit named Groups. The Group Family will be configured to create the departmental groups in that same OU.

Open the Active Roles console, and perform the following steps to implement the Group Family.

To create and run the Departmental Group Family

  1. Right-click the Groups OU and select New | Group Family.

This will start the New Group Family wizard. The remaining steps apply to that wizard.

  1. On the Welcome page, click Next.
  2. In the Group Family name box, type Departmental Group Family. Click Next.
  3. Click the Pre-configured grouping by option, click Department in the list under that option, and then click Next.
  4. Remove the Groups OU from the Containers list, and add the Users OU to that list. Click Next.
  5. Click the User option, and then click Next.
  6. Verify that the Group by these properties list includes the only entry—Department. Click Next.
  7. Select the Skip this step, without capturing groups manually check box. Click Next.
  8. Click Next to accept the default rule for group naming: CG-%<key.department>
  9. Click Next to accept the default group scope and type.
  10. Click Next to accept the default location for the controlled groups: Group Family home OU
  11. Click Next to accept the default settings related to Exchange.
  12. Select the Run Group Family once after completing this page check box. Click Next.
  13. Click Finish.

Once you have completed these steps, the Group Family performs all the necessary processing to create the groups, one group per department, and adds users to the appropriate groups based on the Department property.

You might look at the contents of the Groups OU in the Active Roles console to verify that the departmental groups are created successfully. You might also examine properties of a group generated by the Group Family, to verify that the membership list of the group is correct. For example, the membership list of the CG-Executive Services group consists of the user accounts that have the Department property set to Executive Services.

Dynamic Groups

Understanding dynamic groups

Active Directory allows groups (herein called basic groups) to include members statically—select objects and add them to groups. Active Roles provides a flexible, rules-based mechanism for populating groups. Once set up, the process automatically adds and removes members from groups.

Active Roles provides rules-based groups called dynamic groups. Membership rules determine whether an object is a member of a dynamic group. A membership rule may take a form of search query, object static inclusion and exclusion rule, and group member inclusion and exclusion rule. As the environment changes, the memberships of objects in dynamic groups automatically change to adapt to the new environment.

Active Roles dynamic groups reduce the cost of maintaining lists and groups, while increasing the accuracy and reliability of this maintenance. Furthermore, it automatically keeps distribution lists and security groups up to date, eliminating the need to add and remove members manually.

To automate the maintenance of group membership lists, dynamic groups provide the following features:

  • Rules-based mechanism that automatically adds and removes objects from groups whenever object attributes change in Active Directory.
  • Flexible membership criteria that enable both query-based and static population of groups.

In the Active Roles console, dynamic groups are marked with the following icon:

When you convert a basic group to a dynamic group, the group loses all members that were added to the group when it was a basic group. This is because members of a dynamic group can be defined only by membership rules.

When you convert a dynamic group to a basic group, the group retains all its members included due to the membership rules, and loses the membership rules only.

When a member of a dynamic group, such as a user or another group, is deprovisioned, the dynamic group is automatically updated to remove that member. Hence, deprovisioning a user or group removes that user or group from all dynamic groups. This behavior is by design.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating