2.4 Objects That Designer Does Not Model

Feature

Description

O (Organization) and OU (Organizational Unit)

Ensure that O or OU objects are created before deploying them.

Import the containers that contain O or OU objects. The following objects must be included in O or OU objects:

  • All O or OU objects that are Security Equivalences objects for any drivers.

  • O or OU objects that are used in any policies.

  • O or OU objects that are used in any job configurations.

  • O or OU objects that are used in GCVs.

Users

Ensure that the User objects are created before deploying them, especially the admin users. The list of users can be collected in two different ways:

Import the containers that contain the user objects. The following objects must be included in the list:

  • Security Equivalences and Exclude Administrator Roles for all the drivers.

  • Static Members on groups and RBE policies.

  • Search identities and Memebrship Filter on Dynamic groups and RBE policies.

  • Users that are used in any policies.

  • Users that are used in any job configurations.

  • Users that are used in GCVs.

Groups

Ensure that the static and dynamic group objects are created before deploying them.

Import the containers that contain the groups. The following objects must be included in the list:

  • Groups that are used in any policies.

  • Groups that are used in any job configurations.

  • Groups that are used in GCVs.

Password Policies

Ensure that the policies are created before deploying them.

Indices

Ensure that indices are created before deploying them.

Custom Objects

User-defined objects ar not defined in Designer. Manually create them before deploying.

Import the containers that contain the custom objects. The following objects must be included in the list:

  • All custom objects that are Security Equivalences objects for all the drivers.

  • Custom objects that are used in any policies.

  • Custom objects that are used in any job configurations.

  • Custom objects that are used in GCVs.

Designer 3.5 and later allows you to import objects listed in the above table in LDIF format and then deploy them along with other objects that are being deployed.

NOTE:These objects are not modeled as drivers or driver sets in Designer. They can be modified by modifying the LDIF file that contains these objects in Designer. For more information, refer to Enabling Staging of Projects in the Designer 3.5 Administration Guide.