Users Guide
2. In the working pane, click View Details.
On the Template Details page, the deployment template name, description, the reference device from which the
deployment template was created, and the last updated date by the OpenManage Enterprise user information is displayed.
3. Right-click an element to expand all or collapse all the child elements in the Configuration Details section to display all the
attributes that are used for creating the deployment template. You can also expand individual child elements specific to a
parent element. For example, if you selected that iDRAC and BIOS elements must be used for cloning on the target device,
attributes related only to such elements are displayed.
Edit a server deployment template
Built-in deployment templates cannot be edited. Only the user-created deployment templates that are identified as ‘Custom’ can
be edited. You can edit the attributes of a deployment template irrespective of whether you created it by using a reference
template file or a reference device.
1. On the Configuration > Templates page, select the required custom template check box, and then click Edit.
2. In the Edit Template dialog box:
a. In the Template Information section, edit the deployment template name and description. The template type cannot be
edited.
b. Click Next.
c. In the Edit Components section, the deployment template attributes are displayed in:
● The Guided view — This view of attributes displays only common attributes, grouped together by function.
Attributes from the following categories are shown:
i. In the BIOS Settings section, select any one of the following:
○ Manually: Enables you to manually define the following BIOS properties:
￭ System profile: From the drop-down menu, select to specify the type of performance optimization to be
achieved in the system profile.
￭ User accessible USB ports: From the drop-down menu, select to specify the ports that the user can
access.
￭ By default, the use of logical processor and in-band manageability are enabled.
○ Optimize based on workload: From the Select workload profile drop-down menu, select to specify the type
of workload performance optimization you want achieve on the profile.
ii. Click Boot and define the boot mode:
○ If you select BIOS as the boot mode, do the following:
￭ To retry the boot sequence, select the Enabled check box.
￭ Drag the items to set the boot sequence and hard drive sequence.
○ If you select UEFI as the boot mode, drag the items to set the UEFI boot sequence. If required, select the
check box to enable the Secureboot feature.
iii. Click Networking. All the networks associated with the deployment template are displayed under Network
Interfaces.
○ To associate an optional identity pool to the deployment template, select from the Identity pool drop-down
menu. The networks associated with the selected identity pool is displayed. If the deployment template is
edited in the Advanced view, the Identity pool selection is disabled for this deployment template.
￭ To view the network properties, expand the network.
￭ To edit the properties, click the corresponding pen symbol.
- Select the protocol to be used for booting. Select only if the protocol is supported by your network.
- Select the Untagged and Tagged network to be associated to the network
- The partition, max, and min bandwidth are displayed from the deployment template (profile) we created
earlier.
￭ Click Finish. The network settings of the deployment template is saved.
● The Advanced view — This view lists all the deployment template attributes that can be changed (including those
shown in the Guided view). This view allows you to specify not only attribute values (like the Guided view), but also
whether or not each attribute gets included when the deployment template is deployed to a target device.
Attributes are grouped together functionally for display. Vendor-specific attributes are grouped under Other
Attributes. Each individual attribute is displayed with a check box preceding its name. The check box indicates
whether or not the attribute will be included when the deployment template is deployed to a target device. Because
Manage device deployment templates
63