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.1 Release Date: September 2015 Previous Version 2.0.
• Enhancements: – Reorganization of links on the Settings portal. – Grouping of NAS Clusters and HA Clusters device groups in the device tree. – Grouping of reports on the Reports portal. – Availability of response action messages for certain incoming alerts. – Addition of a button that opens the context-sensitive menu in the device tree nodes and other portals that support the tree-view format. – Ability to open the device details and associated application launch points using the contextmenu of an alert.
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.
Installation It is recommended that you install OpenManage Essentials by using either the "Setup.exe" or “Autorun.exe" file. Issue 1: Description An SQL ODBC Driver timeout error is displayed during the installation of OpenManage Essentials. [47759] Resolution This error may be seen invalidly if the host name cannot be resolved on the OpenManage Essentials server. 1. Ping the host name of the OpenManage Essentials server to confirm that name resolution works. 2.
Issue 4: Description The "OpenManage Essentials Install" window displays junk characters in the Japanese language operating system. [39199] Resolution 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.
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 'Run Now' tasks are migrated as disabled.
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. Select all the discovery ranges, right-click and select "Perform Discovery and Inventory Now".
Issue 8: Description While upgrading from OpenManage Essentials version 1.0.1 or 1.1 installed with remote SQL Server 2005 to OpenManage Essentials version 2.1, the following message is displayed: “SQL Server 2005 is detected on the target system. The minimum version of SQL Server supported by Essentials is SQL server 2008.” [31161] Resolution In this case, you must manually migrate the data from SQL Server 2005 to other supported SQL Server versions, and then upgrade to OpenManage Essentials version 2.0.
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 at all times. The communication between the console and the web server is performed utilizing web method calls in a multi-threaded environment.
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 12: Description When a PowerEdge FM120x4 sled is discovered using SNMP+WMI protocol, the Software Inventory Table displays multiple entries for the iDRAC version. [39428] Issue 13: Description If a device is not configured with the system contact details, the "Contact Information" table is not displayed in the device inventory information.
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. [138013] Issue 21: Description In case of SNMP discovery, when the name resolution on an IP address to a host name fails using DNS, Essentials attempts to resolve the name using the MIB2 name query.
Issue 26: Description NIC information is not displayed in the device details screen for Dell/EMC arrays. Resolution 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. The storage processors are redundant and return the same inventory data to OpenManage Essentials.
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. Mount the OpenManage Server Administrator DVD in the Linux server 2. Install 'srvadmin-cm' rpm. 3. Restart the OpenManage Server Administrator services. 4.
Issue 40: Description Discovery and inventory of servers that have virtual network adapters are not displayed in the “NIC Information” table of the server. This occurs when discovering and inventorying Microsoft Windows servers with SNMP, WMI, or both along with Hyper-V role configured with virtual networks adapters. Resolution: OME displays only the IP of the network adapter it was discovered on. If it is a virtual network adapter, it displays “Host NIC Adapter”.
Issue 44: Description When OpenManage Essentials is used to discover and inventory devices of the same category having the same name (for example, servers) in different subnets (for example, my_server), then: • The device tree displays the information of the device that was discovered last. • The device information portal (Details tab) displays the merged data from all devices. Resolution: 1. Ensure that the correct FQDN is defined for each target device. 2.
Issue 49: Description HA Clusters can be discovered using SNMP only. The discovery task that is intended to discover HA Clusters must have SNMP enabled and the associated credentials must be correct for the target devices. In order for the members to be discovered, the IP address of each cluster member must be included in the list of addresses to be discovered by the discovery task. When discovering HA Clusters, the cluster name may replace the name of the active cluster node.
Issue 55: Description The location of a server is not displayed in the Device Summary table when the server is discovered outof-band with either the WS-Man or SNMP protocol. [62819] 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 8: Description If you edited sample alert actions in OpenManage Essentials version 1.0, you must manually clone them before migration. The alert actions will get overwritten with default sample actions. Issue 9: Description The test trap from PowerVault MD 32xx/32xxi is received in OpenManage Essentials system with IP 0.0.0.0. This is an expected behavior in OpenManage Essentials and any other trap listener. Issue 10: Description While upgrading OpenManage Essentials from version 1.0.1 to 1.
Issue 2: Description The iDRAC Service Module deployment task is unsuccessful when parameters are provided for installing selective components. [52132] Resolution: Perform one of the following • Create the iDRAC Service Module deployment task without any parameters, and then run the task. After the deployment is completed, open the iDRAC web interface and enable or disable the components. • Include the MAIN_FEATURE parameter along with the parameter you want to use.
Issue 9: Description If an OMSA deploy task is run on a target using either incorrect parameters or a non-applicable package, the Tasks Execution History displays success, even though the task fails on the target device. Example scenarios: – Installing OMSA Instrumentation on a virtual machine – Upgrading OMSA on a target that does not have OMSA installed – Downgrading OMSA [083482] Issue 10: Description Only the OMSA web server component can be installed on a virtual machine.
"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: "http://msdn.microsoft.com/en-us/library/aa822854(VS.85).
2. 3. 4. 5. 6. In the "Local Security Settings" dialog box, double-click "Local Policies", and then double-click "User Rights Assignment." In the details pane, double-click "Adjust memory quotas for a Process." Click "Add User or Group," and, in the "Enter the object names to select” field, type the user or group name to which you want to assign the user right and click "Ok." Click "Ok" again and double-click "Replace a process level token" in the "Details" pane.
Issue 26: Description For Deploy Server Administrator Task, after the task is created, the task status may display 'pending' while the task icon displays the 'task complete' icon. This means that the Deploy Server Administrator package (msi or msp) has been downloaded successfully though the task execution is still pending. Once the task execution starts the 'task complete' icon will change accordingly. Issue 27: Description For ‘Remote Task’ and ‘System Update’ multiple selection of task is not supported.
Issue 34: Description OpenManage Server Administrator deployment on ESXi server: OMSA cannot be deployed on ESXi server using OpenManage Essentials. For more information, see the “How to setup and configure ESXi 5 for use in OpenManage Essentials” white paper and the “Installing OpenManage Server Administrator on ESXi4 with OpenManage Essentials” video at delltechcenter.com.
Issue 39: Description When creating a Command Line task and selecting Remote Server Administrator command for a Linux target using a command other than omreport and omconfig, the task status indicates the task as completed and displays a green status . This occurs because the Remote Server Administrator command supports omreport and omconfig commands. Resolution: While creating a Remote Server Administrator command, make sure to use only omreport and omconfig commands for the task to return correct data.
Issue 44: Description The 64-bit Dell Remote Access Controller Admin (RACADM) tool does not support the OpenManage Essentials RACADM Command Line Task. [29703] Issue 45: Description The Total Targets in the Task Execution History retains the count of the previously executed targets and also the execution history. [29583] Issue 46: Description OME allows editing and re-run of OMSA deployment tasks.
Issue 53: Description An existing remote task may be replaced by a newly created remote task. [31534] Resolution Restart the DSM Essentials Task Manager service. Issue 54: Description Deploying OpenManage Server Administrator (OMSA) as a sudo user does not work on a system running SLES 11. Resolution Ensure that the directory for the sudo user exists in the /home directory on SLES 11, and then deploy OMSA. If the directory does not exist under /home, create the sudo user using the useradd –m option.
Configuration Management Issue 1: Description When the Deploy Template wizard is run and both deployment and boot-to-network-ISO are requested, if the boot-to-network-ISO task fails to start for some reason, the task will never show that it has completed. The task details window shows the failure and the task completes, but it fails to update its status in the database, so the UI never shows it as completed.
Issue 2: Description "Device Name" is a default field and is present in all reports. [134260] Issue 3: Description The time displayed in the reports generated by Essentials and the "Device Summary/Details" page is in the time zone corresponding to the management station. [75603] Issue 4: Description Software Components report does not display entries for ESXi servers. Issue 5: Description To populate 'Modular enclosure reports' the CMC should have firmware version 4.
Issue 2: Description SupportAssist version 1.3 is not compliant with the Federal Information Processing Standard (FIPS). [40254] Issue 3: Description If the system locale is set to English (India), clicking the Help icon in OpenManage Essentials displays an error. Resolution Copy the help file folder and rename it. For example, copy the EN-US help file folder and rename it as EN-IN.
Issue 9: Description When you launch Dell OpenManage Server Administrator for managed systems with Server Administrator agent only installations, a remote web server is used for which you must provide the user name and password of the managed system. [390431] Issue 10: Description The "Contact Information" for a device may display the firmware version instead of the technical support contact information.
Issue 17: Description After the SNMP feature is installed on Windows Server 2008 R2 or Windows Server 2012, the Windows Event Viewer logs an Error with Source: SNMP and Event ID: 1500, under Windows Logs-> System. This SNMP error is also logged whenever the SNMP Service is started. This SNMP error has been determined not to have any influence on the operation of SNMP or the system, and can be ignored. For more information, see the Microsoft knowledgebase article 200203 at support.microsoft.com.
Launching OpenManage Essentials • • • • When an Internet proxy server is configured on the system, the site must be added to the exception list to bypass the proxy. This should be configured with GPO’s by a domain administrator. If you are using certificates, ensure that you use the domain certificates and those are added in IIS manager for the “DellSystemsEssentials” website.
If the issue persists, there may be an issue with the DNS server resolving the name of the OpenManage Essentials server. To resolve the DNS server issue: 1. Contact your system administrator and ensure that the OpenManage Essentials system name is added to the DNS server. 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.
• • 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.
Database (Microsoft SQL Server – Local or Remote) NOTE: Only case-insensitive instance of SQL Server is supported. SQL Server 2012 SP1 Express is installed with OpenManage Essentials version 2.1. NOTE: For large deployments, you must use SQL Standard.
Installation Instructions First-time Installation of OpenManage Essentials version 2.1: See the Dell OpenManage Essentials Version 2.1 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.1 is not supported. However, you can migrate IT Assistant to an earlier version of OpenManage Essentials (version 1.
1. Go to dell.com/support/manuals. 2. In the Tell us about your Dell system section, under No, select Choose from a list of all Dell products and click Continue. 3. In the Select your product type section, click Software, Monitors, Electronics & Peripherals. 4. In the Choose your Dell Software, Monitors, Electronics & Peripherals section, click Software. 5.
