Unsolved
This post is more than 5 years old
30 Posts
0
1103
DDVE 6.0.1.0 vs invalid certificate - how to fix this?
Hi,
After trying to install an older version of DDVE (6.0.0.9) and getting a "invalid certificate" while trying to deploy the OVF, I've figured it may be related to the merge with Dell. As such, I've downloaded the most recent version (6.0.1.0) and got the same result. When I look at the certificate, I'm seeing that it is valid from 2016-03-08 to 2017-03-08. I assume that explain why I can't deploy this OVF. Is there a way to fix this or we have to wait for EMC to generate a new certificate?
Thank you.
ehfortin
e_fortin
30 Posts
0
April 24th, 2017 06:00
Hi,
I found a way around it. It is not sexy but it worked. Basically, I extracted the content of the OVF to a folder and deleted the file that end with ".cert". I then started the OVF wizard from vCenter, selected the 3-4 files that remains in the folder I created and it worked without issue. As you will see, the wizard now tell you that there are no certificate so no issue with the expiration date.
If somebody has a better way of doing it, I would like to know it. Until then, I have a workaround.
Thank you.
ehfortin
James_Ford
30 Posts
1
April 27th, 2017 07:00
Hi,
So this is a known issue caused by an out of date certificate in the DDVE OVF. In vSphere 6.0 (and earlier) this simply causes a warning but deployment continues - in vSphere 6.5, however, this is a fatal error and the OVF cannot be deployed.
Data Domain are currently working on making a new OVF available with an updated certificate but I don't have a time frame on when this will be done yet. In the mean time you can deploy using ovftool from the command line - even on 6.5 this will produce a warning but the deployment will still work.
Thanks, James