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]
 When you launch Dell OpenManage Server Administrator for managed systems with Server Administrator agent only
installations, a remote web server is used; you must provide the user name and password of the managed system.
[390431]
 While creating a "Generic Command Line" Task, “Application requires interaction with desktop" checkbox does not work
and 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.
 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.
 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.
 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.
 If a remote task is scheduled to run periodically and system time is changed to the future time, exception may be seen
in the console. 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.
 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
 For Deploy Server Administrator Task, after the task is created, the task status may say 'pending' while the task icon
shows the 'task complete' icon. This means that the Deploy Server Administrator package i.e msi or msp has been
downloaded successfully though the task execution is still pending. Once the task starts execution the 'task complete'
icon will change accordingly.
 For ‘Remote Task’ and ‘System Update’ multiple selection of task is not supported.
 Even though the task is 'Run Now' task or if the tasks that does not have valid schedule associated with it, Right Click on
the task in the left hand side task pane will show the 'Activate Task Schedule' option. Though, activating the schedule
will not do anything as there is no schedule associated with the task.
 If you activate schedule for cloned sample tasks without adding targets, it may display a message for entering
credentials for targets since schedule cannot be activated without valid targets. To avoid this messageadd valid targets
for the cloned task before activating the task schedule