1.Install 

1.Q: Can I upgrade my OME 1.0 Open Evaluation installation to the new OME 1.0.1 version?
A: Yes.  When OME 1.0.1 ships, you will be able to easily install it over your 1.0 Open Evaluation instance.

2.Q: I cannot install OpenManage Essentials using a remote SQL Database Named instance?
A: SQL Server with named instances requires ‘SQL Server Browser’ service to be running to connect remotely.

3.Q: Will OpenManage Essentials support SQL Server ‘evaluation’ edition?
A: No, SQL Server ‘evaluation’ edition is not supported because this is a prerelease version.

4.Q:  What if I see this error when I launch the console – “HTTP Error 500.19 - Internal Server Error the requested page cannot be accessed because the related configuration data for the page is invalid.”
A:  Remove/Disable the XPress compression scheme from the configuration using the command below:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

OR

Add an attribute of "precondition= "64bitness" for this module entry so that it loads only in 64bit application pools.

5.Q: What if IPMI is disabled after installing BMC Utility?
A: Try restarting DSM Essentials Network Monitor Service, DSM Essentials Task Manager service and restart IIS.

6. Q: How do I change OME web service/console port after OME installation?
A: After OME installation, follow these steps:

- From Start->Run, type "regedit" and hit "Enter" to open Windows      registry.

- Navigate to HKEY_LOCAL_MACHINE->SOFTWARE->Wow6432Node->Dell Computer  Corporation->Dell OpenManage Essentials->Connection Service

- Update "ConsolePort" on the right hand side.

- Launch Start->Administrative Tools->Internet Information Services  (IIS) Manager

- Navigate to <SystemName>->Sites->OpenManage Essentials

- Right click on "OpenManage Essentials" and click "Edit Bindings".

- Edit https port number "2607".

- Restart OME Netmon, Task manager and IIS services

Note: Please do not modify http port number either in registry or IIS.

7. Q: Installation of OME takes longer on Windows 2008 SP2 X64bit. Why?
A: Installation of IIS roles services takes longer to install on Windows 2008 SP2 X64bit which causes OME installation time to increase.

8. Q: Fresh Installation of OME 2.3 on Windows Server 2016 fails with the prereq missing message. Why?

A: Refer this link for more details around problem & available solutions: http://en.community.dell.com/techcenter/systems-management/f/4494/t/20018103

2.Tasks

1.Q: What troubleshooting can I do if a software update task or remote task fails to be created or executed?
A: Make sure DSM Essentials Task Manager service is running in Windows services.

2.Q: Why am I not receiving emails after setting up email alert action?
A:  If you have an Antivirus Client installed on your system, you will need to configure it to allow emails.

3.Q: Does OME support Power control options for 8G servers?
A: Yes, Power ON (option available in Server Power Options Task), and Power OFF (option available when used in IPMI command line task, in Arguments field use: chassis power off) works on 8G servers with BMC. 

Note: If the 8G server has a DRAC4 over BMC, make sure the DRAC4 IP is pingable in Troubleshoot tool using IPMI protocol. If the RMCP ping fails, the power tasks will likely be failing. This simple check will also help to know if the connection to the RAC devices for any generation server is passed. 

4.Q: Why does the update using iDRAC taking a long time?
A:  Check your credentials. Wrong credentials may cause OME to wait for communication timeout which will result in failed task after the timeout period. If you are updating 10+ devices with wrong credentials it may take up to 2-3 hours before reporting failure.

5.Q: How can I stop command Line task with single target? 
A: A task with only one device cannot be stopped once the execution has started.

6. Q: Why does the OME Task Manager crash when the username used has a \p in remote tasks. For example: veggie\pizza.
A: This is a limitation in OME parsing logic. The workaround is to create and use a username that does not have a \p in it.

3.Discovery

1.Q: What troubleshooting can I do if a discovery task fails to be created or executed?
A: Make sure DSM Essentials Task Manager service is running in Windows services

2.Q: Why are devices discovered with WMI getting classified as Unknown?
A: WMI discovery will classify a device as unknown when the credentials for a user account in the Administrators group (not Administrator) are supplied for the discovery range in some cases.If you are seeing this issue, read the following KB article and apply the registry work around described therein.

So far, this applies to managed nodes with Windows Server 2008 R2.http://support.microsoft.com/?scid=kb;en-us;951016

3.Q. My ESXi servers are getting classified as unknowns.
A: If you are using ESXi 5.0 update 1, please install OM 7.0 VIB available at 

http://www.dell.com/support/drivers/us/en/555/DriverDetails/DriverFileFormats?DriverId=VPTVV.

You can also try increasing the timeout (setting to 10) and retry (setting to 4) values in the WS-MAN page for discovery wizard.

4.Q. My ESXi servers after few days of monitoring, becomes unknown
A:  VMware has identified an issue affecting VMware ESXi 5.0x and 5.1x where CIM monitoring applications fail to authenticate with “No space left on device” error in /var/log/syslog.log:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2043464.

This issue can cause previously discovered systems to move to an unknown status, fail to discover, or not show in both OpenManage Essentials (OME) and Dell Management Plugin for VMware vCenter (DMPVV).