White Papers

Executive summary
58 Managing Modular Infrastructure by using OpenManage Essentials (OME)
20.4 Troubleshoot the Auto-deploying templates
Whenever the Deploy Configuration to Undiscovered Devices task is executed, it looks for Service Tags in the
Auto Deployment list. The following situations may be encountered:
 There are no Service Tags in the Auto Deployment list. In this case, the task exits, and no entry is
created in the task execution history grid.
 The task finds one or more Service Tags in the Auto Deployment list for devices that have not been
discovered by OME yet. In this case, a task execution history entry is created and it indicates why the
Service Tag was not processed.
 The task finds one or more Service Tags in the Auto Deployment list for devices that have been
discovered by OME. It creates tasks named Deploy Configuration to Undiscovered Devices–Task–
timestamp to deploy to those devices. In this case, an execution history entry is created and the entry
specifies which Service Tags were processed for deployment.
 If an error occurs in a task created for auto deployment to a device, to troubleshoot the error, see
Troubleshoot the File Share issues in managing Modular Infrastructure.
20.5 Troubleshoot the configuration compliance in OpenManage
Essentials
To troubleshoot the configuration compliance:
 If a device is not shown in the pie chart, make sure it meets the device configuration requirements.
For details, see Target Device Requirements.
 If a device has acquired the license recently and shows as unlicensed, refresh the inventory of the
device by right-clicking on the device in the device view under ManageDevices and select Refresh
Inventory. After the inventory is run, the device state should no longer be ‘Not Licensed’.
 If you believe that the state of a device is incorrect, refresh the configuration inventory of the device
(right-click the device compliance entry and select Run Inventory Now’.
 If the existing template cannot be upgraded, perform discovery and inventory on the CMC device
from which the template was created.