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

Building an advanced lab using VMware vRealize Automation – Part 9: Deploy and configure the IaaS platform

20150630 - vRAIn part 8 we installed and configured the vRealize Automation Appliance into the lab.

In this part we deploy and configure the IaaS platform.  This will involve building a Windows Server VM and installing the requisite components.  Once done, we will secure the platform with an SSL certificate from our Certificate Authority. Continue reading

Building an advanced lab using VMware vRealize Automation – Part 6: Deploy and configure the vCenter Server Appliance

20150630 - vRAIn part 5 of this series we created a Windows 2012 R2 Domain Controller to provide our authentication services for the environment.

In this part, we deploy the VMware vCenter Server Appliance (vCSA) 5.5. This will serve as the backbone to our infrastructure, as well as the endpoint for the majority of our VMware vRealize Automation deployments. Later in the series, we will configure other endpoints such as VMware’s vCloud Air or AWS. Continue reading

Building an advanced lab using VMware vRealize Automation – Part 5: Authentication services

20150630 - vRAIn part 4 of this series we configured two ESXi hosts to host our lab.  In this part we will setup a Windows Server 2012 R2 Core virtual machine and configure it as a domain controller in a separate root domain.  We will then configure a forest trust to our production domain so that our users can authenticate. 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 = ""
$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 $ } | select Name, @{ Name="ToolsVersion"; Expression={$}}, @{ 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