With the Active Roles Console, you can export Managed Units to an .xml file and then import them from that file to populate another instance of Active Roles. The export and import operations provide a way to move Managed Units from a test environment to a production environment.
To export Managed Units, select them, right-click the selection, and select All Tasks > Export. In the Export Objects dialog, specify the file where you want to save the data, and click Save.
To import Managed Units, right-click the container where you want to place the Managed Units, then click Import. In the Import Directory Objects dialog, select the file to which the Managed Units were exported, and click Open.
NOTE: When you export and then import a Managed Unit, only membership rules are transferred along with other properties of the Managed Unit. The permission and policy settings of the Managed Unit are not exported. You need to reconfigure them manually after you import the Managed Unit.
You can rename a Managed Unit with the Rename setting of the Active Roles Console.
To rename a Managed Unit
-
In the Active Roles Console, on the Console tree, navigate to Configuration > Managed Units.
-
Under Managed Units, locate the Managed Unit you want to rename, right-click it, and click Rename.
-
Enter a new name, then press Enter.
NOTE: Renaming a Managed Unit does not affect the membership rules, permission settings, or policy settings associated with the Managed Unit.
You can delete existing Managed Units with the Active Roles Console.
To delete a Managed Unit
-
In the Active Roles Console, on the Console tree, navigate to Configuration > Managed Units.
-
Under Managed Units, locate the Managed Unit you want to delete, right-click it, and click Delete.
NOTE: When you delete a Managed Unit, its members are not deleted. However, the permission settings and the policy settings that were specified via the Managed Unit are no longer in effect after the Managed Unit has been deleted.
This scenario involves the creation of an administrative view named Sales in an organization with an OU-based structure of Active Directory.
Suppose an organization has offices in USA and Canada. The rule for including a user in an OU is the geographical location of the user. Therefore, all users who work in USA reside in the USA OU, and those working in Canada reside in the Canada OU.
The offices in USA and Canada each have Marketing, Development, and Sales departments. By creating a Sales MU, it is possible to manage users from the Sales departments in USA and Canada collectively, without changing the actual OU-based structure.
When delegating control of an MU, all users that belong to the MU inherit security settings defined at the level of the Managed Unit. Thus, applying an Access Template to a Managed Unit specifies the security settings for each user in the MU.
To implement this scenario, perform the following steps:
-
Create the Sales MU.
-
Add users from the Sales department in USA and Canada to the Sales MU.
-
Prepare the Sales Access Template.
-
Apply the Sales Access Template to the Sales MU, and designate an appropriate group as a Trustee.
As a result, the members of the group gain control of user accounts that belong to the Sales MU. The scope of control is defined by the permissions in the Sales Access Template.
The following sections elaborate on the steps to implement this scenario.