Goodbye vCenter Server for Windows and Flash-based vSphere web client!

Hmm…. it’s not even VMworld yet and VMware decide to make 2 big-ish announcements.

Although tbh, since vSphere 6.5 was released these 2 announcements have long been coming!

Finally, after loads of speculation, VMware had announced that vCenter Server for Windows and the Flash-based vSphere web client is to be deprecated with the launch of the next version of vSphere. Updates to 6.5 will continue supporting the 2 features, but come vSphere 7.0 it will be no more….


“vCSA-exclusive capabilities such as file-based backup and restore, unified update and patching, native vCenter High Availability, and a significant performance advantage mean that the VCSA has become the platform of choice for vCenter Server.  Additionally, due to the integrated nature of appliance packaging, VMware is able to both better optimize and innovate vCenter Server at an accelerated pace.  Finally, with the VCSA, VMware can provide support for the entire vCenter Server stack including the vCenter Server application, the underlying operating system (Photon OS), and the database (vPostgres). By doing so, VMware can ensure that customers can focus on what matters most while having a single source for updates, security patches, and support.  The VCSA model is simply a better model for vCenter Server deployment and lifecycle management.”

That pretty much sums up why VMware are 100% behind the vCSA, although they miss out the whole “screw you Microsoft licensing!!” part! Plus given that 6.5 ships with a migration tool that helps you move/upgrade from a Windows vCenter to an Appliance vCenter, it’s no surprised that more and more people are moving over when it comes round to upgrade time!

In fact ever since 6.5 was released, I’ve not even deployed a single Windows vCenter Server – all my customers have been moved over to the vCSA.

With regards to the vSphere Web Client, loads of people found the flash-based version was frustratingly difficult to use – it was slow, it was notoriously prone to crashing and frankly it was based on in-secure Flash technology (not to mention that Adobe themselves are dropping flash). HTML5 is the way to go baby!

So with those announcements in mind….. I may think about changing some of my VMworld sessions to jump on the vCSA and Web Client update sessions!!



The End of vSphere C# Client

I’ve been so busy the past week or so that I totally forgot to post up a link to an article I wrote for SearchVMware regarding the recent announcement of the end of the C# Client!


VMware Labs re-write the Onyx tool for vSphere 6.0 Web Client

I’ve been a fan of Onyx since it was launched back in 2009/10 and was an avid user of it when I had to quickly learn how to write some automation scripts for a previous project.

For those of you who haven’t heard of this tool before, Project Onyx is a script recorder that sits between vSphere Client and vCenter Server and records what scripts were called whenever you did something within the C# Client…. it could output the scripts as raw SOAP messages, C#, and vCO (or vRO) JavaScript code.

To my joy, the clever guys at VMware Labs have now taken Onyx and created a new Fling that works with vSphere 6.0 Web Client:

Onyx for the Web Client is a Fling that translates actions taken in the vSphere Web Client to PowerCLI.NET code. The resulting code can then be used to understand how VMware performs an action in the API and also better define functions.

Even better news is that it works for a Windows installed vCenter Server and the vCenter Server Appliance! =)

However, reading through the documentation, I noticed this huge warning in red:

WARNING: This fling replaces core Web Client files and may cause issues with stability and patching of future versions of the web client, please only continue with this installation if you are using a test or dev environment.

As such, I really strongly recommend that you only use this tool in your test environment as it could interfere with future patches/updates…. not to mention it could cause problems if you have to log a support call with VMware!

The end of Flash MUST be nigh!!

Adobe has to either fix all the vulnerabilities with Flash or kill it off completely!!

Even Facebooks’ security chief is telling Adobe to kill off the product!

With all the recent security exploits with Flash, it comes as no surprised that Firefox now blocks Flash by default!

Chrome has already limited Flash playing in their browser, and Microsoft recommends that you disable it in IE and only allow certain trusted sites….

However, one of the BIG problems that now faces VMware customers is which browser can they use to manage their VMware environment with vSphere Web Client?

If you’re not aware, VMware wrote the Web Client to use Flash…. which was a huge mistake in my opinion! And now that browsers are dropping NPAPI and Flash support, how long till VMware realise their mistake and re-write the Web Client using HTML5?

Whilst there has been loads of enhancements to vSphere 6.0 Web Client, you can see from the comments on VMware’s blog announcement that the continuation of using Flash has not gone down well…..

Anyways, let’s see what Adobe does…..

Tweak Chrome to fix vSphere Web Client

So one of the reasons my blog hasn’t been updated quite as regularly as the previous 6 months is because I’ve been quite busy with work, plus I’m also trying to write articles for….. =)

Here’s a quick ‘tip’ article of mine that they recently published.