Owner's Manual

Using OS Deployment tasks from multiple Original Equipment
Manufacturers (OEMs) within the same task sequence
Scenario:
To create a task sequence in Configuration Manager that performs system hardware configuration and operating system
deployment, and works on multiple hardware platforms, enabling you to add Original Equipment Manufacturer (OEM)
hardware configuration steps from more than one vendor into the same task sequence.
Note: All the following references to OEMs do not include Dell.
Issue:
The OEM add-ons for system hardware configuration utilize pre-configured templates to arrange steps in the task
sequence in a proper order. When you add a new OEM step into a task sequence, it first checks to see if the task
sequence already has any OEM steps in it. If there are no steps, it prompts you for automatic configuration of the steps.
In certain cases, such as the addition of a "Reboot to PXE or USB" step, if you do not allow the automatic
reconfiguration, it will fail.
In the first released version of the integration components on which the OEM hardware configuration add-ins are built,
the Form checks for pre-existing OEM task steps, but does not check for other existing OEM steps. This causes an issue
where adding one OEM step to an existing task sequence created by another OEM's automatic configuration causes the
newly-added step to be taken as the first OEM step in the task sequence.
In case of the hardware configuration step, cancel the reconfiguration because it would still add a valid task step to the
sequence. However, if you are adding a "Reboot to PXE or USB" step, canceling the automatic reconfiguration will
leave the task step un-configured and invalid. Accepting the Reconfiguration will re-apply the original grouping and
reorganization to the task sequence, which will also render it invalid.
Solution:
The initial OEM release works correctly on its own and subsequent versions of the underlying integration components
will check for existing steps from any OEM. Therefore, ensure that you use the following procedure for using steps
from multiple OEMs in a task sequence:
1. Create a new task sequence with OEM configuration steps (preferably, use the right-click action on the Task
Sequences" node).
2. You can now add steps from any OEM into a task sequence and it will be handled correctly.
Known Issues
Task Sequence Issues/Limitations:
 In the task sequence saving the BIOS settings with the option "[Configuration saved as a Variable]" fails to
apply BIOS settings. Save the settings in an .INI file to successfully apply BIOS settings.
Array Builder Issues/Limitations:
 CERC SATA 1.5/6-Channel (CH), and CERC SATA 1.5/2S controllers are not supported in Dell Server
Deployment Pack.
 RAID configuration on PERC S100/S300 controllers are not supported with X64 boot images. Use X86 boot
image or manually configure the RAID before Operating system deployment.
Limitations: