vSphere: Get ESX Server Serial Numbers
KB ID 0001670 Problem A few weeks ago I needed to sort out some extended warranty for a customers servers. To do that I needed the serial numbers of those servers, (a mixture of IBM/Lenovo and Dell Servers). As I didn’t fancy a drive to two different datacenters, I wanted to try and get them programatically. Solution After some searching I came across a post by one of my old EE buddies LucD with exactly what I needed. I’m...
VMware: List/Audit VMware Tools Versions
KB ID 0001618 Problem If you want to either audit, or simply get a quick list of which of your VMs are running which versions of VMware Tools, here are a few options. Show VMware Tools Versions With PowerCLI Use the following Syntax Get-VM | Select-Object -Property Name,@{Name=’ToolsVersion’;Expression={$_.Guest.ToolsVersion}} Like so; Show VMware Tools Versions With VI Client Using HTML Client To Show VMware Tools...
PowerCLI: Connect-VIServer Certificate Errors
KB ID 0001603 Problem When attempting to connect to a vCenter or ESXi host, you see the following error; Connect-VIServer : {Date} {Time} Connect-VIServer Error: Invalid server certificate. Use Set-PowerCLIConfiguration to set the value for the InvalidCertificateAction option to Prompt if you’d like to connect once or to add a permanent exception for this server. Additional Information: Could not establish trust relationship...
PowerCLI: vMotion Multiple VMs
KB ID 0001585 Problem vMotioning one VM is pretty simple to do; Get-VM VM1 | Move-VM -Destination (Get-VMHost ESX-02.pnl.com) And moving ALL the VMs on one host, to another is pretty straight forward also; Get-VMHost ESX-01.pnl.com | Get-VM | Move-VM -Destination (Get-VMHost ESX-02.pnl.com) But what if you have a list of VMs you want to move, and you are too lazy, (sorry too skilled), do do them manually or one at a time? Solution...
vSphere: Migrating vSwitch PortGroups and VLANS
KB ID 0001578 Problem Over the past few weeks I’ve been doing some work for a client that involves me adding some new ESX hosts. These will be setup the same as their existing ESX hosts. That’s fine, but they use standard vSwitches and have A LOT of port groups and VLANs. I could sit and create them all manually, and tag them onto the the correct VLANs, but something that’s boring and repetitive is better solved with...