Release Notes

• Microsoft Windows Server 2012 R2 Datacenter Edition

• Microsoft Windows Server 2016 Standard Edition

• Microsoft Windows Server 2016 Data Center Edition

• Microsoft Windows 8.1 Professional

• Microsoft Windows 8.1 Enterprise

• Microsoft Windows 10 Professional

• Red Hat Enterprise Linux 6.9 x86_64

• Red Hat Enterprise Linux 7.4

• Red Hat Enterprise Linux 7.5

• SUSE Linux Enterprise Server 11 SP4 x86_64

• SUSE Linux Enterprise Server 12 SP3

Supported web browsers:

• Google Chrome 63, 64, and 65

• Mozilla Firefox 57, 58, and 59

• Microsoft Internet Explorer 11

• Microsoft Edge

New in this release

• Support for new platforms, operating systems, and browsers.

• Support for Tripp lite PDU.

For details on the previous release, see OMPC 4.0 Release Notes.

Fixed issues

Issue 1: Misleading error message in Power analysis page.

Description: When you select a group without any rack for power analysis, the error message displayed is misleading.

Root cause: The different error cases not mapped to different error codes and OMPC 4.0 cannot provide error information in detail when

there is an unsupported scenario.

Resolution: In OMPC 4.1, new error mapping code is added and OMPC can provide clear error info in this case.

Known issues

Issue 1: Inconsistent power data observed for R640 in IPMI and Redfish protocol.

Description: There are minor differences in the R640 data observed through the IPMI and Redfish protocols, as both the protocols use

different sampling intervals for power reading.

Resolution: It is recommended to use one protocol at a time for data collection to maintain consistency in data.

Limitations

Issue 1: The power graph is blank while viewing the power (or temperature) history.

Description: When viewing the power history (or temperature) of a selected group in the 15 minute/1H window, the graph is blank.

Possible cause: OpenManage Power Center has just been installed and has not collected enough data to provide a power history graph.

Resolution or workaround: It is recommended to wait as OpenManage Power Center collects appropriate data to present the graph.

Issue 2: Though I have edited and saved the IPMI key, the next time I open the saved IPMI profile, the key is once again displayed as

0000….

Description: The key might have changed, and the you may have updated the value . However, while the display should read the value as

xxxx… as the key is encrypted, the encrypted key is instead displayed as 0000….. There is no difference between the display 0000…. and

xxxx….

Resolution or workaround: N/A

Issue 3: OMPC does not provide a warning when I delete my own LDAP account..

Dell OpenManage Power Center 4.1 Release Notes