Release Notes


4. Click "Add User or Group," and, in the "Enter the object names to select box type the user or group
name" to which you want to assign the user right and click "Ok."
5. Click "Ok" again and double-click "Replace a process level token" in the "Details" pane.
6. Click "Add User or Group" and in the "Enter the object names to select box type the user or group
name" to which you want to assign the user right and click "Ok." [239550]
Issue 9:
Description
While creating a "Generic Command Line" Task,“ the Application requires interaction with desktop"
check”box does not work and the executable window is not be visible when Essentials is installed on the
Microsoft Windows Server 2008 R2 system. Task runs the executable in the background. If Windows
requires input, task may hang and you may need to kill the process for the task to continue.
Issue 10:
Description
After successfully running the "Deploy Server Administrator" task on the Linux server, if discovery still
classifies the server as "Unknown" restart the Linux server and run the discovery again. The Linux server
should start showing up under the device tree.
Issue 11:
Description
When trying to run a remote server administrator command against some Linux targets, the "Task
Execution History" pane may show the task as complete even though, when the "Execution Details" pane
is examined, the "Execution Summary" states: "The task is not supported for the target device."
This occurs when the Dell OpenManage Server Administrator on the target devices does not properly
report the information needed for OpenManage Essentials to determine if the Remote Server
Administrator command can run on the system(s). This may mean OMSA is not properly configured, is in
an unknown state, or needs to be upgraded.
Issue 12:
Description
If you are a super-user on a system and you do not have full permissions to this path:
~InstalPath\SysMgt\Essentials\SystemUpdate\Packages, you must give the super-user full access to that
path before running the OM-Deploy task.
Issue 13:
Description
If a remote task is scheduled to run periodically and system time is changed to a future time, an
exception may be seen in the console.
Resolution
To resolve this issue, disable all period tasks, stop the "DSM Essentials Task Manager" service then change
the system time. After time has been changed, start the "DSM Essentials Task Manager" service and edit
each period task schedule.
Issue 14:
Description
If the Remote task is running, it cannot be deleted from "Task Execution History" pane though, it can be
deleted by right-clicking the task from "Task Tree" pane