Ova Vmware Workstation
Mar 17, 2017 - Solved: Attempting to import ONTAP 9.1 OVA file for simulator setup using VMware® Workstation 12 Pro 12.5.4 build-5192485. Receiving unknown error. The OVA is the OVF folder contents all zipped into a single file. The purpose of the OVA is when you want to take an OVF and share it or give it as a download. The OVA needs to be opened into the OVF before it can. Type the name for the virtual machine, which you need to attach the OVA, OVF, second box drop down OVA or OVF files. Workstation Pro converts the virtual machine from OVF format to VMware runtime (.vmx) format. You can import both.ovf and.ova files. OVF is a platform-independent, efficient, extensible, and open packaging and distribution format for virtual machines.

I am testing in a lab environment with the following setup: I have a Windows 10 laptop with VMware Workstation 12 Pro installed. I have create a virtual machine in Workstation running Windows Server 2012 R2.
I have set up AD and DNS on it. This server has an IP address of 192.168.59.129 and its FQDN is win2012.ad.example.com. I can ping the machine and DNS is working correctly. I am now trying to install vCenter Server Appliance 6.5, so far with no success.
I am trying to use the OVA file: VMware-vCenter-Server-Appliance-6.5.0.52OVF10.ova located in the ISO. I understand after reading several articles that I first need to configure the.vmx file before booting my machine. I think the main reason is that I am not fully understanding the settings that should be placed in the file, specifically the vmdir settings.
I have tried a number of different variations on the settings and still nothing seems to be working. There are two things that might be causing issues for you from the information you've posted so far. The vmdir.site-name and vmdir.domain-name values are not relating to the AD site name and domain name. VCenter has it's own site and domain name concepts that you're supposed to enter here. The site name is arbitrary (until you get into multiple vCenter deployments).

Starcraft broodwar german rapidshare. The domain name is essentially the vCenter specific Kerberos realm (defaults to vsphere.local). And because you set the domain name to the same name as your AD domain, they conflict.
Import Ova Vmware Workstation
Also, in your AD DNS, do you have a reverse zone setup such that the PTR lookups against the IP addresses resolve back to the names? VCenter is historically sensitive about forward and reverse lookups working.
Comments are closed.