Users Guide
• (Optional) In OMIMSSC for SCCM:
• Create a task sequence.
For more information, see Creating task sequence.
• For non-Windows OS deployment, have a device type credential prole. For more information, see Creating credential prole.
• Create an unattended boot media. For more information, see Creating LC boot media.
• (Optional) In OMIMSSC for SCVMM:
• Create a hypervisor prole. For information about creating hypervisor prole, see Creating hypervisor prole.
• For Windows deployment, have a device type credential prole. For more information, see Creating credential prole.
About this task
You can create an Operational Template by capturing the conguration of the reference server. After capturing the conguration, you can
directly save the template, or edit the attributes for update source, hardware conguration, and windows component as per your
requirement. Now you can save the template, which can be used for other PowerEdge homogenous servers.
Steps
1 In OMIMSSC, do any of the following to open Operational Template:
• In the OMIMSSC dashboard, click Create Operational Template.
• In the navigation pane, click Proles > Operational Template, and then click Create.
The Operational Template wizard is displayed.
2 Provide a name and description for the template. Also, provide the IP address of the reference server, and then click Next.
NOTE: You can capture the conguration of reference server with iDRAC 2.0 and
later.
3 In Server Components, click a component to view the available attributes and their values.
The components are as follows:
• Firmware update
• Hardware components, which are RAID, NIC, and BIOS
• Operating system—select either Windows, or ESXi, or RHEL
4 (Optional) edit the values for the available attributes, if necessary.
5 Select the check box against each component as only the selected components conguration of selected components is applied when
the Operational Template is applied on all the congurations that are captured.
In Operating System component, perform the steps in either of the following options, as per your requirement:
• For Windows OS deployment on SCCM, see Windows component for the OMIMSSC console extension for SCCM.
• For Windows OS deployment on SCVMM, see Windows component for the OMIMSSC console extension for SCVMM.
• OMIMSSC
• For non-Windows OS deployment, see Non-Windows component for the OMIMSSC console extensions.
6 To save the prole, click Finish.
Windows OS component for OMIMSSC console extension for SCCM
About this task
While creating the Operational Template, perform the following steps for windows component:
Steps
1 Select a task sequence and deployment method.
NOTE
: Only the task sequences deployed on collections are listed in the drop-down menu.
For information about task sequence, see Task sequence.
2 Select one of the following options for the Deployment method:
• Boot to network ISO—reboots specied ISO.
Operational Template
35