Dell OpenManage Essentials Version 2.2 Release Notes This document describes the new features, enhancements, and known issues in Dell OpenManage Essentials Version 2.2. Release type and definition Dell OpenManage Essentials Dell OpenManage Essentials provides a central point of access to monitor and manage systems on a local area network (LAN).
What is Supported? For a complete list of supported devices, operating systems, and web browsers, see the Dell OpenManage Essentials Version 2.2 Support Matrix at delltechcenter.com/ome or dell.com/ OpenManageManuals. What’s New • Ability to create a device configuration template from an IOA. • Ability to deploy a device configuration template on an IOA. • Display of VLAN configuration inventory information of the IOAs within a chassis. • Ability to assign VLAN IDs to the IOAs within a chassis.
Issue 1: Description: When performing the system update task as a sudo user on a target that does not have OMSA installed, the Scheduled F/W & Driver Inventory task fails with the sudo requires password error. [48587] Resolution: Edit the sudoers file using the visudo command, and add the following: • For target systems running a 32-bit operating system: – Cmnd_Alias OMEUPDATE = /bin/tar,/opt/dell/srvadmin/bin/omexec, /tmp/ LinuxPreInstallPackage/runbada,/tmp/LinuxPreInstallPackage/omexec, /tmp/ invcol.
• The TPM feature is set (using BIOS) to ON with Preboot Measurement. For information about TPM security settings, see the Dell OpenManage Server Administrator Online Help or the Dell OpenManage Server Administrator User's Guide available at dell.com/OpenManageManuals and on the appropriate media supplied by Dell. For software updates for BIOS to function, perform the following steps: 1. Disable the Microsoft Windows BitLocker Drive Encryption feature. For information on disabling this feature.
Description: While performing in-band updates to the Broadcom NIC firmware on ESX servers, you may intermittently notice that the task status displays failed, even though the update was performed successfully. This is because of an incorrect status message that is provided by the update package during execution. Resolution: 1. Reboot the target and perform inventory to verify if the update is successful. 2. Re-apply the update if required.
message is displayed: This package does not support running on 32-bit operating systems. [59158] Issue 21: Description: System update task to upgrade Emulex LightPuse HBA — Storport Miniport driver (10 GbE Network Adapter) on Windows Server 2008 R2 or 2012 results in a time-out error.
3. If name resolution is successful, follow the instructions in the Troubleshooting: Timeout Expired knowledge base article at technet.microsoft.com. Issue 2: Description: In the Prerequisite Checker screen, the following message may be displayed: An error occurred while attempting to execute a Visual Basic Script. Please confirm that Visual Basic files are installed correctly. Resolution: • In Internet Explorer, make sure that the Active Scripting and Scripting of Java applets options are enabled. a.
1. Click Start → Control Panel → Region and Language. 2. In the Format drop-down list, select Japanese (Japan). 3. Click Apply. 4. Try installing OpenManage Essentials again. Issue 5: Description: After installing OpenManage Essentials, if you reinstall the database application (which is used by OpenManage Essentials) the OpenManage Essentials database is detached from the database application.
Migration The following Tasks will not get migrated from ITA: • • • • • • • • Server Software Update Client Software Update IPMI Command Line Power Control Device (via ASF) Performance Management Import Dell Catalog Server Administrator Deployment for Windows Server Administrator Deployment for Linux • While migrating tasks from IT Assistant to OpenManage Essentials, all the Run Now tasks are migrated as disabled.
Description: After upgrade to OpenManage Essentials version 2.2: • • The devices are not classified correctly. The devices that were reported in the Non-Compliant Systems tab are displayed in the Compliant Systems tab. [40445] Resolution: After the upgrade, you must initiate the discovery and inventory for all ranges. 1. Click Manage → Discovery and Inventory. 2. Under Discovery Ranges, click All Ranges. The Discovery Range Summary is displayed. 3.
Resolution: Provide the user account in the discovery wizard with IPMI admin privileges on the RAC and re-run discovery to get the health status. Issue 8: Description: Customizations to the Devices portal layout are deleted on upgrading to OpenManage Essentials 2.2. [18342] Issue 9: Description: While upgrading from OpenManage Essentials version 1.0.1 or 1.1 installed with remote SQL Server 2005 to OpenManage Essentials version 2.
Description: OpenManage Essentials launches in Internet Explorer even if any other browser is set as the default browser. [35491] Issue 3: Description: OpenManage Essentials does not launch or displays an exception when the number of connections to the OpenManage Essentials website is limited in IIS. Resolution: The OpenManage Essentials console requires constant communication with the web server to ensure that the data is up-to-date always.
To workaround this issue, do not select the group node for discovery, but rather just the devices within that group. Issue 3: Description: An EqualLogic storage array is displayed even after excluding the EqualLogic discovery range. Resolution: If the EqualLogic Group Management, EqualLogic Storage Group, and all the EqualLogic member IP addresses are included in a single discovery range configuration, excluding that range will exclude the entire group in the device tree.
Issue 11: Description: When a PowerEdge FM120x4 sled is discovered in-band using SSH protocol, the Embedded Device Information table is not displayed in the device inventory. [39312] Issue 12: Description: When a PowerEdge FM120x4 sled is discovered using SNMP+WMI protocol, the Software Inventory Table displays multiple entries for the iDRAC version.
Issue 19: Description: Dell Fibre Channel switches (modular) are classified under Network Devices → Switches and not under Modular Systems in the device tree. [36990] Issue 20: Description: When the name resolution on an IP address to a host name fails using DNS, OpenManage Essentials attempts to resolve the name using the NetBIOS name query. This action may cause the device to appear in Essentials with the NetBIOS name even if it does not have a DNS entry.
keeping in mind the devices (and protocols supported by agents running on those devices) that you are going to manage. [153729] Issue 26: Description: NIC information is not displayed in the device details screen for Dell/EMC arrays. Use Navisphere Manager to view these details. Issue 27: Description: If you are managing a Dell/EMC storage array, enter the IP address for only one of the storage processors (that is, either SPA or SPB, and not both) in the discovery range.
Supply Information section. To display the correct information, discover the server using either SNMP, or both SNMP and CIM protocols. [300080] Issue 34: Description: Even after performing inventory on the discovered Linux servers N number of times, the Linux servers are still listed under Non-Inventoried systems. Resolution: To resolve this issue perform the following steps: For Red Hat Enterprise Linux 5.5, SUSE Linux Enterprise Server 10, SUSE Linux Enterprise Server 11 1.
Description: When a Dell PowerConnect 8100 series switch is discovered, the MAC address associated with the management IP in the NIC Information table will be displayed as N/A in OpenManage Essentials. Issue 40: Description: Discovery and Inventory of servers that have virtual network adapters are not displayed in the NIC Information table of the server.
Resolution: 1. Ensure that the correct FQDN is defined for each target device. 2. Set the UI discovery to use the DNS for name resolution. 3. Go to C:\Program Files (x86)\Dell\SysMgt\Essentials\configuration or the path where OpenManage Essentials is installed. 4. Open the dconfig.ini file, and add the following under [DISCOVERY_PARAM]: NAME_CORRELATION_MODE=value The possible values are: • • • 0 = Default (OpenManage Essentials works as described in this issue).
If the cluster IP address is the only IP address in the discovery task that is related to the HA Cluster, the currently active cluster node will be discovered and its name will be the same as that of the cluster itself. This results in the cluster name appearing in several places under the All Devices organizational view. Another option which helps with cluster discovery is setting the name resolution to NetBIOS instead of DNS names and running the discovery.
Resolution: The location of the server is displayed in the Device Summary table only if the server has OMSA installed and is discovered in-band. If the server is discovered out-of-band with either the WS-Man or SNMP protocol, the device location is displayed only in the Data Center Location Information table. Issue 57: Description: The Service Tag is not displayed for the PowerEdge FN IOAs that were manufactured prior to February 1, 2016.
Description: The Service Tag of a PowerVault MD 38xx Series storage array displayed in OpenManage Essentials does not match with the Service Tag displayed in PowerVault Modular Disk Storage Manager. [64059] Issue 66: Description: If the mode of the IOAs in a chassis is changed from Standalone or VLT to PMUX, the IOAs of a chassis are not discovered when using the Chassis (CMC) Discovery — All Components filter.
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. To see the applications, you have to start the service. Issue 6: Description: Alerts are not received when the SNMP Trap service is stopped and started. To resolve the issue, restart the DSM Essentials Network Monitor service.
Description: For EqualLogic storage arrays, the Alert Details window displays an incorrect alert description. [62474] Remote Tasks • OpenManage Essentials supports iSM deployment on servers running Community Enterprise Operating System (CentOS). Issue 1: Description: The task targets tree is not expandable when iDRAC Service Module Deployment task is opened in view mode. [51128] Resolution: Open the corresponding task in edit mode to view the selected targets.
Install Dependency section in the iDRAC Service Module Version 1.0 Installation Guide at dell.com/ support/manuals.[47177] 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 14: Description: Remote Server Administrator command line task may not respond for Server Administrator running on Microsoft Windows Server 2008 and Microsoft Windows Server 2008 R2. To enable the successful functioning of remote Server Administrator CLI and software updates/deploy features, ensure the following (applicable to Microsoft Windows only): • The managed system and the management station must be on the same domain or there should be a trust relationship between the two domains.
Issue 18: 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.
Administrator command can run on the system(s). This may mean that OMSA is not properly configured, is in an unknown state, or needs to be upgraded. Issue 23: 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.
Description: Sometimes when editing the remote task the target selection is not seen. To see the targets, cancel or close the edit window and re-edit the task to see the target selection. 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 .
Description: Creating a Remote Server command task with the command omreport system alertlog may take longer than expected to complete. This occurs if the alert logged on the target system is unusually large, the task may fail to complete. Resolution: Review the alert log on the system to determine if the log can be cleared. Issue 38: Description: When Server Administrator deployment task is performed on more than 20 Linux targets, the task may fail.
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. [30243] Issue 44: Description: The 64-bit Dell Remote Access Controller Admin (RACADM) tool does not support the OpenManage Essentials RACADM Command Line Task.
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 Successful, 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.
Description: Clicking the Browse button available in a task wizard displays a JavaScript error. Resolution: Clear the web browser cache and click Browse again. Issue 59: Description: A cloned task may not display all the task targets immediately after the task is cloned. [55462] Resolution: Wait until the cloned task is displayed in both the Remote Tasks tree and the Remote Tasks grid, and then verify the task targets.
Issue 7: Description: Compute Pool tree view may display blank nodes when CMCs or IOAs are added to baremetal pool. [69829] Resolution: Collapse and then expand the root node of the Compute Pool tree or refresh the OpenManage Essentials user interface. 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.
Command to list your local groups: net localgroup Command to add Users to OmeUsers: net localgroup "OmeUsers" Users /add Command to add Administrators to OmeAdministrators: net localgroup "OmeAdministrators" Administrators /add Command Line Interface (CLI) Issue 1: Description: OpenManage Essentials CLI functionality will not work when a non-default Console Launch port is used for installing OpenManage Essentials.
• • Japanese (Japan) 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. However, this issue is not observed for Compellent devices with firmware version 6.3.
Description: The warranty information (including expired and renewed) displayed in OpenManage Essentials for a particular Service Tag, may not match with the warranty record displayed at support.dell.com. The service level code and model name of a warranty record displayed at support.dell.com may not exactly match with the OpenManage Essentials warranty report. [44410] Issue 14: Description: If OpenManage Essentials uses the WMI protocol to discover a server, the RAC information table is not displayed.
Manage MIBs The following are some of the MIB(s) that have been verified. • 38 ALCATEL-IND1-PORT-MIRRORING-MONITORING-MIB, rmon-mib, rfc1213, Accordmibs,Entity-mib, If-mib, ripv2-mib, snmpv2-mib, ADTRAN-DS1-MIB, ADTRAN-MIB, AS-2000, WaveLAN-MIB, AILUXCONNECT-MIB, AISPY-MIB, HHMSAGENT-MIB, HHMSSMALLMIB, ALCATEL-IND1-CHASSIS-MIB, BGP4-MIB (IETF_BGP4.
PACKETEER-MIB (PACKETEER-MIB.mib), PACKETEER-RTM-MIB, ADSL-LINE-EXT-MIB, ADSL-LINE-MIB, DIAGNOSTICS-MIB, PBC-CMTS-MIB, PBC-ENT-MIB, PBC-GENERIC-MIB, PBC-KODIAK-M-G10-MIB, PENRIL-MIB, PERIPHONICS, PERIPHONICS-VRU-NETWORK-MIB, PICTURETEL-VCS-MIB, PICTURETEL-VCS-CONFIG-MIB, PICTURETEL-VCS-H320-MIB, PICTURETEL-VCS-H323-MIB, PICTURETEL-VCS-SYSSTAT-MIB, LSF-SNMP-MIB (LSF-AGENTMIB) The following MIB(s) that can be parsed to view the details, but cannot be imported.
• SONICWALL-FIREWALL-TRAP-MIB • WLSR-AP-MIB, WLSX-SWITCH-MIB, WLSX-TRAP-MIB, WLSX-WLAN-MIB • LLDP-MIB, LLDP-V2-MIB, LLDP-EXT-MED-MIB, DVMRP-STD-MIB, MAU-MIB, DISMANTRACEROUTE-MIB, HC-ALARM-MIB, AI-AP-MIB Issue 1: Description: The following MIB(s) may not be parsed by the MIB Import Utility. You can verify if these MIB(s) compile properly with any standard MIB compiler tool.
Example: Import a device A MIB having some traps definitions. After importing, assume OpenManage Essentials receives 10 traps from device A. If you remove the imported MIB from OpenManage Essentials, the 10 received traps in OpenManage Essentials are also removed. Issue 6: Description: Search Unknown Traps lists traps even after the trap is added using MIB Import Utility, as previous events received are still categorized in OpenManage Essentials as unknown.
Services • Ensure that the OpenManage Essentials database is present and accessible by running the following command on the database server command prompt. – sqlcmd -E -d OMEssentials -Q sqlcmd -E -d OMEssentials -Q "select * from sys.databases where name = 'OMEssentials'" • If the above command works, enable the logs using the dconfig.ini file and collect the logs from the specified folder location.
2. Edit your host file to resolve the IP of the OpenManage Essentials server. The host file is located at %windir%\System32\drivers\etc\hosts. 3. Add the IP of the OpenManage Essentials server to the Local intranet sites in Internet Explorer. NOTE: You cannot remove the certificate errors unless you use the fully qualified name of the OpenManage Essentials server.
• On a domain controller only domain administrators are automatically added to OmeAdministrators and OmeUsers roles. Enterprise administrators must be manually added to the OpenManage Essentials roles. [31506] • When running OpenManage Essentials using the Google Chrome browser, even if Preferences → Console Settings → Security Settings (ActiveX) are enabled in OpenManage Essentials: – The MIB Import Utility cannot be launched from the Extensions tab.
NOTE: The recommended minimum hardware requirements for OpenManage Essentials on a domain controller are 8 GB RAM, 8 cores processor, and a remote database. NOTE: When accessing the OpenManage Essentials console via a remote browser, you will experience better performance in the console user interface by using a (remote) system that has a well-equipped processor. For small and medium configurations, a system with an Intel multi-core processor or equivalent is typically sufficient.
NOTE: • It is recommended that you install the latest SQL Server Service pack. • OpenManage Essentials supports 32 bit and 64 bit SQL Server. It is recommended that you install the 64 bit SQL Server. Other Minimum Requirement (Many of these can be installed from the prerequisites window) • Internet Explorer 9, 10, or 11; Mozilla Firefox 38 or 39 • IIS 7.x/8 • Microsoft SilverLight 5.1.41212.0 • Microsoft .NET Framework 4.5.2 • Microsoft ASP.
Uninstallation NOTE: Before uninstalling OpenManage Essentials, you must uninstall Dell OpenManage Essentials MIB Import Utility and Dell SupportAssist (if installed). 1. Click Start → Control Panel → Programs and Features. 2. In Uninstall or change a program, select Dell OpenManage Essentials and click Uninstall. 3. In the message Are you sure you want to uninstall OpenManage Essentials?, click Yes. 4. In the message Uninstalling OpenManage Essentials removes the OpenManage Essentials database.
© 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.