Dell Systems Management Solutions: Dell OpenManage Essentials (OME) FAQ

Dell Systems Management Solutions: Dell OpenManage Essentials (OME) FAQ

OpenManage Essentials (OME) FAQ

Installation | Configuration | Preferences | Discovery | Inventory | Health | System Update | Reports | Tasks | Compellent | Troubleshooting | Misc


Installing OME using a remote SQL Database Named Instance

SQL Server with Named Instances requires the SQL Server Browser service to be running to connect remotely

OME support for the SQL Server Evaluation edition

OME does not support the SQL Server Evaluation edition

Error "HTTP Error 500.19 - Internal Server Error the requested page cannot be accessed because the related configuration data for the page is invalid." occurs when launching the OME console

Disable the XPress compression scheme from the configuration using the following command:
%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']
Alternatively, Add an attribute of "precondition= "64bitness" for this module entry so that it loads only in 64bit application pools.

IPMI is disabled after installing BMC Utility

Restart DSM Essentials Network Monitor Service, DSM Essentials Task Manager service and restart IIS

Change OME console port after the OME installation

Follow these steps:
Windows: Press Windows Key+R, type "regedit" and press Enter to open Windows Registry Editor
Navigate to HKEY_LOCAL_MACHINE->SOFTWARE->Wow6432Node->Dell Computer Corporation->Dell OpenManage Essentials->Connection Service
Change the "ConsolePort" registry key
Start Internet Information Services (IIS) Manager
Navigate to ->Sites->OpenManage Essentials
Right click on "OpenManage Essentials" and click "Edit Bindings"
Edit https port number 2607
Restart OME Netmon, Task Manager and the IIS services
Note: Do not modify the http port number in the registry or in IIS.

The installation of OME takes longer on Windows 2008 SP2 X64bit

The installation of IIS roles services takes longer to install on Windows 2008 SP2 X64bit which causes OME installation time to increase

Installing OME on a server where TLS 1.2 security protocol is the only protocol enabled

Follow these steps:
Update Windows Server to the latest available update
Enable only TLS 1.2 security protocol. Click here for more information
Enable FIPS in Windows Server. "System cryptography: Use FIPS-compliant algorithms for encryption, hashing, and signing" should be enabled under Local Group Policy.
The SQL Server edition must support TLS 1.2. Click here for more information
Install OpenManage Essentials.

Back to Top


Device name restrictions when using the Create Template feature to get a Chassis configuration

Do not brackets i.e [ ]

Error "MinBandwidth"

Set the new values to zero as an intermediate step before applying the desired values
Original setting 20, 20, 30, 30
New setting 70, 10, 10, 10 - This will FAIL with old value 20 and new value will be blank

Back to Top


Increase the console maximum timeout setting from 6 hours

6 hours is the maximum timeout setting

Back to Top


Troubleshooting a discovery task that fails to be created or executed

Make sure DSM Essentials Task Manager service is running in Windows Services

Devices discovered with WMI are classified as Unknown

WMI discovery will classify a device as Unknown if the credentials used are in the Administrators group and used for the discovery range.

Click here for more information

ESXi servers are classified as Unknown

Increase the timeout setting to 10 and retry setting to 4 in the WS-MAN page for discovery wizard

Important Discovery information and Dell OpenManage Server Administrator (OMSA)

OMSA must be installed on Dell PowerEdge servers to be discovered and managed using the SNMP protocol. OMSA can be installed using the OME console. PowerEdge servers using WMI can be discovered without OMSA. The servers will not be classified as Unknown or Computer. Management capabilities in OME are limited if OMSA is not installed.

Servers appear under the Unknown node in the device tree

Systems discovered with SNMP only without OMSA installed will be classified as Unknown and displayed under the Unknown device group. Check the SNMP settings if OMSA is correctly installed on the managed node
Note: SNMP community strings are case sensitive

Start the Services MMC on the managed node and open the properties page for SNMP Service
Add the OME server on the Security tab under Accept SNMP packets from these hosts

Run /etc/init.d/dataeng enablesnmp followed by /etc/init.d/dataeng restart on Linux servers

Run the Services test in the Troubleshooting Tool to determine if the following conditions are met


Restart the services

Devices have the status System Down determined and frequency of checking device status

The connection state shows 'ON or 'OFF' under device summary table in the LHS. The removal of the device from the network by either powering it off or removing the NIC cable will result in a status of 'System Down'. The device is considered down if it does not respond to the ping application. Polling for connection state defaults to 1 hour. The frequency of polling can be changed

Troubleshooting a server in Unknown status or not returning inventory data even after SNMP is enabled and OMSA is installed on the target server

Confirm the DSM SA Data Manager Service is running in Windows Services on the target server. Restart the service if necessary and re-run the inventory task.

Discovering EqualLogic storage arrays

EqualLogic arrays are discovered with the SNMP v2 protocol. Choose SNMP in the OME discovery wizard along with the appropriate 'read' community string. Include the IP address of the EqualLogic Group and IP addresses for all the members in the discovery range.

The iDRAC 6 IP address shown as in OME

Upgrade the iDRAC firmware

EqualLogic blade devices are not classified under the Modular group

Confirm the chassis service tag in EqualLogic is populated for that to be classified under Modular group

Discovery of PowerConnect 8132 is time consuming

Update to the latest firmware

KVM 4332DS is not classified under KVM

Update the firmware

iDRACs are being deleted and re-added during a long discovery and inventory

Enable the DNS iDRAC to Server name correlation

DSA (LASSO) collection of logs from EqualLogic group upon receiving an event is incorrect or incomplete

Discover EqualLogic storage groups using the Group Management or Storage Group IP address only and not include any of the member IP addresses in the discovery range configuration.

Troubleshooting the "invalid package signature" error when tasks such as OMSA deployment, iDRAC Service Module deployment or system update fails

Install the VeriSign Class 3 Public Primary Certification Authority - G5 certificate on the server running OME

The Dell Server appears in the OEM device group

Perform a Lifecycle Controller wipe using winrm from a computer on the same network using the command below
Note: The LifeCycle Controller wipe operation is destructive. It will wipe out your iDRAC License key. Export the key so it can be restored. Refer the appropriate iDRAC manual. winrm i LCWipe -u:[iDRAC_root] -p:[iDRAC_PWD] -r:https://[iDRAC_IP]/wsman -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic
Note: The command will ReturnValue of 0 if it was successful. The iDRAC will inaccessible for a short period of time. The iDRAC will be back to a default state with an IP address. Run an OME discovery in order to re-categorize the server in the device tree.

Unable to discover iDRAC/chassis/ESXi servers using WSMAN protocol

Check that the devices have valid certificates installed

The devices in Device tree disappear during discovery

Edit the dconfig.ini located in SysMgt\Essentials\configuration
Change the following line PRIVATE_MAC_EXCLUDE_LIST to
Save and restart the OME services
Note: Administrative privileges are required to edit dconfig file. Make a backup copy of dconfig.ini file before making changes.

The iDRAC or CMC display as "Unknown" status after upgrading to the latest firmware version

Click here for information on resolving this issue.
Note: Ensure the required registry updates are done either manually or using the "Easy Fix" described in the Microsoft support article

Back to Top


Troubleshooting inventory task failures

Make sure DSM Essentials Task Manager service is running in Windows Services

Updating inconsistent data in the device details and Modular Enclosure Information report for a PowerEdge VRTX CMC after performing discovery and inventory using WS-Man when all the server slots of the chassis are empty

The PowerEdge VRTX only reports data for server slots with a modular server present and does not report any data for empty server slots.

PCIe Information and Virtual Adapter Information table in the PowerEdge VRTX device details page continue to show the server name of a modular server that has been removed from the VRTX chassis, after the CMC has been re-inventoried

This behavior will impact data tables which show association of the modular server slots to the PowerEdge VRTX chassis resources such as the PCIe Information, Virtual Adapter Information and Virtual Disk Access Policy Information tables. To update these tables to reflect the correct data the instance of the VRTX CMC must be removed from the device tree and re-discovered and inventoried.

The output power supply shown as 0 watts in the PowerSupply info table for my server with a cabled PSU

The output power supply info will be shown as 0 watts for servers with cabled PSU such as a T430 server.

Back to Top


Retrieving the health status of Dell PowerEdge servers

OMSA should be installed on the server

OME displays the power supply health as Normal when the redundant power supply has lost power

Upgrade OMSA

The device count and rollup health show 0 when the REST API command is used for a group marked hidden in the OME Console

The REST API used to return information about a Device Group ( /DeviceGroups/DEVICEGROUPID ) should not be used on device groups that are marked hidden in the OpenManage Essentials console

The PowerConnect W series switch not displaying device health

The health attribute is only available if the PowerConnect W switch is in the master role

Back to Top

System Update

Loading a Dell catalog for software update or errors when trying to run software update tasks

Download the catalog to the OME server directly
Browse for catalog.xml file on the local system
Load catalog and verify it shows as loaded in OME. Download to get the latest catalog from for troubleshooting purposes
Create software update tasks. Information can be found in the task details when the task fails.
Change Internet Explorer security settings to Low if tasks will not run when executed

Order installation of packages

Packages are applied in the following order.- Driver- Firmware- Firmware ES- BIOS- Application

The error "Attempted to perform an unauthorized operation." occurs when performing a catalog import task

Change the folder and share permissions to allow the user access
When using Repository manager as you catalog source make sure that the packages associated with the RM generated catalog are present in the same folder as the catalog.
If the packages are not present in that folder you would see an invalid path result for the packages.

Configuring Internet Explorer with Enhanced Security Configuration so OME can utilize all features that use resources from Dell Online

Add * to the Trusted sites security zone.

The error "Access to path 'C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate is denied" occurs running system updates

In File Explorer navigate to C:\Program Files (x86)\Dell\SysMgt\Essentials\ and create a new folder named SystemUpdate

The System Update task displays as failed even though the server updated successfully

The target server required a reboot and did not respond within 30 minutes. Check the server status and run the inventory separately for the server.

The inventoried server does not have a software inventory or displays as a non-inventory state when an inventory task was executed

Install OMSA on the server or verify the services are started
Check the OMSA log located at C:\Program Files\Dell\SysMgt\oma\log
Delete all of the files except for the cachecfg.txt and restart the DSM SA Shared Services within Services.msc.

Dell PowerEdge servers are discovered and inventoried, identified as non-compliant and the update task completes quickly

Provide NTFS Full Control permissions to the C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate folder
Re-run system update tasks on the same target when they have not completed
This will result in OME resending the same updates again.

The Error "Exception message: Error: 1205, Procedure: usp_Catalog_Insert, Message: Transaction (Process ID 69) was deadlocked" occurs

Use a different tool to mount the ISO

Pushing updates to VRTX Chassis

The VRTX chassis must be discovered and inventoried using WS-Man protocol for OME to push updates

The compliance report pie chart disappeared or is not displaying

Refresh your browser or perform the following
Click the 'Filtered by: All Update Devices' link next to the 'System Update' portal title.
Check 'All Update Devices' in the device selection tree.
Click 'Apply'.
Within 30 seconds the pie chart will reappear
Note: If the chart still does not appear, make sure all devices are discovered and inventoried verifying your catalog.

Updates sent via iDRAC fail when using the correct credentials and the connection is present

Execute the below command for every iDRAC that fails updates and then rerun the update task.
racadm sslresetcfg

The iDRAC is not able to download the packages and update tasks using WSMAN fail. The IP address of the OME server in the URL is blank.

Be sure the DNS is configured correctly and the hostname resolves to IP Address. DNS should not be set to lookback alone.

Servers with iDRAC firmware version 1.30.30 are not compliant

Upgrade the iDRAC firmware

9G and 10G servers do not appear when the catalog source is SUU

There are separate catalogs for 9G and 10G server updates

The error "The specified URL is invalid." occurs when an out-of-band system update task fail

Check that ports 442, 80 and 1278 are open on the firewall or disable the firewall

Linux target in-band updates fail to execute

Install tar and gunzip put them in the path. The "NOPASSWD:ALL" setting must be present for the sudoers group when using "sudo",.

The task fails with error message "Error occured: The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again." after creating a system update via iDRAC

Enable the Basic authentication level

The Client configuration should match the settings below

winrm get winrm/config/client

NetworkDelayms = 5000
URLPrefix = wsman
AllowUnencrypted = false
Basic = true
Digest = true
Kerberos = true
Negotiate = true
Certificate = true
CredSSP = false
HTTP = 5985
HTTPS = 5986

Back to Top


Virtual Machine Information and Virtual Machine Host Product information Tables are missing in ESX Sever Device Details

The SNMP agent for this system may not be properly configured and is not returning any data for the VMware OID

The Device Name shows as IP Address instead of the actual Device Name on the Reports page

The IP address will be displayed instead of device names only when devices from which the alerts received are not discovered in OME

The warranty report is not getting populated after running inventory

Disable Internet Explorer Enhanced Security Configuration, add and websites to Trusted sites

Back to Top


Troubleshooting a software update task or remote task that fails to be created or executed

The DSM Essentials Task Manager service must be running in Windows Services.

Emails are not received after setting up email alert action

Configure Antivirus software or other email blocking software to allow emails from OME

Updating the iDRAC is time consuming

Check the credentials used to perform the installation

Stopping a command line task with a single target

A task with only one device cannot be stopped once the execution has started

OME Task Manager crashes when the user account has a \p in remote tasks. For example: domain\puser

Use a username that does not have a \p in it

Back to Top

OMSA & Compellent

Resolution for Compellent issues

Make sure your Dell-Compellent device has the latest firmware installed

Back to Top


Troubleshooting installation issues

Review the 'InstallUtil.log' file located in windows temp directory usually c:\windows\temp for installation issues

Error "You do not have permissions to alter these settings. Please contact your system administrator."

Add the domain account used to install OME to the local Administrators group and run iisreset from an elevated command prompt

The right click option for OMSA launch isn't available with OMSA is installed on the target server

Delete and rediscover the same device

OME is unable to create a connection to SQL Server

Make sure TCP/IP is enabled using SQL Server Configuration Manager

EqualLogic blade devices are not classified under the Modular group

Make sure the chassis service tag in EqualLogic is populated for that to be classified under Modular group.

Back to Top


OME CLI functionality not working

The default port 2607 must be used during installation

Unable to delete nested custom groups from OME CLI

he default port 2607 must be used during installation

General OMSA information

Click here and choose the appropriate version

The alerts and task schedules in OME display a time stamp off by 1 hour

Check the location settings for the server in "Regional and language settings" in the Control Panel to make sure the location for the server and date/time formats are set appropriately for the region where the server is located

OME takes a long time to launch or traverse through various pages

Windows updates running in the background or other resources intensive processes impact performance

OME does not launch and errors "An add-on for this website failed to run"

Add the OME URL to the exceptions list in the Internet Explorer options -> Security -> Local Intranet -> Sites -> Advanced

OME memory consumption increases when logged in as a domain user

Disable the following settings in the IE browser
Check for Publisher's certificate revocation
Check for server certificate revocation

Error message "unable to generate a Trusted Key for Linux" after running Discovery /Inventory on a system running Linux

Run an OMSA Deployment Task which will successfully generates the Trusted Key

Back to Top

Article ID: SLN311891

Last Date Modified: 03/20/2019 03:53 AM

Rate this article

Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.