Dell OpenManage Essentials Version 1.
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 1.3 Release Date: February 2014 Previous Version 1.
Ability to display alert notification pop-ups in the console. Support for enhanced error messaging for system update tasks. Availability of enhanced inventory information for Dell Compellent devices. Availability of Remaining Rated Write Endurance status for SAS and SATA SSD attached to a PowerEdge RAID Controller (PERC) 8. Support for the installation of OpenManage Essentials in 64-bit operating systems only.
Issue 5: Description If after successfully running the software update task on Windows HyperV server, the server is still shown under "Non-Compliant" tab, wait for 30-45 minutes. The server is displayed under the "Compliant" Tab. Issue 6: Description While updating PERC using OpenManage Essentials, two firmware packages may show up for PERC 4e/Di RAID Controller if you use the 6.5 SUU DVD. You can use either package to update your PERC.
Issue 13: Description System update task does not work if the security group policy called Admin Approval Mode for the builtin Administrator account is enabled on the system running OpenManage Essentials. [30884] Resolution OpenManage Essentials cannot elevate permissions to copy and execute updates when Admin Approval Mode is enabled on the OpenManage Essentials system. Use the default settings to execute the System Update task.
– 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.
Examples: - SilverLight - Microsoft SQL Server Issue 8: Description The OpenManage Essentials installation may stop after a system reboot. Cause This issue occurs because the files are extracted to the %temp% directory and the files get deleted after a system reboot. Resolution To resolve this issue, re-launch the OpenManage Essentials executable file again.
Issue 2: Description After upgrade to OpenManage Essentials version 1.3: – 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 7: Description Customizations to the Devices portal layout are deleted on upgrading to OpenManage Essentials 1.3. [18342] 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 1.
Issue 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 at all times.
Issue 4: Description When a PowerEdge FX2s chassis is discovered using WS-Man protocol, the host name of the corresponding mapped sled is not displayed in the PCIe Slot Information table in the device inventory. [37351] Issue 5: 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.
Issue 12: Description When only the EqualLogic storage array in a PowerEdge chassis is discovered, the EqualLogic storage array is not classified under Modular Systems-> PowerEdge chassis-> Storage in the device tree. [38654] Resolution: Make sure that the PowerEdge chassis is also discovered. Issue 13: Description Dell Fibre Channel switches (modular) are classified under Network Devices -> Switches and not under Modular Systems in the device tree.
Issue 19: Description The choice of protocols specified for discovering and managing the devices can result in varying levels of manageability. For instance, if you choose to manage devices in your network using only WMI, the devices with only SNMP agent (example DRAC) are classified under the "Unknown" group and consequently, you may not get the Application Launch (example RAC console) functionality for the device.
Issue 26: Description If a server is discovered using both SNMP and IPMI (in-band and out-of-band IP addresses respectively), Essentials will correlate the two and display a single device under the "Servers" group in the devices view. If IPMI is then disabled, a new device would appear under the "Unknown" group, corresponding to the out-of-band interface. The device details under the Servers group continue to display the out-of-band IP address as well.
Issue 32: 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 37: 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 41: Description When Dell EqualLogic devices are discovered using the group IP, not all NICs of the members are displayed in the Details tab. Alerts from all members, forwarded by the group lead, are not displayed either on the Device Alerts tab or the Alerts portal. [049415] Issue 42: Description When a Dell client device such as Dell OptiPlex, Dell Latitude, or Dell Precision with OM CI 8.
Issue 6: Description For large number of alerts, two auto refreshes are required to show the total alerts and count on the home page. If the alert count is large, the first refresh fetches and shows only a subset of alerts. The second refresh displays the entire list. Issue 7: 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 3: Description Only the OMSA web server component can be installed on a virtual machine. If you deploy the server administrator component using the OMSA Deploy Task on a virtual machine, the Task Status displays success. However, OMSA is not installed on the virtual machine. [26652] Issue 4: Description The Dell OpenManage Server Administrator Managed Node (MSP file) supports minor upgrades only (from version n to version n+1).
Issue 8: 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.
Issue 13: Description While creating a "Generic Command Line" Task, the “Application requires interaction with desktop" check box does not work and the executable window is not visible when Essentials is installed on the Microsoft Windows Server 2008 R2 system. The task runs the executable in the background. If Windows requires input, the task may hang and you may need to kill the process for the task to continue.
Issue 21: Description Even though the task is 'Run Now' task or if the tasks that does not have valid schedule associated with it, right-clicking the task in the left 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.
Issue 28: Description To Install OpenManage Server Administrator on a 64-bit Linux system, install the following 32-bit rpms and their dependent packages before running OpenManage Server Administrator Deploy task from OpenManage Essentials: compat-libstdc++-33.i686 libxml2.i686 pam.i686 glibc.i686 zlib.i686 libgcc.i686 Issue 29: Description While creating an OpenManage Server Administrator update deployment task; the task may remain in “In-progress” state for 6 hours.
Issue 33: Description If you select an MSP package to update major versions of OpenManage Server Administrator, (for example, version 6.x to version 7.x) the task displays the status as successful and the details indicate that the software update is complete. However you can notice that the update was never completed. This occurs because the MSP is only supported while updating minor versions. For example, 6.3 to 6.5 or 7.0 to 7.1.
Issue 40: Description Invalid parameters provided for RACADM command line tools are not validated by OpenManage Essentials, and the tasks status displays that the command was executed successfully as part of the task. [30539] Issue 41: Description After the successful execution of the Sample - Windows OMSA Uninstall command line task, no details are displayed in the Task Execution History.
Issue 47: 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. The –m option ensures that the directory for the sudo user is created in the /home directory.
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. If you want to use the CLI functionality, make sure that the default console launch port 2607 is used during installation. Issue 2: Description OpenManage Essentials CLI does not support deleting nested custom groups.
Issue 6: Description You may not get appropriate privileges in the OpenManage Essentials GUI if: You are part of an Active Directory group, which is in turn part of another group You launch Server Administrator using the desktop icon and Single Sign-on is enabled. [167801].
Issue 15: Description OpenManage Essentials displays the power supply health as normal when the redundant power supply has lost the AC power source. Resolution: This is an issue with Server Administrator version 6.x. To avoid this issue, install/upgrade to Server Administrator version 7.0 or later. Issue 16: Description Problems with Dell License Manager Version 1.0.1 cannot be fixed using the “Repair” button. Resolution: 1. Navigate to the Control Panel Programs and Features. 2.
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.
– The remote desktop cannot be launched using the Application Launch-> Open Remote Desktop option. [40290] Installation Prerequisites Recommended Minimum Hardware Configuration for OpenManage Essentials Small (up to 100 Managed Systems): Processor: 2 (1.8 GHz minimum) Memory: 4 GB Disk Space: at least 6 GB Database: SQL Server Express Database location: Local Medium (up to 500 Managed Systems): Processor: Quad Core (1.
NOTE: OpenManage Essentials is supported only on x64 operating systems. NOTE: OpenManage Essentials is also supported on virtual machines. Database (Microsoft SQL Server – Local or Remote) NOTE: For large deployments, you must use SQL Standard.
NOTE: The OpenManage Install dialog box displays a notification if the latest version of OpenManage Essentials or Dell SupportAssist is already installed on the system. For Dell Repository Manager and Dell License Manager, this notification may not be displayed, even if the latest versions are already installed. [28109] Contacting Dell NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog.
