- Knowledge base
- Scanner Appliance
- Troubleshooting
-
Security updates
-
Product news
-
Next-Gen Vulnerability Management
-
Getting started
-
General
-
Operating status
-
Network & System Security
-
Web Application Security
-
Cloud Security
-
API Security
-
Phishing Simulation & Awareness Training
-
Attack Surface Management
-
Scanner Appliance
-
Device Agent
-
On-premise platform deployment
-
Asset management
-
Vulnerability manager
-
Reports
-
Digest reports
-
Organizer
-
Continuous monitoring
-
Integrations
-
Platform API
-
Remediation
-
Users
-
PCI DSS
-
Terms & conditions
-
Dashboard
vSphere deployment issue - The OVF package is invalid and cannot be deployed.
An issue that might occur when deploying the OVA via vSphere Client.
In some cases with older versions of the client, the deployment fails, and you will see this error:
"The OVF package is invalid and cannot be deployed.
The following manifest file entry (line 1) is invalid: SHA256 (xxxxxxx.ovf)."
- The cause of this error is that the vSphere Client does not support the SHA256 hashing algorithm, which the latest VIC OVA was made of (from 1.1.1).
It also affects any OVA deployments via PowerCLI when using the Get-Ovf Configuration cmdlet.
The resolution for this issue is to deploy vIC via the vSphere Web Client or ESXi Embedded Host Client because both support SHA256.
If you want to have your deployments automated, you need to convert the OVA from the Cryptographic Hash Algorithm SHA256 to SHA1.
For further information regarding the issue and troubleshooting: https://kb.vmware.com/s/article/2151537