Cross-domain Group Family
When you configure a Group Family, you choose containers that hold the objects you want Group Family to assemble into groups (managed object containers) as well as the container to hold those groups (controlled group container). The Group Family policy has the option allowing you to select managed object containers from any domains registered with Active Roles. With this option, managed object containers may be from different domains and the domain of the controlled group container may be different from the domain of the managed object containers. Depending upon the location of the managed object containers, the groups controlled by Group Family can include objects from domains other than the domain that holds the controlled group container (external domains).
Active Directory has restrictions regarding the types of groups that can have members from external domains, and the types of groups that can have membership in other groups. All these restrictions apply to the groups controlled by Group Family. Thus, Active Roles does not allow Group Family to add objects from external domains to global groups, nor does it allow Group Family to add domain local groups to a global group. With these natural restrictions, you can configure Group Family so that its controlled groups include members from any domains registered with Active Roles.
As stated above, whether managed object containers can be selected from external domains depends upon the Group Family policy. If you want to use this capability, select the Enable cross-domain membership policy option (see Group Family policy options).
Group Family policy options
Group Family policy options determine the Group Family processing behavior. For instance, there is a policy option that determines whether controlled groups can have members from external domains.
You can view or change Group Family policy options in the Active Roles console as follows:
- In the console tree, select Configuration | Policies | Administration | Builtin.
- In the details pane, double-click Built-in Policy - Group Family.
- In the Built-in Policy - Group Family Properties dialog box, click the Policies tab, select the policy, and click View/Edit.
- In the Policy Properties dialog box that appears, click the Policy Settings tab.
The Policy Settings tab includes the following options:
- Enable cross-domain membership
Select this option if you want Group Family to support the grouping of objects from external domains. When selected, this option allows each Group Family instance to have managed object containers from any domains that are registered with Active Roles. If this option is not selected, the managed object containers must be from the domain of the Group Family configuration storage group.
Selecting this option should be considered a long-term commitment to scenarios where objects managed by Group Family may reside in domains other than the domain of the Group Family configuration storage group—external domains. Once you have enabled cross-domain membership, you can configure Group Family instances to look for managed objects in any domains registered with Active Roles. However, if you later decide to un-select this policy options, the Group Family instances that were configured to look for managed objects in external domains will cease to function. You will have to inspect and, if needed, reconfigure your existing Group Family instances to limit scope of managed objects to the domain of the Group Family configuration storage group.
- Enable support for non-stored virtual attributes
When selected, this option makes it possible for Group Family to perform grouping based on custom non-stored virtual attributes-the attributes that have their value calculated by a certain policy rather than stored in the Active Roles database. This option can have a negative effect on Group Family performance, so select it only if you have any of the Group Family group-by properties implemented as a custom non-stored virtual attribute.
This option is normally not selected for performance reasons, which causes Group Family not to create controlled groups that use a custom non-stored virtual attribute as a group-by property. You need to select this option if you want Group Family to create controlled groups by grouping objects based on custom non-stored virtual attributes.
Creating a Group Family
Creation of a Group Family is a two-step process that includes:
- Creating the Group Family configuration
- Running the Group Family to initially create or capture groups
The Active Roles console provides the New Group Family wizard for creating the Group Family configuration. The wizard creates a group, referred to as configuration storage group, and populates that group with the configuration data you specify.
Note that you can create any number of Group Families, with each Group Family intended to control a certain collection of groups. When linking a group to a grouping, the Group Family engine ensures the group is under the control of only the Group Family that created the link, thereby avoiding conflicts.
NOTE: Groups created through Group Family does not support group name with special characters, such as, /\[]:;|=*?<>".
Start the New Group Family wizard
You can start the New Group Family wizard in the Active Roles console by using the New | Group Family command on the organizational unit in which you want to place the configuration storage group.
To start the New Group Family wizard
- Right-click the organizational unit to hold the Group Family configuration storage group, and select New | Group Family.