Troubleshooting: OVA Deployment Fails Due to a Newer Virtual Machine Hardware Version

Version Affected: All
 
 

Overview

Deploying the SecureAuth OVA can fail with an error about the wrong hardware version.

Cause

The OVA is built using a recent version of ESXi, so its virtual machine hardware version can be newer than what the target VMware environment supports.

Resolution:

Lower the OVA's virtual machine hardware version to one your ESXi environment supports:

1. Extract the .OVA file (using 7-Zip File Manager or WinZip) to a folder with the same name as the image file, without the file extension. This produces the .vmdk files, an .ovf file, and possibly an .mf file.
2. Edit the .ovf file in Notepad or another text editor.
3. Search for <vssd:VirtualSystemType>vmx-.
4. Change the version number (for example, vmx-13) to one your ESXi version supports (for example, vmx-10).
5. Save and close the .ovf file.
6. If present, remove the .mf file from the folder.
7. Import the OVF template as you normally would.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.