Users Guide

address of the domain controller>
racadm set iDRAC.ActiveDirectory.DomainController3 <fully qualified domain name or IP
address of the domain controller>
racadm set iDRAC.ActiveDirectory.GlobalCatalog1 <fully qualified domain name or IP
address of the domain controller>
racadm set iDRAC.ActiveDirectory.GlobalCatalog2 <fully qualified domain name or IP
address of the domain controller>
racadm set iDRAC.ActiveDirectory.GlobalCatalog3 <fully qualified domain name or IP
address of the domain controller>
• Enter the Fully Qualied Domain Name (FQDN) of the domain controller, not the FQDN of the domain. For example, enter
servername.dell.com instead of dell.com.
• For bit-mask values for specic Role Group permissions, see Default role group privileges.
• You must provide at least one of the three domain controller addresses. iDRAC attempts to connect to each of the
congured addresses one-by-one until it makes a successful connection. With Standard Schema, these are the addresses of
the domain controllers where the user accounts and the role groups are located.
• The Global Catalog server is only required for standard schema when the user accounts and role groups are in dierent
domains. In multiple domain case, only the Universal Group can be used.
• If certicate validation is enabled, the FQDN or IP address that you specify in this eld must match the Subject or Subject
Alternative Name eld of your domain controller certicate.
• To disable the certicate validation during SSL handshake, use the following command:
racadm set iDRAC.ActiveDirectory.CertValidationEnable 0
In this case, no Certicate Authority (CA) certicate needs to be uploaded.
• To enforce the certicate validation during SSL handshake (optional), use the following command:
racadm set iDRAC.ActiveDirectory.CertValidationEnable 1
In this case, you must upload the CA certicate using the following command:
racadm sslcertupload -t 0x2 -f <ADS root CA certificate>
NOTE: If certicate validation is enabled, specify the Domain Controller Server addresses and the Global Catalog
FQDN. Ensure that DNS is congured correctly under
Overview → iDRAC Settings → Network.
Using the following RACADM command may be optional.
racadm sslcertdownload -t 0x1 -f <RAC SSL certificate>
2. If DHCP is enabled on iDRAC and you want to use the DNS provided by the DHCP server, enter the following command:
racadm set iDRAC.IPv4.DNSFromDHCP 1
3. If DHCP is disabled on iDRAC or you want manually enter the DNS IP address, enter the following RACADM command:
racadm set iDRAC.IPv4.DNSFromDHCP 0
racadm set iDRAC.IPv4.DNSFromDHCP.DNS1 <primary DNS IP address>
racadm set iDRAC.IPv4.DNSFromDHCP.DNS2 <secondary DNS IP address>
4. If you want to congure a list of user domains so that you only need to enter the user name when logging in to the web
interface, use the following command:
racadm set iDRAC.UserDomain.<index>.Name <fully qualified domain name or IP Address of
the domain controller>
You can congure up to 40 user domains with index numbers between 1 and 40.
Extended schema Active Directory overview
Using the extended schema solution requires the Active Directory schema extension.
Best practices for extended schema
The extended schema uses Dell association objects to join iDRAC and permission. This allows you to use iDRAC based on the overall
permissions granted. The default Access Control List (ACL) of Dell Association objects allows Self and Domain Administrators to
manage the permissions and scope of iDRAC objects.
By default, the Dell Association objects do not inherit all permissions from the parent Active Directory objects. If you enable
inheritance for the Dell Association object, the inherited permissions for that association object are granted to the selected users and
groups. This may result in unintended privileges being provided to the iDRAC.
134