Release Notes

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. [28951]
Issue 18:
Description
On a domain controller (DC) or a system that is part of a domain, only "The Administrator" user can
repair Essentials using the Repair option available in the Uninstall or change a program window. Domain
Admins or Enterprise Admins cannot repair Essentials using the Repair option. However, they can repair
Essentials by launching the Essentials installer, and then selecting the Repair option. [31061]
Issue 19:
Description
If OpenManage Essentials is installed using domain user and if discovery/inventory fails after the
installation, verify the domain controller is responsive, a slow domain controller might cause
discovery/inventory to fail.
Issue 20:
Description:
REST API call to Dell's 11th generation of PowerEdge servers discovered in OpenManage Essentials using
SNMP protocol does not provide the System ID attribute. [61502]
Resolution:
It is recommended to discover the iDRAC of the 11th generation PowerEdge server using WS-Man
protocol.
Troubleshooting
Installation
• Ensure the latest SQL server service packs are installed on the system. You can run the following
command on the command prompt to verify the SQL version.
– sqlcmd -Q "print @@version"
• For typical install, ensure that the current user has “sysAdmin” rights to the SQL Server. For custom
install, ensure that the provided authentication credentials have “sysAdmin” rights.
• Try to use the custom install with different authentication method if typical install fails.
• Collect the logs from the temp folder. Search for the latest MgmtSt_*.log and InstallUtil_Install.log
files. Try to quickly analyze (if possible) InstallUtil_Install.log.