“Shockwave Flash has crashed” workaround for vSphere Web (Flash) Client | virtuallyGhetto


Im using the vSphere Web Client everyday at the moment and will also preference the HTML5 version over the Flash (phtoowe) version.

Chrome 61.0.3163.100 breaks Flash though due to a patch for an undisclosed zero-day which was in use in the wild. Impacts Chrome on Mac and Windows.

See the post below from William Lam over at VMW.

On Saturday, I started to notice that logins to the vSphere Web (Flex) Client stopped working with Google Chrome. Upon a successful logon, it would immediately crash with “Shockwave Flash has…

Source: “Shockwave Flash has crashed” workaround for vSphere Web (Flash) Client | virtuallyGhetto


Adding your vCenter Web Client as a search provider in Chrome


Most browsers these days offer a function that allows you to add other search engines to them. This function allows you to quickly search for stuff directly from your web browsers search field instead of having to open up the site directly, type in what you want and press enter.

In this article I’m going to show describe how to add your vCenter 6.5U1 HTML5 client as a custom search engine in Google Chrome.

This will allow you to search for vCenter objects directly from Chrome without first opening the HTML5 Web Client.

What you need

  • Access to an HTML5 vCenter Web Client (vCenter 6.5U1 on the VCSA was used to write this.)
  • Google Chrome (Chrome 60 was used at the time this was written)

Find your vCenter Web Client Search URL

  • Browse to your HTML5 vCenter Web Client and sign in. Its usually something like ​https://{FQDN}/ui` where {FQDN} is the URL for your vCenter Web Client.
  • From the banner at the top of the page, click on `Menu` and select `Search`.
  • Enter the name of a VM you want to search for and press `Search`.
  • Copy the URL from the address bar in Chrome. In this example we have something like this. I’ve replaced https://{FQDN}/ui/#?extensionId=vsphere.core.search.domainView&query={SEARCHTERM}&searchType=simple

Add a custom search provider to Chrome


  • Open a new Chrome tab or Window, enter your keyword and the object name you want to search for.
  • Chrome will return the vCenter Web Client search page with the term you entered.
  • $profit.

VMware Fusion 8.5.X – Windows 10 – Shared Folders AWOL


Updated: 20170228

The problem occurred again. This time, an uninstall and reinstall of VMware Tools didn’t fix the issue.

The fix was to:

  • Open the VMware Fusion Sharing preferences and leave “Enable Shared Folders” ticked but untick all the “Mirrored Folders”.
  • When prompted, log off and log back on.
  • Open the VMware Fusion Sharing preferences and select the folders you want under ‘Mirrored Folders’.
  • You will again be prompted to log off. Log off and then log back on.

The mirrored folders should be accessible again.


VMware Fusion has a nifty feature called ‘Shared Folders’ thats lets you access data on the underlying Mac OSX host from within the guest OS. Fusion must be configured to enable it and VMware Tools must be running inside the guest for it to work.

Recently, mine stopped working. I hadnt disabled the feature in Fusion and nothing lept to mind about other changes I could have made that caused the problem.

Today I had some spare cycles to dig into the cause of the problem and find the fix. See the source below from Nov 2015.

TL;DR: Windows Update nerfs a registry value which VMware Tools uses. The fix was simple, uninstall VMware Tools, reboot, install VMware Tools, reboot.


Source: Shared Folders – Windows 10 upgrade from 15.11. | VMware Communities

Windows Update Standalone Installer Error


I had to install PowerShell 3.0 on my Windows 7 SP1 VMware Fusion 8.5 VM earlier today and grabbed the installer from https://www.microsoft.com/en-us/download/details.aspx?id=34595. The download was done from Chrome on my Mac and saved to my Mac’s Downloads folder.

I have Shared Folders running in Fusion so I have direct access to the Downloads folder from Windows via the Z:\ drive presented to Windows.

When I ran the .msu file from z:\downloads I would receive an error which said:

Installer encountered an error: 0x80070003
The system cannot find the path specified.


The fix is to copy the .msu file to a VMDK based disk in the VM and run it again.



Install vSphere CLI on Ubuntu 14.04 LTS


ARGGGH. What a painful experience this was.

Mainly due to unresolved dependancies in the vmware-install.pl script.

After a half a day shaving this yak, the method to fix the dependancies is:

sudo apt-get install libxml-libxml-perl libdevel-stacktrace-perl libclass-data-inheritable-perl libconvert-asn1-perl libcrypt-openssl-rsa-perl libcrypt-x509-perl libexception-class-perl libarchive-zip-perl libpath-class-perl libtry-tiny-perl libclass-methodmaker-perl libdata-dump-perl libnet-inet6glue-perl

Lastly, you need to install UUID and UUID::Random from CPAN. There doesnt appear to be suitable packages in 14.04.

  • install cpan (find your own link to an article on doing this on Ubuntu)
  • Then:
perl -MCPAN -e 'install UUID'
perl -MCPAN -e 'install UUID::Random'

You can then run your vmware-install.pl.

Home Internet Monitoring Appliance


My home internet has been pretty flakey of late and I needed a way to monitor the performance of the connection over long periods of time so that I could gather evidence to escalate to my ISP for support and troubleshooting.

Due to the absence of a suitable machine at home to run the tools on I decided to build an Ubuntu VM with smokeping and Cacti. This would allow me to build the environment quickly and then move the VM to a temporary laptop running VMware Workstation at home.

The following steps describe the sequence of events and references I used to complete the work.

Microsoft FUD vs VMware round 2


There’s a new Microsoft & VMware drama brewing. Before I detail it though here’s a good recap of the first one.

This new drama is about MS Exchange 2010 DAGs with virtual servers on VMware HA.

Exhibit 1a and 1b are the VMware guides for deploying this solution.

Exhibit 2 is the Microsoft response saying that the VMware best practice guides are an unsupported solution.

Exhibit 3 is VMware’s riposte telling MS to suck it up, it works, get your act together and support it.