{"id":3872,"date":"2020-01-16T22:22:00","date_gmt":"2020-01-17T04:22:00","guid":{"rendered":"https:\/\/www.jasemccarty.com\/blog\/?p=3872"},"modified":"2020-02-16T19:40:48","modified_gmt":"2020-02-17T01:40:48","slug":"vswa-67p01-workstation","status":"publish","type":"post","link":"https:\/\/www.jasemccarty.com\/blog\/vswa-67p01-workstation\/","title":{"rendered":"vSAN Witness Appliance 6.7 P01 on Workstation 15 (& Fusion 11)"},"content":{"rendered":"

I haven’t posted here in a while, but I figure this is the best spot a very quick<\/strong> post on for this given it isn’t officially supported<\/em><\/strong>.<\/p>\n

With the release of the vSAN 6.7 P01 Witness Appliance, the OVA now prompts for OVF properties.<\/p>\n

These additional settings are read upon boot up, and automatically configure networking for the appliance. This streamlines the vSAN Witness Appliance deployment process significantly.<\/p>\n

\"\"
\nI blogged about this here: https:\/\/blogs.vmware.com\/virtualblocks\/2019\/11\/07\/vswa-67p01-update\/<\/a><\/p>\n

Importing pre-vSAN 6.7 P01 vSAN Witness Appliances into Workstation<\/h2>\n

OVF Property support was introduced in VMware Workstation 6.5.<\/p>\n

vSAN Witness Appliances have alaways prompted for the password to be used for the virtualized ESXi instance. This has always worked on vSphere, but has always failed on VMware Workstation. This is because the root password property was being assigned to a custom OVF Property “vsan.witness.root.passwd”<\/span>. VMware Workstation really didn’t know how to handle this property, and importing a pre-vSAN 6.7 P01 Witness would always result in the Witness spinning up with no way to log into it.<\/p>\n

Workarounds that allowed for proper root password assignment included:<\/p>\n