Month: October 2017

Leave a reply

MacOS on vSphere ESXi 6.0

I recently installed MacOS High Sierra (10.13) on ESXi 6.0 for a developer I work with.  The steps I used were from a number of sources found on the InterWebs.

First off you need a Mac to download the installer. On the Mac, go to the App Store and and download MacOS.  While that is downloading, you’ll need to run the Unlocker script found at  Please read the notes thoroughly, and yes, a reboot of the host is needed.

After the installer is downloaded, you will need to create the ISO. The following steps are all done on the Mac

Mount the installer:
hdiutil attach /Applications/Install\ macOS\ High\ -noverify -nobrowse -mountpoint /Volumes/install_app

Then create a blank ISO
hdiutil create -o /tmp/HighSierra.cdr -size 7316m SPUD -fs HFS+J

Then mount the blank ISO
hdiutil attach /tmp/HighSierra.cdr.dmg -noverify -nobrowse -mountpoint /Volumes/install_build

Then restore the base image to the blank ISO
asr restore -source /Applications/Install\ macOS\ High\ -target /Volumes/install_build -noprompt -noverify -erase

copy the install dependencies
cp /tmp/HighSierra.dmg /Volumes/OS\ X\ Base\ System/

unmount installer image
hdiutil detach /Volumes/OS\ X\ Base\ System

convert to iso
hdiutil convert /tmp/sierra.cdr.dmg -format UDTO -o /tmp/HighSierra.iso

rename to iso and place on Desktop
mv /tmp/HighSierra/iso.cdr ~/Desktop/HighSierra.iso

Enjoy on non Apple Hardware!





Leave a reply

listing vms from a portgroup

I was recently asked to get a list of all VMs in a certain VLAN along with OS and IP address.  To do that…

get-vdportgroup “<name of port group>” | get-vm | get-guest | select vm, ipaddress, osfullname | ft -autosize

if you happen to be on a standard switch, replace get-vdportgroup with get-virtualportgroup -name <name of portgroup>


Leave a reply

Vendor mismatch has been detected

I recently updated my Nexus 9 to the nightly build of LineageOS 14.1 October 10.  The normal update went smoothly.  However, after rebooting, I was greeted with “A vendor mismatch has been detected.  Typiucally this means yopur vendor image is out of date.  Please ensure that your vendor image matches N9F27M”

According to Lineage, the nightlies are based on the October monthly updates from Google.  Which means the vendor image needs to be extracted from the factory image from Google and updated on the Nexus 9.

Once the vendor img has been extracted or downloaded, you’ll need to use adb fastboot to install it.

  • Connect to N9
  • adb reboot bootloader
  • fastboot devices
  • fastboot vendor vendor-flounder-n9f27m.img
  • fastboot reboot

N9 will reboot and you should no longer get that popup box

Leave a reply

Capturing FireFox with flash and VMware client integration plugins in an AppStack

I’ve recently created an AppStack that included FireFox 52.4.1 ESR with the flash plugins and the VMware Client Integration Plugin. I first created 3 separate AppStacks, FireFox, FlashPlugins and FireFox with the VMWare Client Integration Plugin. Running all these plugins seem to run fine. It’s when I created an all in one AppStack I encountered issues with the CIP.

After the AppStack was deployed, I ran FireFox and kept getting the following

Quite annoying, so after much searching I find out that the certificates generated during the provisioning process do not get captured by AppVolumes when you complete provisioning.  The ssl folder on the target system shows as single file:

It should look like this:

For this to work right, CIP needs to have the certs in this location. So to achieve this, I updated the FF AppStack, copied the CIP folder to C:\ProgramData, modified the allappvolattached.bat to include:

Powershell Copy-Item c:\programdata\cip\ c:\programdata\vmware\ -Recurse

ipconfig /flushdns

After re-provisioning the AppStack, I was step closer.  The pop-up was gone, but the CIP piece was still not working.

After much searching again, I made the following changes:

Turned off the proxy, using direct internet connection

toggled the following to false

and made the following changes to the host file vmware-localhost

::1 vmware-localhost

After a reboot, the CIP started working.

Another long day of troubleshooting an AppStack.

Good news is, I’m fairly confident in creating AppStacks and troubleshooting it now.

Leave a reply

VMC-AWS Pricing

Check out the pricing models for VMC-AWS. This looks promising, however, I’m a little weary about the data transfer charges.

Leave a reply

Power settings for ESXi hosts

About 2 weeks ago, I noticed in vRealize Operations Manager that one of my VDI hosts was experiencing higher than normal CPU contention. What was more interesting was that 90% of all VMs on that host had high cpu usage.  Moving a VM off the host, brought down CPU utilization, however, any VM moving to that host, started experiencing the same behavior.  After a few searches it turned out that the host’s power setting was set to balanced.  After setting the to Static High Performance Mode, the CPU contention dropped to below threshold and CPU demand on the host dropped as well.

So note to self and to others, when setting up hosts, set the power to high performance.  Luckily for me a reboot was not required.  This may be differ among vendors though.


Week of 9/24


Past 7 Days


You can see above where I made the change.

Leave a reply

Amazon LightSail and Bitnami WordPress Stack

After many hours of tinkering, below are the steps I’ve used to run 2 WordPress sites on one LightSail instance. This is assuming that you have DNS running and you have your A records set correctly.  In my case its techstuff and introspection.

I would’ve made my life a lot easier if I just went with /techstuff and /introspection.  But the having subdomains just sounds better.

After deploying the LS instance, I assigned it an Elastic IP.

Downloaded my SSH Key Pair.

Logged into my LS Instance
ssh -i “ssh_public_key_pair.pem” username@elastic_ip

Download the bitnami wordpress stack module.
wget “”

Changed the permissions on the file
chmod a+x “”

Run the installer
sudo ./ –wordpress_instance_name BLOG_NAME

Choose the language you wish to use

Choose the location of the Bitnami

Enter the root password for MySQL

Repeat this to have more than one WordPress site.

If you want to give your WordPress site its own subdomain, like, run the following from inside the newly created WordPress site

sudo ./bnconfig –appdomain SUBDOMAIN.DOMAIN_NAME

and that should be it.

Hope this saves time for anyone trying to run multiple WordPress sites on a single Amazon LightSail instance.  It took me a couple of days to stumble upon what I wanted to accomplish.

Any questions feel free to contact me.

Leave a reply

That didn’t take long

Newly-ish created VPS is getting attacked

Oct 9 13:28:52 ip-xxx-xx-xx-xxx sshd[2006]: Received disconnect from 11: Bye Bye [preauth]
Oct 9 13:28:53 ip-xxx-xx-xx-xxx sshd[2008]: reverse mapping checking getaddrinfo for niggacanttouchme [] failed – POSSIBLE BREAK-IN ATTEMPT!
Oct 9 13:28:53 ip-xxx-xx-xx-xxx sshd[2008]: Received disconnect from 11: Bye Bye [preauth]
Oct 9 13:28:54 ip-xxx-xx-xx-xxx sshd[2010]: reverse mapping checking getaddrinfo for niggacanttouchme [] failed – POSSIBLE BREAK-IN ATTEMPT!
Oct 9 13:28:54 ip-xxx-xx-xx-xxx sshd[2010]: Received disconnect from 11: Bye Bye [preauth]
Oct 9 13:33:08 ip-xxx-xx-xx-xxx sshd[2012]: Address maps to, but this does not map back to the address – POSSIBLE BREAK-IN ATTEMPT!

Leave a reply

Moved to Amazon Lightsail

I’ve moved to Amazon Lightsail from 1and1.  With the increase cost of running WordPress from 1and1, I’ve completely moved off it and am now running on Amazon Lightsail., along with DNS management by Amazon Route 53. My costs of hosting a WP site and DNS should drop dramatically


Amazon Lightsail is the one click offering by Amazon that gives users, developers or anyone that needs a simple virtual private server (VPS) with a easy to understand and predictable monthly rate, which is unlike EC2.  Keep in mind though that as the name implies this is targeted for “light usage”.  If you need something more powerful, you’ll probably need to go the EC2/ S3 route.

%d bloggers like this: