Users Guide
Each attribute or class that is added to an existing Active Directory Schema must be dened with a unique ID. To maintain unique IDs
across the industry, Microsoft maintains a database of Active Directory Object Identiers (OIDs) so that when companies add extensions to
the schema, they can be guaranteed to be unique and not to conict with each other. To extend the schema in Microsoft's Active
Directory, Dell received unique OIDs, unique name extensions, and uniquely linked attribute IDs for the attributes and classes that are added
into the directory service.
• Dell extension: dell
• Dell base OID: 1.2.840.113556.1.8000.1280
• RAC LinkID range: 12070 to 12079
Overview of Schema Extensions
Dell has extended the schema to include an Association, Device, and Privilege property. The Association property is used to link together
the users or groups with a specic set of privileges to one or more RAC devices. This model provides an administrator maximum exibility
over the dierent combinations of users, RAC privileges, and RAC devices on the network without much complexity.
When there are two CMCs on the network that you want to integrate with Active Directory for authentication and authorization, create at
least one association object and one RAC device object for each CMC. You can create multiple association objects, and each association
object can be linked to as many users, groups of users, or RAC device objects as required. The users and RAC device objects can be
members of any domain in the enterprise.
However, each association object can be linked (or, may link users, groups of users, or RAC device objects) to only one privilege object. This
example allows an administrator to control each user’s privileges on specic CMCs.
The RAC device object is the link to RAC rmware for querying Active Directory for authentication and authorization. When a RAC is added
to the network, the administrator must congure the RAC and its device object with its Active Directory name so that users can perform
authentication and authorization with Active Directory. Additionally, the administrator must add the RAC to at least one association object
for users to authenticate.
The following gure shows that the association object provides the connection that is needed for the authentication and authorization.
NOTE
: The RAC privilege object applies to DRAC 4, DRAC 5, and CMC.
You can create as many or as few association objects as required. However, you must create at least one Association Object, and you must
have one RAC device object for each RAC (CMC) on the network that you want to integrate with Active Directory.
Figure 8. Typical Setup for Active Directory Objects
146
Conguring User Accounts and Privileges