Setup Guide

Server Configuration Profiles: User’s Guide
14 Server Configuration Profiles: Reference Guide | 456
4. If not using RepositoryUpdate, confirm that the target servers have similar iDRAC and device
firmware levels.
2.4.2 Active Directory Example
Configuring Active Directory on many iDRACs is a great example of how a golden template can be utilized.
There are a significant number of Active Directory settings and configuring them directly from the XML/JSON
template could prove to be difficult.
Instead, configure a single iDRAC’s Active Directory settings from the iDRAC GUI and confirm that the
settings are working as intended. Once confirmed, generate a template using SCP Export with the Clone
option. The template will contain populated values for Active Directory. The template can be adjusted if
needed, and then applied to an unlimited number of iDRACs to setup Active Directory on these systems.
That’s the true strength and flexibility of SCP. It enables the transfer of configuration settings to many setups
with a single template.
2.5 General Compatibility
There are a few things to consider regarding the compatibility of the template. Server Configuration Profiles
were originally introduced with iDRAC7 and this document is being released alongside iDRAC9 version 4.40.
Over the lifespan of SCP, new features have been added that may not be compatible with older versions of
iDRAC.
Additionally, feature sets for individual devices can change over their lifetime. The possible values for
attributes might be added or removed, or entire attributes might have been added or removed depending on
the firmware version of a device.
The factors like server model, platform capabilities, and license level can impact the presence of attributes in
a generated template or result in potential errors when applying a conflicting template.
SCP was designed to take all these factors into consideration. The template itself is backwards compatible
throughout all generations of iDRAC. The schema has remained unchanged from release until iDRAC9
version 4.40. See Include Custom Telemetry
.
SCP Import is also a ‘continue on error’ operation, which means if a setting fails to apply the remainder of the
settings will still be attempted. Any errors encountered will be clearly communicated in the
configuration
results of the job.
It is recommended, but not necessary, to generate a template from a server that has a similar configuration to
the target server(s). This will help reduce the chances of errors during SCP Import.