Users Guide
A graceful reboot of the server is attempted when the Do not forcefully reboot the host OS option is selected. If the
reboot fails, you must rerun the template deployment task.
c. Select the Use strict checking check box to match the VLANs with like characteristics. If unselected, only VLAN name
and QoS are used for matching
NOTE: This option is displayed only if the selected target devices are modular system sleds.
d. Click Next.
3. If the target device is a server, in the Boot to Network ISO section:
a. Select the Boot to Network ISO check box.
b. Select either CIFS or NFS as the share type, and then enter information in the fields such as ISO image file path and
share location where the ISO image file is stored.
c. Select the Time to Attach ISO dropdown menu options to set the number of hours the network ISO file will remain
mapped to the target device(s). By default, this value is set as four hours.
d. Click Next.
4. In the iDRAC Management IP section, change the target device IP settings if required, and then click Next.
NOTE:
● Template deployment fails if DHCP settings are assigned during template deployment to a target device that was
originally discovered using a static IP.
● If the IP setting is not configured on the discovered MX7000 sled, the Boot to Network ISO operation is not run
during the template deployment.
5. In the Target Attributes section, the non-virtual identity attributes specific to each of the selected target devices, such as
the location attributes and IP address, can be changed before deploying the deployment template. When the template is
deployed, these changed target attributes are implemented on only the specific devices. To change the device-specific, non-
virtual identity attributes:
a. Select a target device from the list displaying the previously-selected target devices.
b. Expand the attribute categories and then select or clear the attributes that must be included or excluded during template
deployment on the target device.
c. Click Next.
6. In the Virtual Identities section, click Reserve identities.
The assigned virtual identities of the NIC cards of the selected target device are displayed. To view all the assigned identities
of the identity pool of the selected target device, click View all NIC details.
NOTE:
If identities are already assigned outside of the appliance, then a new deployment will not use those identities
unless they are cleared. For more information, see Identity pools on page 70
7. In the Schedule section, run the job immediately or schedule for a later time. See Schedule job field definitions on page 159.
8. Click Finish. Review the warning message and click YES.
A Device Configuration job is created. See Using jobs for device control on page 101.
Deploy IOA deployment templates
NOTE:
To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based
OpenManage Enterprise user privileges on page 14.
Before you begin deploying an IOA deployment template, ensure that:
● You have created an IOA deployment template for deployment. See Create a deployment template from a reference device
on page 61.
● The target devices meet the requirements that are specified in Minimum system requirements for deploying OpenManage
Enterprise on page 18.
● Firmware version of the target device is the same as the IOA deployment template.
● Only the following cross template deployments are supported:
Table 13. Supported cross template deployments
IOA Deployment template mode Supported IOA template modes of target
Standalone Standalone, PMUX
66 Manage device deployment templates