Release Notes

.\<Username>

\<Username>

Issue 38:

Description: The Sample — Linux OMSA Uninstall command line task does not support the uninstallation of OMSA version 6.1 or

earlier. [30243]

Issue 39:

Description: The Total Targets in the Task Execution History retains the count of the previously executed targets and also the

execution history. [29583]

Issue 40:

Description: OpenManage Essentials allows editing and re-run of OMSA deployment tasks. It is recommended that the editing and

re-run options are selected only for tasks that have nished execution. [29525]

Issue 41:

Description: After the successful execution of the Sample — Windows OMSA Uninstall command line task, no details are displayed

in the Task Execution History. [30535]

Issue 42:

Description: The Schedule View calendar allows you to select a date prior to the current date for launching the task creation wizard.

OpenManage Essentials validates the date only during the task creation, and displays an error message if the task is scheduled on a

date prior to the current date. [27551]

Issue 43:

Description: The Sample — Windows OMSA Uninstall and Sample — Linux OMSA Uninstall command line tasks do not verify if

OMSA is installed on the target. After execution of the task, the Task Status displays Successful, even if OMSA is not installed on

the target system. [30244, 30533]

Issue 44:

Description: When using a single OMSA deploy task on multiple targets, if one or more task targets are not updated, OpenManage

Essentials displays The task was cancelled for the target device. The Task Execution History displays the Stop

status.

Resolution: Re-run the task:

1. In the Task Execution History, right-click the task and click Edit.

2. Deselect all the targets that were successfully updated.

3. Provide the credentials and click Finish. [16585]

Issue 45:

Description: An existing remote task may be replaced by a newly created remote task. [31534]

Resolution: Restart the DSM Essentials Task Manager service.

Issue 46:

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

insucient permission error. [61746]

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