Compatibility Matrix

3
Important notes
This section provides important information that you need to consider when you are working on OpenManage Integration for
VMware vCenter.
OpenManage Integration for VMware vCenter supports BIOS mode to deploy Hypervisor on the target server. Make sure that
you have BIOS mode selected in the reference hardware prole before applying the Hypervisor prole. If there is no hardware
prole selected, make sure to manually congure the boot mode as BIOS and reboot the server before applying the Hypervisor
prole.
NOTE: Hypervisor deployment is supported only in the desktop client.
The OpenManage Integration for VMware vCenter currently supports only the community named "Public" or "public".The SNMP
community name is not congurable. If another community name is used, the events are not received by the OpenManage
Integration for VMware vCenter and the events do not appear in the VMware vCenter.
A hardware prole 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 hardware prole, the elds 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 hardware
prole.
NOTE: Servers being used for deployment should also have updated BIOS. If deployment tries to apply settings to a
server with issues in BIOS, deployment fails. Currently the BIOS version is not checked for compliance, but it is
displayed on the server compliance page. Warnings are displayed on the hardware prole reference server and BIOS
settings pages and when you select a deployment template with an aected hardware prole during deployment.
Registering OpenManage Integration for VMware vCenter with the VMware vCenter using Fully Qualied Domain Name (FQDN)
is highly recommended. For FQDN based registrations, the hostname of the vCenter should be properly resolvable by the DNS
server.
NOTE: For more information about the DNS requirements for vSphere, see:
DNS requirements for vSphere 5.5
DNS requirements for vSphere 6.0
12