Wednesday Tidbit: Adding the SQL Server Agent to a Windows Failover Cluster

20150916 - 1Yesterday I decided it was time to patch my VMware vCenter 5.5 hosts to the recently released Update 3. As I make use of properly configured SSL certificates, each component (SSO, Web Client, Inventory and vCenter Server) has to be installed separately. However when I came to install the last one, I ran into an issue. Continue reading

Wednesday Tidbit: Using Cluster-Aware Updating to patch a Windows Server 2012 R2 Failover Cluster

20150820 - 1Recently I built a Windows Server 2012 R2 Failover Cluster to run my SQL, file services and Certificate Authority workloads. For a number of reasons (mentioned in the article) I decided to build it on the Server Core edition of Windows.

Whilst this offers numerous advantages, simplicity isn’t always one of them. One example of this is patching. Continue reading

Wednesday Tidbit: Using PowerCLI extensions fling to configure vFlash

20150713 - PowerCLIA couple of weeks ago VMware released the PowerCLI Extensions Fling. This gives users early access to experimental PowerCLI functionality in the form of modules.

Whilst the highlight of the release was undoubtedly Instant Clone (aka VMFork), a bunch of cmdlets appeared for configuring vFlash on hosts.  Fortunately for me, I recently had cause to use them.

Continue reading

Wednesday Tidbit: List VMs and their VMware Tools versions

20150713 - PowerCLII recently upgraded a customer’s vCenter to 5.5 along with the ESXi hosts from 5.0 to 5.5.  After the work was complete, I needed to work out which virtual machines needed their VMware Tools upgrading, as while they were all out of date… some were more out of date than others.

With eighty VMs in the cluster, manual checking was out of the question.  Again PowerCLI came to the rescue.

Connect to the vCenter:

$vc = "yourvcenter.company.local"
$credential = Get-Credential
Connect-VIServer -Server $vc -Credential $credential

Use the following code to list the VMs and the tools version number:

Get-VM | where {$_.powerstate -ne "PoweredOff" } | where {$_.Guest.ToolsVersionStatus -ne "guestToolsCurrent"} | % { get-view $_.id } | select Name, @{ Name="ToolsVersion"; Expression={$_.config.tools.toolsVersion}}, @{ Name="ToolStatus"; Expression={$_.Guest.ToolsVersionStatus}}

guestToolsIsUnmanaged means tools are either not installed or are “3rd-party/Independant”

Finally, disconnect from the vCenter:

Disconnect-VIServer $vc -confirm:$false