When deploying an OVA in vSphere 8, it is not uncommon for the workflow to flag the OVA publisher certificate as untrusted. This can be a significant issue for organizations that prioritize security. In this blog post, I will cover how to overcome this issue.

The Problem

Deploying an OVF Template/OVA is a common operation for a VMware Administrator. You right-click on the ESX Cluster or an ESX host in the inventory browser and click Deploy OVF Template. This action initiates the Deploy OVF Template workflow. Typically, there are ten steps to this workflow. The first three steps ask for:

For those of you who know me and those of you who don’t, it won’t come as a surprise that I’m not a developer and I will never claim to be one. So, when I decided I wanted to learn how to contribute to a project on GitHub what better way to do this than to write a blog post about it.

Introduction

It’s no mystery that I run a homelab for personal and work purposes. I’m also lucky to own two Synology NAS arrays. My first NAS unit is a DS414. It’s a bit old, but it continues to hum along nicely. I need to make some time to upgrade the firmware on it. It’s still back on the 6.x firmware. As of the time I’m writing this post the latest firmware is 7.1.x. Stay tuned for post on how to do the upgrade. My other NAS unit is a DS1821+ This unit is great. This unit is running the latest firmware. It has eight drive bays and supports adding an external expansion unit. This means the maximum volume size supported is a whopping 108 TB!! I don’t see myself ever expanding to that size. But it’s nice to know I can.