Have you tried downloading the ISO version rather than the Zip?
You could then mount this to your workstation / a windows sever logically close to the target location and run the installation of VCSA from there?
Tried it. Did not work.
Downloaded the ISO version.
I resolved the previous issue by downloading another version of vcenter.
Now, I have the error 2016-06-07T14:39:12.695Z: RPM Installation failed
Can you provide more information on what your actually doing?
I've never had the VCSA fail with an RPM installation error before.
What servers and vsphere version are you installing this on?
I am seeing a similar problem with the VCSA 6.5 distribution:
SHA digest of file VMware-vCenter-Server-Appliance-188.8.131.5200-4602587_OVF10-disk1.vmdk does not match manifest
Extracting the OVA file from the ISO also fails to deploy.
VMware vCenter Server Appliance
2016-11-15 | 6.5.0 | 3.37 GB | iso
2016-12-01T14:23:25.952Z - info: output:ERROR
+ SHA digest of file VMware-vCenter-Server-Appliance-184.108.40.20600-4602587_OVF10-disk1.vmdk does not match manifest
2016-12-01T14:23:33.010Z - info: output:RESULT
2016-12-01T14:23:33.010Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><Errors><Error><Type>ovf
tool.manifest.mismatch</Type><LocalizedMsg>SHA digest of file VMware-vCenter-Server-Appliance-220.127.116.1100-4602587_OVF10-d
isk1.vmdk does not match manifest</LocalizedMsg><Arg>VMware-vCenter-Server-Appliance-18.104.22.16800-4602587_OVF10-disk1.vmdk
2016-12-01T14:23:33.015Z - error: Ovf Service:vmrefFlag: false
2016-12-01T14:23:33.015Z - info: Cancelling timeout due to error from progress callback
2016-12-01T14:23:33.015Z - error: Progress Controller: [VCSA ERROR] - Progress callback error
2016-12-01T14:23:33.016Z - error: Progress Controller: [VCSA ERROR] - Details SHA digest of file VMware-vCenter-Server-Appliance-22.214.171.12400-4602587_OVF10-disk1.vmdk does not match manifest
Such issues occurs if we have latency.
Hope you are having Esxi host and the ISO file located on the same location.
This is exaclty the issue I am having now. My ISO seems to be corrupt but now I am starting to hesitate to accept that answer.
Well, as identified in your thread here, your hash does not match the value which is posted by VMware. So regardless of whether this is the 100% exact cause or not, we know you have corruption or missing data somewhere in that file. As in Monopoly, do not pass go and do not collect $200, because if you have corruption then nothing else really matters until that's resolved.
Since then I have managed to get the newer ISO for 6.7... and it got deployed without issues. So there is now evidence that the issue WAS indeed the corrupt ISO.