Release Notes

Description: Deploying OpenManage Server Administrator (OMSA) as a sudo user does not work on a system running SLES 11.

Resolution: Ensure that the directory for the sudo user exists in the /home directory on SLES 11, and then deploy OMSA. If the

directory does not exist under /home, create the sudo user using the useradd –m option. The –m option ensures that the

directory for the sudo user is created in /home directory.

Issue 47:

Description: If a device group is selected as a task target, the task runs on all devices in the group, including devices that were

added to the group after the task creation. [55466]

Resolution: Before the task runs, edit the task and ensure that the task target only includes the required devices.

Issue 48:

Description: While accessing OpenManage Essentials remotely as an OMESiteAdministrator, creating a remote task displays an

insufficient permission error. [61746]

Resolution: Close the web browser and open OpenManage Essentials again.

Issue 49:

Description: The Task Target page does not display all device groups for the OMESiteAdministrator. [61821]

Issue 50:

Description: A cloned task may not display all the task targets immediately after the task is cloned. [55462]

Resolution: Wait until the cloned task is displayed in both the Remote Tasks tree and the Remote Tasks grid, and then verify

the task targets.

Configuration management

Issue 1:

Description: The device configuration Inventory and Compliance tabs in the Devices Portal display inventory and

compliance information only after the corresponding tab is manually refreshed. [48567]

Issue 2:

Description: For device configuration inventory tasks, the Task Execution History displays the user who ran the task as

System. [48738]

Issue 3:

Description: If a device on which a configuration template was deployed, is deleted and then rediscovered, the last template

deployed on the device is not displayed in the Repurpose and Bare Metal Devices tab.

Issue 4:

Description: Auto deployment tasks created in OpenManage Essentials version 2.0 do not run successfully after upgrade to

version 2.0.1 or version 2.2. [61955]

Resolution: Recreate the auto deployment task after the upgrade.

Issue 5:

Description: When CMC deployment fails on the target chassis (firmware M1000e 5.x, VRTX 2.x, FX2/FX2s 1.x) due to invalid

or unsupported values in the template attributes, the status is displayed as "Unknown" instead of "Failed" in the Task

Execution History window under Details tab. [75135]

Resolution: See the description in task details to determine the issue.

Issue 6:

Description: If the deployment template is captured from a server with configurations like DELL PERC S130/S140 with Single

Disk based volumes, then the deployment of those templates on the target devices fail with “RAID Level not supported” error.

[77419]

Resolution: The deployment of single disk-based volumes is not supported by iDRAC server configuration feature. After

deploying the template, manually configure the single disk-based volumes using PERC configuration utility.

Issue 7:

Description: When the create template task is modified, junk characters are displayed in the template name which has non-

English characters. [79180]