Compatibility Matrix

Important notes
This section provides important information that you must consider when you are working on OpenManage Integration for
VMware vCenter.
● OMIVV currently supports only the community named "Public" or "public". The SNMP community name is not configurable. If
another community name is used, the events are not received by OMIVV and the events are not displayed in the VMware
vCenter.
● A system profile created using a reference server with a certain BIOS version can cause deployment to fail. Some BIOS
versions do not provide accurate information for certain BIOS settings, such as the Embedded NIC1 and NIC2 settings. When
a server with the minimum BIOS version is used as a reference server in a system profile, the fields are ignored by both the
UI and deployment. An issue may occur, however, if the settings in question are required to have a certain value for
deployment to complete successfully. The solution to this issue is to use a server with up-to-date BIOS as a reference server
for a system profile.
● OMIVV registered with the VMware vCenter by using Fully Qualified Domain Name (FQDN) is highly recommended. For
FQDN-based registrations, the host name of the vCenter should be properly resolvable by the DNS server.
● For more information about the DNS requirements for vSphere, see the following links:
○ DNS requirements for vSphere 6.5 and Platform Services Controller appliance
○ DNS requirements for vSphere 6.7 and Platform Services Controller on Windows
● For cloud server, iDRAC Enterprise license is required.
● OMIVV supports only Server Message Block (SMB) version 1.0 and SMB version 2.0 based CIFS shares.
● iDRAC Delegated Authorization using OAuth 2.0 is not supported.
3
Important notes 13