Recently, some macOS Sierra users have had an issue with the VCSA 6.5 installer. At the “Set up appliance VM” (step 5), the VCSA deployment and storage sizes are not available. The following error is received “A problem occurred while reading the OVF file.. Error: ovftool is not available”. Let me start by saying this is not an issue with the VCSA 6.5 ISO or installer, it has to do with a change in Sierra. Also, before I go any further, Sierra is currently not supported with the VCSA 6.5 installer. Engineering is working to support Sierra in a future update. The supported system requirements for the VCSA installer are here. With that said, I want to shed more light on why this is happening and what options are available with Sierra.
The vCenter Server Appliance (VCSA) 6.5 has significant new features and improvements mentioned here. One area of notice is the installer, which in this release not only has a new look and feel but other improvements. These improvements are not only visible from the ISO, but also during the deployment. The end result is a better experience throughout the VCSA deployment process. Let’s jump in and take a closer look.
The VCSA installer is now browser agnostic, which makes it more portable. Along those lines, the Client Integration Plugin (CIP) is no longer needed. CIP provided browser functions such as importing an OVF/ OVA which are now native. Other CIP provided functions that are now native include:
- Exporting VM or vApp as an OVF / OVA
- Deploying OVF / OVA from a local file system or URL
- Exporting and importing from Content Library to the local file system
- Downloading and uploading files to and from a datastore
- Connecting remote devices to a VM (CD-ROM, USB, etc.)
During VMworld Barcelona 2016, VMware announced vSphere 6.5. With lots of new features and updates, this is one of the biggest vSphere releases we have had in a while. Leading the charge is none other than the vCenter Server Appliance (VCSA). VMware’s direction for vCenter Server is the VCSA and it’s quite evident from this release. The VCSA and its Windows counterpart remain on par when it comes to scalability. From an operational and feature perspective, the VCSA has advantages. This post is a quick rundown of the VCSA 6.5, I’ll go into more details in future blog posts. Time to take a look at what’s new and why migrate2vcsa you should 🙂
VCSA 6.5 ISO
Starting with the VCSA 6.5 ISO, improvements are easily visible when comparing to 6.O:
I recently wrote about the release of the vSphere HTML5 Web Client Fling and how to configure it. Since then there has already been an update to the Fling. I’ve gone through update process in my lab using the rpm, but I also decided to deploy a new OVA (version 1.1) and found a few hidden features.
During the configuration of the appliance I found a directory called “vspherefeatures”. The directory contains a configuration file with three disabled entries. Of course the first thing that came to mind is what’s the harm in just enabling one to see what happens. What happened was me enabling all three after seeing the first one worked.
The Three hidden features are Datastore File Browser, Add Host Wizard, and Network Selector. I’m assuming that these are features that will be available in future releases of the vSphere HTML5 Web Client Fling. For now looks like we can get a sneak peak 🙂
VMware first introduced the vSphere Web Client with the release of vSphere 5.0. The vSphere Web Client would be the future management tool replacing the vSphere client aka “Legacy, Thick or C# Client”. This would be become more evident over time with each release of vSphere. New features could only be managed through the vSphere Web Client. While the concept of a browser based client is a step in the right direction, the dependency of flash was not. Keep in mind the decision to use flash was made when it was the standard for web applications, times and standards have changed. With that change it has taken some time to work on replatforming the vSphere Web Client. This always leads to the question, when will we see a HTML5 version of the Web Client? I’m happy to announce the wait is over!