Using genuine SSL certificates is good for security. It lets users know the device/host they’re connecting to is genuine, and prevents man-in-the-middle attacks. It also removes nasty warnings in the browser title bar. Continue reading
Wednesday Tidbit
Wednesday Tidbit: Adding the SQL Server Agent to a Windows Failover Cluster
Yesterday 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: configuring a clustered MSDTC for vRealize Automation 6.x
A few days ago I found I was unable to add reservations to my vRealize Automation installation. After finding VMware knowledge base article 2089503, I realised it was because I’d forgotten to configure the Microsoft Distributed Transaction Co-ordinator (MSDTC) on my new SQL cluster. Continue reading
Wednesday Tidbit: registering multiple vCenters with vCOPs
Recently, the company I work for has done really well in bringing onboard new customers – nearly all of which we have provided with a private cloud solution running on the VMware platform. Continue reading
Wednesday Tidbit: Using Cluster-Aware Updating to patch a Windows Server 2012 R2 Failover Cluster
Recently 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
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.
Wednesday Tidbit: Connecting vCenter to vCloud Air
Recently I signed up with VMware vCloud Air, as I want to use it as an endpoint for machines provisioned in the lab by vRealize Automation. Before I could get to that, I need to link my vCenter to vCA, which turned out to be trickier then I first imagined… 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
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
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