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
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.
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)
perl -MCPAN -e 'install UUID'
perl -MCPAN -e 'install UUID::Random'
You can then run your vmware-install.pl.
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.
- Install and update latest Ubuntu LTS
- Install and configure smokeping
- install and configure tcpping (required to be able to probe Diablo3 servers)
- install and configure Cactii
- Install and configure smokeping to integrate with Cactii
- Install VMware Workstation on temp laptop
- Import VM from Mac
- Configure VM as standalone device on home network
- Configure smokeping
- to smokeping home gateway
- to smokeping LNS
- to smokeping Internode border
- battlenet servers
- to smokeping some high visibility public internet things
- Configure cacti to poll Billion 7800NL (SNMP)
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.
A few quick links to the VMware maximums documentation that’s useful.
If you like lots of details you can read the official VMware Maximums doco here.
If you like the details reduced to two pages of condensed goodness you can read here.
I haven’t linked direct to the docs because they change a lot. I’ve linked to a point higher up in the path from which you can drill down on.
This one made me laugh.
If you need to resort to something like this I think you might want to:
- Consider changing (enhancing?) how your employees are selected/hired.
- Investing more money and effort in your training.