Release Notes

● If you have a Windows Firewall configured on the management station or the managed system, make the following
configuration changes to enable remote Server Administrator CLI and software updates to work successfully.
Management Station:
1. Open TCP port 135.
2. Add the application omremote.exe (located in Essentials\bin) to the Firewall exception list.
Managed System:
● If you have the Windows firewall configured, enable remote administration by running the following command in the
command prompt:
○ "netsh firewall set service RemoteAdmin"
For more information on connecting through the Windows firewall, see Microsoft's MSDN website for Platform SDK:
Windows Management Instrumentation (Connecting through Windows Firewall) at:
● http://msdn.microsoft.com/en-us/library/aa389286(VS.85).aspx
● http://support.microsoft.com/kb/875605
For Windows Server 2008 onwards, see the following link: http://msdn.microsoft.com/en-us/library/
aa822854(VS.85).aspx. [312918]
Issue 10:
Description: When creating or updating a task, the stamp for the creation or update time is that of the OpenManage Essentials
UI. The Last Run Time displayed on the summary report, however, is the time of the Essentials Services system. If there is a
significant variation in the UI and Services system time, it is possible that a scheduled task may not execute or show that it was
executed before it was created. [137997]
Issue 11:
Description: If you set the task start or end time to a time in Daylight Saving Time (DST) shift period, OpenManage Essentials
changes the task start or end time to the closest valid time. [165393]
Resolution: A workaround to eliminate the changing of start or end time is to set a valid start/end time.
Issue 12:
Description: By default, root login through SSH is not enabled on VMware ESX Servers. As a result, all the OpenManage
Essentials tasks that use the root account fail. To enable the SSH root login on the ESX Server, set the option
PermitRootLogin=YES in /etc/ssh/sshd_conf file. [174023]
Issue 13:
Description: The Server Administrator Deployment task requires dependent components (example libc++) to be installed on
the target systems running the Linux operating system. If these components are not installed, the task fails with the following
error message:
● omexec must be installed on the remote node for the task. See the help and ensure that
the remote node requirements are met before executing the task.
Issue 14:
Description: If the Log On account of DSM Essentials Task Manager or DSM Essentials Network Monitor services is
changed, the following user rights must be assigned for the Log On account:
● Adjust memory quotas for a process
● Replace a process level token
If the Log On account is missing the above user rights, the Essentials task fails to execute.
Resolution: To assign user rights to an account on the local computer:
1. From the Start menu, point to Administrative Tools and then click Local Security Policy.
2. In the Local Security Settings dialog box, double-click Local Policies, and then double-click User Rights Assignment.
3. In the details pane, double-click Adjust memory quotas for a Process.
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]
NOTE:
Changing Log On accounts of DA and Host Services is not supported. If changed, it will lead to errors. For these
services, use Local System account for Log On.
18