Users Guide

have been discovered. If a target device is discovered, the device conguration is automatically deployed to the target device. You
can also modify the recurrence of the Setup Auto Deployment task based on your preference.
NOTE: If you create auto deployment tasks in OpenManage Essentials version 2.0, 2.0.1 or 2.1 and then upgrade to
version 2.2, 2.3 or 2.4, the auto deployment tasks do not run successfully. In this scenario, it is recommended that you
recreate the auto deployment tasks after the upgrade to version 2.2, 2.3 or 2.4.
NOTE: Auto Deployment feature is not applicable for IOA templates.
Related links
Conguring Auto Deployment Settings
Setting up device conguration auto deployment—Bare-metal deployment
Managing Auto Deployment Credentials
Adding a Discovery Range for Auto Deployment
Conguring Auto Deployment Settings
The Auto Deployment Settings allows you to perform the following:
• Enable or disable the device conguration auto deployment.
• Set the recurrence of the device conguration auto deployment task.
To congure the auto deployment settings:
1. Click Settings → Deployment Settings.
The Deployment Settings page is displayed.
2. Select or clear Enable auto deployment for recently discovered devices to enable or disable auto deployment of device
conguration.
3. Edit the Run auto deployment every xx Minutes eld based on your preference.
4. Click Apply.
Related links
Auto deploying device congurations
Setting up device conguration auto deployment—Bare-metal deployment
The Setup Auto Deployment task enables you to deploy a conguration template, which includes a set of conguration attributes, to
devices that you will discover at a later time. Deploying a device conguration template on the devices ensures that the devices are
uniformly congured.
Before you create a device conguration auto deployment task, ensure that:
• The deployment le share is congured. For more information, see Conguring the Deployment File Share.
• The auto deployment setting is enabled and congured. For more information, see Conguring Auto Deployment Settings.
• The Service Tag or node ID of each target device is available in a .csv le. The Service Tags or node IDs should be listed under
the title ‘ServiceTag’, ‘Service Tag’, or ‘Node ID’ in the .csv le.
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 specic compute node to use. In
the .csv le, you must include the node IDs of the specic compute nodes that you want to auto deploy.
• You have either created a device conguration template or cloned a sample template.
• The target devices meet the requirements specied in Device Requirements for Deployment and Compliance Tasks.
• The Server Conguration Management license is installed on all target servers. For more information, see OpenManage
Essentials — Server Conguration Management License.
CAUTION: Deploying a conguration template on a device may result in potentially destructive changes to the device
conguration including performance, connectivity, and ability to boot the device.
136