Users Guide

10. If you want to continue reclaiming the virtual I/O identities of the server, click Yes.
The reclaim identities task is created and the task runs immediately. You can double-click the task in Task
Execution History to view the task execution details.
Reclaiming Assigned Virtual I/O Identities
You can also reclaim the assigned virtual I/O identities from a device based on your preference.
To reclaim the assigned virtual I/O identities:
1. Click Deployment.
The Deployment Portal is displayed.
2. Under Virtual I/O Pools on the left pane, select a virtual I/O pool.
The Virtual I/O Pool Summary page is displayed on the right pane.
3. On the Virtual I/O Pool Summary page, click the Devices with Identities tab.
Devices with assigned or deployed virtual I/O identities are displayed on a grid.
4. Right-click a device on the grid and then click Reclaim Assigned Identities.
The reclaim assigned identities warning message is displayed.
5. If you want to continue reclaiming the assigned virtual I/O identities of the device, click Yes.
The reclaimed virtual I/O identities are returned to the virtual I/O pool.
Setting Up Device Configuration Auto Deployment (Stateless Deployment)
The Setup Auto Deployment task enables you to deploy a configuration template, which includes a set of
configuration attributes, to devices that you will discover at a later time. Deploying a device configuration
template on the devices ensures that the devices are uniformly configured.
Before you create a device configuration auto deployment task, ensure that:
• The deployment file share is configured. For more information, see Configuring the Deployment File
Share.
• The auto deployment setting is enabled and configured. For more information, see Configuring Auto
Deployment Settings.
• The Service Tag or node ID of each target device is available in a .csv file. The Service Tags or node
IDs should be listed under the title ‘ServiceTag’, ‘Service Tag’, or ‘Node ID’ in the .csv file.
NOTE: On devices which have multiple compute nodes (such as the PowerEdge FM120x4), all of
the compute nodes have the same Service Tag. Therefore, the node ID must be used to identify
the specific compute node to use. In the .csv file, you must include the node IDs of the specific
compute nodes that you want to auto deploy.
• You have either created a device configuration template or cloned a sample template.
• You have already created a compute pool. For more information, see Creating a Compute Pool.
• The target devices meet the requirements specified in Device Requirements for Deployment and
Compliance Tasks.
• The OpenManage Essentials — Server Configuration Management license is installed on all target
servers. For more information, see OpenManage Essentials — Server Configuration Management
License.
• On servers with a Mellanox HBA adapter, make sure that the version of adapter firmware installed is
02.34.50.10 X08 or later.
CAUTION: Deploying a configuration template on a device may result in potentially destructive
changes to the device configuration including performance, connectivity, and ability to boot the
device.
164