Dell OpenManage Essentials Version 2.
Release Notes OpenManage Essentials Dell OpenManage Essentials provides a central point of access to monitor and manage systems on a local area network (LAN). By allowing an administrator a comprehensive view across the enterprise, OpenManage Essentials can increase system uptime, reduce repetitive tasks, and prevent interruption in critical business operations. Version 2.0 Release Date: September 2014 Previous Version 1.
– – – – – Deploy 64-bit Dell Update Packages (DUPs). Boot a system from a network-mounted ISO using iDRAC. Availability of new and additional reports. Availability of additional inventory information. Display of warranty pop-up notification for devices. Support for the following devices: – Dell PowerEdge 13th Generation servers. – Dell Networking, Dell Compellent, Dell PowerVault, and Dell EqualLogic devices — support for additional models.
Issue 4: Description In rare cases, inapplicable package may be listed in the compliance report, but the updates are not applied to the target node if the package is not applicable. Issue 5: Description Intel PCI-E driver package information for a server displayed in OpenManage Essentials might be different than the driver package information displayed in SUU. Package name, Component name, Current Version, and Repository Version might be different.
Issue 11: Description When enable downgrades is selected, ensure that you refresh the browser before attempting update/downgrade. Issue 12: Description ActiveX installation is blocked through OpenManage Essentials. Resolution To resolve this issue, run Windows update to download the latest certificate sources. Issue 13: Description A warning message “No Compliant updates found in selected repository” is displayed if you have created a bundle for updating iDRAC using Repository Manager Version 1.4.
Issue 17: Description System Update tasks through iDRAC (out-of-band) do not complete. [30029] Resolution 1. Delete the job queue in iDRAC. 2. Reset the iDRAC. 3. Re-inventory the iDRAC to get the updated inventory. 4. Re-run the System Update tasks. Issue 18: Description OMSA deployment task displays success, even if OMSA is not installed on the target system. [26652] Issue 19: Description OpenManage Essentials only supports system updates on PowerEdge systems.
– "VBScript File", click "Change Program" and select open with "Microsoft Windows Based Script Host". The Windows Scripting Host (WSH) may be incompatible, corrupted, or not installed. By default, WSH is installed during operating system installation. To download the current version of WSH, go to: http://msdn2.microsoft.com/en-us/library/ms950396.
Issue 8: Description If you have an older version of the “OpenManage Essentials installation prerequisite” application installed on your system and the application is not getting upgraded using the "Install all critical prerequisites" button or the specific prerequisite URL, verify the support matrix of the specific application. You may have to uninstall the previous version and then install the newer version recommended by OpenManage Essentials from its installer prerequisites window.
Issue 1: Description After upgrading from OpenManage Essentials version 1.1.1 to 2.0, or 1.1.1 to 1.2 to 1.3 to 2.0, the Custom URL settings page may display multiple custom URLs based on the classification of a device in the device tree. For example, if a custom URL is created for the Servers device group and the servers in your environment are classified under the Servers, RAC, and VMware ESX Servers device groups in the device tree, after upgrading to OpenManage Essentials version 2.
Issue 5: Description While migrating of tasks from ITA 8.9 to OME, all scheduled task that are configured to “Run Once” appears as “Periodic Daily” and is disabled. This issue occurs because ITA task information is incomplete when sent to OME during the migration process. This does not affect any of the existing tasks that OME has configured. Resolution It is recommended that any tasks that are not required must be deleted before starting migration. Issue 6: Description After an upgrade from OME 1.0/1.0.
Issue 10: Description After upgrading from OpenManage Essentials version 1.0.1 to 1.2, while accessing hardware logs for any server, you start seeing one or more exceptions in the console. Resolution 1. Stop “OmeDAService “, “OmeHostService“, “DSM Essentials Task Manager” and “DSM Essentials Network Monitor”, services. 2. Restart the IIS server. 3. Start “OmeDAService “, “OmeHostService“, “DSM Essentials Task Manager” and “DSM Essentials Network Monitor”, services. 4. Launch the OME console.
Discovery and Inventory The processor count in OpenManage Essentials differs for managed systems that contain processors with multiple cores or HyperThreading enabled. The count differs based on whether the managed system is discovered using the CIM or SNMP protocol. Systems discovered using SNMP report physical processors, and the systems discovered using CIM reports logical processors.
Issue 7: Description vFlash information is displayed in the iDRAC Information table in the device inventory even though this information does not belong to the iDRAC information section. [41115] Issue 8: Description The Service Tag may not be displayed correctly in the device inventory for certain PowerVault MD Series storage arrays. [40631] Issue 9: Description OEM devices discovered using the SNMP or WS-Man protocol are classified under Modular Systems in the device tree.
Issue 16: Description If a Dell PowerEdge VRTX chassis is discovered using SNMP protocol and NetBIOS name resolution setting, the instrumentation (NetBIOS) name is not resolved. [27327] Issue 17: Description When a monolithic Dell 11th or 12th Generation PowerEdge server with iDRAC6/7 is discovered using the IPMI protocol only (iDRAC out-of-band discovery), the overall health status of the server is not reported correctly in OpenManage Essentials. This issue occurs due to a known limitation in iDRAC.
Issue 24: Description While performing discovery, if a device is discovered using "host name," and if its IP address changes at a later time, OpenManage Essentials displays two devices after the next discovery cycle. One device displays the old IP address and status as Power Down, while the other displays the new IP address. This problem is likely to affect systems that have DNS-DHCP IP addressing and for which the IP addresses frequently change.
Issue 31: Description If you manually change the host name of the server which has already been discovered in OpenManage Essentials, then duplicate entries appear in the device list corresponding to the IP address of the device whose host name has been changed. The new host name also corresponds to same IP address and the duplicate entry of the earlier host name is not automatically deleted. OpenManage Essentials displays both the new and the old host names.
Issue 38: Description When you create a custom group you have the ability to select a pre-defined device search query or the ability to select individual devices and groups to form your newly created custom group. If you select a device search query as your basis for your custom group content and you subsequently decide to modify the device search query, the results of the modified device search query is not reflected in the custom group.
Issue 43: Description While discovering ESXi 5.0 and ESXi 5.0 U1 using WSMAN you may observe that the discovery task may take about 6 minutes. This issue is due to the enhanced information OME is gathering from the ESXi 5 host and the increased storage and software calls being sent to the OMSA ESXi 5 VIB. Resolution: Do one of the following: Perform discovery and inventory of ESXi 5 when the servers are not busy. Review the “Performance and Scalability” white paper at delltechcenter.
Issue 47: Description When a Dell client device such as Dell OptiPlex, Dell Latitude, or Dell Precision with OMCI 8.x installed is discovered using the WMI protocol, the Agents table in device details page displayed the OMCI version as N/A. [16891] Issue 48: Description When a XenServer is discovered using SSH, the MAC address is not displayed in the same column for the IP address. Issue 49: Description HA Clusters can be discovered using SNMP only.
Issue 4: Description If the intensity of an alert storm increases beyond 5 traps per second, it could take OpenManage Essentials several minutes to process all the alerts. New alerts that are received in the interim are not displayed on the console until all the alerts in the storm are processed. Issue 5: Description Alert Actions: Application Launch alert actions do not show the application in interactive mode if the Microsoft Windows "Interactive Service Detection" service is stopped.
Remote Tasks OpenManage Essentials supports iSM deployment on servers running Community Enterprise Operating System (CentOS). Issue 1: Description On Dell 13th generation of PowerEdge servers running Windows 2012 Datacenter, the operating system is considered as a 32-bit operating system in the iSM deployment task. [49466] Resolution: Discover iDRAC using WS-Man protocol or discover the range with iDRAC SNMP first and then the range with Server WMI.
Issue 7: Description After deployment of iDRAC Service Module (iSM) using a .rpm package, the iSM service (dsm_ism_srvmgrd) is not started. [43476] Resolution: Start the iSM service manually on the server running Linux. Issue 8: Description The Task Execution History of a Power Task (Power cycle, Reboot, or Power off) displays success even though the task is not run on managed nodes that do not have OMSA installed.
The managed system and the management station must be on the same domain or there should be a trust relationship between the two domains. 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.
Issue 19: Description If the "Log On" account of "DSM Essentials Task Manager" or "DSM Essentials Network Monitor" services are 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 tasks fails to execute. Resolution To assign user rights to an account on the local computer: 1. 2. 3. 4. 5. 6.
Issue 24: Description If a remote task is scheduled to run periodically and the system time is changed to a future time, an exception may be displayed in the console. Resolution To resolve this issue, disable all periodic tasks, stop the "DSM Essentials Task Manager" service, and then change the system time. After time is changed, start the "DSM Essentials Task Manager" service and edit each periodic task schedule.
Issue 32: Description Users can select the type of OpenManage Server Administrator packages depending on whether they want to perform an upgrade (major or minor) or clean install of OpenManage Server Administrator using OpenManage Essentials. Use .msi package for clean install /major upgrade/minor upgrade of OpenManage Server Administrator Use .msp package for minor upgrade Use .
Issue 37: Description Creating a Remote Server command task with the command “omreport system alertlog” may take longer than expected to complete. The task may fail to complete if the alert logged on the target system is unusually large. Resolution: Review the alert log on the system to determine if the log can be cleared. Issue 38: Description When the Server Administrator deployment task is performed on more than 20 Linux targets, the task may fail.
Issue 42: Description If OpenManage Essentials is added to a domain, the Generic Command Line task fails when the username is provided as localhost\. Resolution Provide the username in one of the following formats: \ .\ \ Issue 43: Description The Sample - Linux OMSA Uninstall command line task does not support the uninstallation of OMSA version 6.1 or earlier.
Issue 51: 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 success, even if OMSA is not installed on the target system. [30244, 30533] Issue 52: 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.
Security To prevent security issues due to cross frame scripting (XFS) in Internet Explorer, you must disable web frames across different domains: 1. Click Tools Internet Options. 2. Click Security. 3. Under Select a zone to view or change security settings, select Local intranet. 4. Under Security level for this zone, click Custom level. 5. Under Miscellaneous Navigate windows and frames across domains, select either Prompt or Disable.
Issue 7: Description Windows Server 2008 R2 and Windows 7 will not let you add the Administrators and Users group to the OmeUsers and OmeAdministrators groups using computer management. If you want to add the Administrators and Users group, use the command prompt or delete the OME groups to have them reset.
Issue 4: Description If the system locale setting does not match with any of the following, clicking the Help icon in the Troubleshooting Tool displays an error: 1. English (United States) 2. German (Germany) 3. Spanish (Spain) 4. French (France) 5. Japanese (Japan) 6. Chinese (Simplified, PRC) Issue 5: Description OpenManage Essentials does not display the Controller Information, Enclosure Information, and Physical Disk Information for Dell Compellent devices with firmware version 6.4.1.
Issue 12: Description OpenManage Essentials may not display the correct warranty date and time of the device. It displays the warranty date and time based on: The warranty start time. The location of the managed server or the request originator. Issue 13: Description If OpenManage Essentials uses the WMI protocol to discover a server, the RAC information table is not displayed.
Troubleshooting Installation Ensure the latest SQL server service packs are installed on the system. You can run the following command on the command prompt to verify the SQL version. – sqlcmd -Q "print @@version" For typical install, ensure that the current user has “sysAdmin” rights to the SQL Server. For custom install, ensure that the provided authentication credentials have “sysAdmin” rights. Try to use the custom install with different authentication method if typical install fails.
Microsoft Internet Explorer: Issue: Description Unable to open OpenManage Essentials using Internet Explorer. Internet Explorer displays certificate errors. Internet Explorer displays a message to approve the certificate. – Unable to browse the file system to deploy Server Administrator and system update. – Unable to display the Device tree for devices. – Unable to install active components. Resolution: 1. Open OpenManage Essentials on the client server using Internet Explorer. 2.
If you are launching OpenManage Essentials installer from an UNC/shared path, you will not be able to install prerequisites from the “OpenManage Essentials Prerequisites” window. You must copy the installer files to the system or mount the shared folder path to assign a drive to it. A 32-bit system with OpenManage Essentials may display an error message while applying system updates using iDRAC.
If Dell SupportAssist is installed along with OpenManage Essentials, you require 2 GB RAM, Dual core processors in addition to the minimum requirements described earlier. If you are using SQL Server Standard or Enterprise Editions, the maximum SQL Server memory must be configured within SQL Server to prevent it from using the entire system memory. It is recommended that you use a maximum of 4 GB for a 6 GB RAM configuration.
Installation Instructions First-time Installation of OpenManage Essentials version 2.0 See the Dell OpenManage Essentials Version 2.0 User's Guide for instructions on setting up OpenManage Essentials for the first time on a system. Migrating IT Assistant to OpenManage Essentials Direct migration from IT Assistant to OpenManage Essentials version 2.0 is not supported. However, you can migrate IT Assistant to an earlier version of OpenManage Essentials (version 1.
