Users Guide

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
When launching Array Builder from a <Create configuration file> selection in the deployment action, a
default embedded controller is created.
When a controller is created, a default variable condition, array and disk(s) are created to ensure a valid
configuration. You can choose to leave the controller unconfigured - with disks set to non-RAID, or you
can add arrays or do other actions.
Adding a Controller
1. To add a new controller, select a controller from the list, or select an embedded controller.
The Controllers drop-down menu is enabled.
2. Click Controllers → New Controller.
The Controller Configuration window is displayed.
18