In vCenter, I’ve always found it strange that by default if an ESXi host deviates from its host profile, then the only notification an administrator would receive is a red cross in the GUI. I don’t know about you, but we regard that as a serious issue, as any deviation could lead to unplanned downtime. Continue reading
PowerCLI
Wednesday Tidbit: Using PowerCLI extensions fling to configure vFlash
A 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.
Building an advanced lab using VMware vRealize Automation – Part 10: Configure tenants
In part 9 we installed and configured the IaaS platform for our lab.
In this part we discuss tenants. We configure the default tenant, and explain why you might need more than one. Continue reading
Building an advanced lab using VMware vRealize Automation – Part 9: Deploy and configure the IaaS platform
In 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
Wednesday Tidbit: Test an SRM Recovery Plan using PowerCLI
In the last Wednesday Tidbit I showed how to protect a VM using SRM and PowerCLI.
In this one I show how to test a failover plan so that in the event of a disaster we know what to expect. Once the failover has been performed and recorded as successful, I will back it out. Continue reading
Building an advanced lab using VMware vRealize Automation – Part 8: Deploy and configure the vRA Appliance
In part 7 we configured SSL certificates for our newly deployed vCenter Server Appliance. In this part, we deploy the vRealize Automation Appliance into the lab.
After deployment we will perform a number of tasks to enable the appliance to work in the lab environment.
Continue reading
Wednesday Tidbit: Protect a VM using SRM and PowerCLI
When it was released last year, PowerCLI 5.5 brought with it the ability to do basic management of Site Recovery Manager. Whilst by no means trivial to configure, the functionality is there for when needed.
In this tidbit I will show how to connect to SRM, list the protection groups and add a VM to one. Continue reading
Building an advanced lab using VMware vRealize Automation – Part 6: Deploy and configure the vCenter Server Appliance
In 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
In 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
I 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