User's Manual

4. Save the file in the default directory.
An example of default directory: \\<site server hostname>\sms_<site code>\OSD\lib\Packages\Deployment\Dell
\PowerEdge\DTK\Template\Configs\Raidcfg.
5. Click Apply to save the edited file to the task sequence.
Alternatively, you can select the <Create configuration file> option from the drop-down to create an ini file from the start.
<Import configuration file>
1. Select <Import configuration file> from the Configuration file/Command line parameters drop-down menu.
2. Click Import.
3. Specify the location of the configuration file you want to import and click Open.
<sample.xml>
1. Select <sample.xml> from the Configuration file / Command line parameters drop-down menu.
2. Click View.
The Array Builder wizard for the sample.xml is displayed.
3. To edit the sample.xml, see <Create configuration file>.
Using the Array Builder
Using Array Builder, you can define arrays/disk sets with all available RAID settings, logical drives/virtual disks of
varying sizes or use all available space, and assign hot spares to individual arrays or assign global hot spares to the
controller.
How Array Builder Works
When you run the task sequence on a target server, the array configuration utility detects the existing controller(s) on
the server as well as the disks attached to each controller. The custom action then tries to match the physical
configuration(s) the utility detected to the logical configurations you defined in the configuration rules. These array
configuration rules are defined using a graphical, logical layout that allows you to visualize how your array controllers
are configured. Rules are processed in the order displayed in the Array Builder tree, so you know exactly which rules
have priority.
You can define rules to match configurations based on detected slot number that the controller is in (or just the
embedded controller, if any), how many disks are attached to the controller, or simply apply a blanket configuration to
any controller the Array Builder finds. You can also apply configuration rules based on task sequence variables detected
on the server. This allows you to define different configurations to different servers even if the detected hardware is
identical.
Controllers
Controller elements contain variable condition elements. Controllers are one of several configuration types:
The embedded controller
A controller in slot "X"
Any controller with "X" disks
Any controller with "X" disks or more
All remaining controllers
17