White Papers

Set up Auto-Deploy Configuration
11 Auto-Deploy Provisioning on Servers or Chassis Using DellEMC OpenManage Enterprise 3.2 | Technical white
paper
The Auto-deploy configuration remains in a “Not-Run” state until the service tags, which were entered, are
discovered and the Onboarding task is completed.
Once the Onboarding task is completed, the Deploy task is triggered and a job is created. The details of the
job are displayed in the Jobs page (Monitor > Jobs).
After the completion of the Deploy task, the devices will be listed in both the static group as well as the default
device group if static group was selected initially at the time of the auto-deploy template creation. Otherwise, if
static group was not assigned, then the devices are listed in the default device group.
If Boot to Network ISO is enabled, target will boot to ISO file.
After the auto-deployment task is completed on the targets, the status of auto-deploy configuration will be
displayed as completed.
• Note: If a device is discovered again in console, the auto-deployment task will not be triggered again as
the status of the configuration is completed.
• Note: If the deployment of the auto-deploy configurations with multiple service tags fails on any one
device, the overall status of the task in Jobs portal will be displayed as “completed with errors” and in the
Auto-Deploy page the status of each service tag configuration will be displayed as “completed with error”.
The status of each configuration rolls up on the overall status of the auto deployment task.
• Note: If the Onboarding task fails, then auto-deploy task will be triggered and fail with “Device not
onboarded” message. The status of auto deploy configuration will display as failed, and the device will be
listed in static group and default device group. If the configuration is not associated to static group, then
the device will be listed under default device group.