William Lam

Want a free VMware Workstation 10 License?

03.14.2014 by William Lam //

Last week, I gave away seven free VMware Fusion 6 Professional license worth a total of $903 USD to seven lucky readers as part of a fun give away for my fellow Twitter followers. I know a couple of you who were asking about VMware Workstation licenses and it looks like the Workstation team has just answered that call 🙂

I have in my hands, seven VMware Workstation 10 licenses worth a grand total of $1,743 ($249 USD per license). I would like to give a big thanks to the VMware Workstation team for donating these seven licenses to me so that I could give away to my Twitter followers. If you are interested in learning more about VMware Workstation or have any feedback/questions for the Workstation team, you can follow and interact with them on Twitter at @vmw_workstation. One pretty neat feature of Workstation is the ability to manage your ESXi hosts including Free ESXi which really could come in handy.

So, if you want a super easy way to win a free VMware Workstation 10 license key, then CAREFULLY READ through the instructions below to see how you can score a free Workstation license!

How to Win:

You must be following me on Twitter, I am at @lamw and I will be contacting winners through Twitter.
Leave a short comment on this post on what this VMware Workstation license key would enable you to do, whether that is solving a particular problem or challenge.
What is the one feature that you are most excited about for new users or what new feature would you like to see for existing VMware Workstation customers.
Include your Twitter handle in the comment
Must not be a VMware employee, I will check

Simple, right? I will randomly select seven winners from the list of comments in one weeks time, so make sure you leave your Twitter handle in the post else you will not be eligible to win. This is open to everyone, you do not need to live in the US to win.

Winners:

@Rob_Coote
@phil_wiffen
@MaureenCioe
@billyboskovski
@k00laidIT
@Hazy2k10
@lukeaw

Required ESXi advanced setting to support 16+ node VSAN Cluster

03.13.2014 by William Lam // Leave a Comment

This evening I came across a very interesting VSAN knowledge base article KB 2073930 which states: to support a VSAN Cluster with greater than 16+ nodes, an ESXi Advanced Setting must be configured. The wording in the current KB is a bit confusing as it mentions the advanced setting must be applied to all hosts and then it mentions it should only be applied to the "additional" hosts. I have reached out to engineering and confirmed that the setting should be applied to ALL ESXi hosts and the KB will be corrected shortly. After applying this setting, you will also need to reboot your ESXi host for the changes to take affect.

The advanced setting we are interested in is called CMMDS.goto11 and you can check its current value by running the following ESXCLI command:

esxcli system settings advanced list -o /CMMDS/goto11

The following ESXCLI command will configure the required setting (default it is 0):

esxcli system settings advanced set -o /CMMDS/goto11 -i 1

The reason this setting is disabled by default is that it does consume a tiny amount of memory, we are talking about sub ~150MB per ESXi host. Though this amount is extremely small, the VSAN Engineers wanted to be very cognizant of smaller VSAN deployments and not have to require additional resources if it is not necessary. In my opinion if you plan to eventually scale beyond 16+ nodes in a VSAN Cluster and you can afford the additional memory overhead, then I would recommend enabling this setting as part of your default configuration so you do not need to do it later. If not, you can always do it later, but you know how that goes 🙂

To assist with this change, I have created two scripts: vSphere SDK for Perl and PowerCLI which will automate the configuration of this advanced setting for ALL ESXi hosts within a VSAN Cluster.

Disclaimer: These scripts are provided for informational and educational purposes only. It should be thoroughly tested before attempting to use in a production environment.

You can download the sample vSphere SDK for Perl script called: enable16PlusVSANNodeSupport.pl

Here is an example of how you would run it:

./enable16PlusVSANNodeSupport.pl --server vcenter55-1.primp-industries.com --username root --cluster VSAN-Cluster

UPDATE (07/27/17) - Here is a PowerCLI script called VSANLargeClusterAdvSettings.ps1 which contains two functions (Get-VsanLargeClusterAdvancedSetting and Set-VsanLargeClusterAdvancedSetting) for retrieving and updating the necessary ESXi Advanced Settings to enable large vSAN Clusters for ESXi hosts running on 5.5, 6.0 & 6.5. There are two different KBs depending on the version of ESXi, please see https://kb.vmware.com/kb/2073930 and https://kb.vmware.com/kb/2110081 for more details.

Finally, some fun VSAN trivial from the engineering team. You may have noticed the advanced settings is called "goto11" which I was initially scratching my head over on why the engineers would name it that. I initially though it was either binary 11 OR it was a literal GoTo statement. It turns out, the answer can be found in this YouTube video here. Thanks to Dinesh Nambisan for sharing this awesome little tidbit. I wonder what other surprises lies in the code 🙂

Automating Horizon View deployments using VCT & cURL

03.11.2014 by William Lam // 1 Comment

Last week I spent a couple of days playing around with the new Horizon View Configuration Tool (VCT) Fling and as part of my "exploration" of VCT, I needed to re-run the deployment. Going through the guided wizard the first time was fine, but if you needed to do that 5-10 times, then it was not very fun. Since VCT was a simple web application, I decided to fire up one of my favorite tool, Firebug to do some poking around.

It turns out the payload request was actually very simple and it contains all the variables for each of the parameters that a user would specify through the UI and a single HTTP POST request is then sent to the web application for deployment. I took all the variables and created a simple shell script that a user can easily edit without having to worry about fat-fingering on the UI as there is no form validation at the moment and then send the POST request using my other favorite tool cURL.

Disclaimer: These scripts are provided for informational and educational purposes only. It should be thoroughly tested before attempting to use in a production environment.

You can download the script here called automateVCT.sh

Before running the script, you will need to edit the variables for your environment and if you have an existing Active Directory server, then there are some variables that you can leave off. Towards the bottom of the script, there is an infinite loop that will run to continuously to check the current status which is then printed on the screen every 10 seconds. For practical use, you will probably want to change the timing to something a bit longer like every 5 minutes for a status.

Here is an example of executing the script:

As you can see from the screenshot, once the request has been accepted by VCT, the status will be printed on the screen which is the same status shown in the UI. If everything was successful, you should eventually see the status display the IP Address of your Horizon View environment like the following:

This script really came in handy for testing VCT and I thought it would be great to share it with the community so you can automate the deployment of your Horizon View environment using VCT!