What quirks will I encounter with OVF Tool, I wonder. I suppose I could look at this a yet another learning experience-and making myself all the more marketable by not being stymied when hitting one brick wall-turning 90 degrees and running smack dab into another brick wall. Now I have to take time out of schedule and try to get savvy enough to use OVF Tool. I mean, I guess I am 'glad' such a 'workaround' exists (it could be worse and no workaround exists), but I would like to believe something is actively being done on this particular matter-and is getting solved rather than relegating it to the back burner simply because a "workaround" exists.
I dislike having to resort to this, as I see the issue at-hand as a defect in the current GUI, and I shouldn't have to download a different tool, learn how to use it, (and deal with outputs different from what I am accustomed to). Also, the OEM Customized iso's tab has previous releases (6.7, 6.7U1, 6.7U2) Also, on the vSphere 6.7 downloads page click 'go to downloads' for an ESXi release and on the next page it'll let you select 6.7/6.7u1/6.7u2 from a drop down.
Looks like I need to get acquainted with it, since I don't see/hear anything which makes me believe a fix for this in the Web GUI is in the offing anytime soon. Have you tried the HPe customized iso (assuming you are using an HP server). I had read (elsewhere) that OVF Tool could be leveraged to accomplish the task-at-hand, which bothers me greatly-never having used that tool before. Varying types (i.e., Windows Server 2016, Windows 10 and Windows 7 during today's attempts). I should also state I'm not trying to export a Linux distribution, either, but rather, they're all Windows OS platforms. My only difference is the host machine I am using is an HP Proliant D元60 Gen 9 server. I reported this over on the Re: Cannot export to OVA after Upgrade to 6.5 thread, as I, unfortunately, found that thread before I found this one, but the end result is exactlythe same as you stated.