I don’t believe that PowerCLI 5.1 is yet officially supported on Windows 8, however that’s where I wanted to run it. While carrying out the installation I hit this issue, i.e. .NET Framework 2.0 was not installed as a pre-requisite. This is because PowerShell 3.0 on Windows 8 uses .NET 4 and no longer has .NET 2.0 as a requirement.
To install .NET Framework 2.0 in Windows 8 you need to turn on .
Fellow London VMUG regulars and vExperts Barry Coombs and Mike Laverick have recently self published a new title Building EUC Solutions with VMware View. This book covers the most recent release of View 5.1 and having been privileged to help review one of the chapters and already get myself 1/4 the way through the book it is looking to be a phenomenal effort.
The authors have a lot of real world experience and translate this into the book.
The public vote for sessions at VMworld opened today and there are a crazy number of great sessions to choose to vote for. I decided to give it a go myself this year, so have teamed up with my good buddy Hal Rottenberg to put forward the session 2112 Transforming Your Automation Scripts with Advanced PowerShell / PowerCLI. If you would like to see us present it, then please consider voting it up!
In an Active Directory environment its typical for client machines to use a local domain controller as their time source, domain controllers with the PDC emulator for the domain and the PDC emulator for the root domain to synchronise time with an external source. In most circumstances the aim is to keep the time synchronised within a 5 minute tolerance level, this will ensure there are no issues with Kerberos authentication which has the 5 minute tolerance as part of its requirements.
I experienced a vSphere HA event where VMs restarted on other hosts and I was requested by management to confirm which VMs had restarted. Details are stored within vCenter events, but trawling through those manually for multiple VMs would be pretty tedious. Enter of course, PowerCLI. The Get-VIEvent cmdlet enables you to search through the events, but to a certain extent it kind of helps if you know what you are looking for since there is so much information to look through.
If you’re running your vSphere deployment on HP kit then there’s a pretty good chance you use the HP Customized ISO Image for installation, for example this one for ESXi 4.1 U1. These customised images typically contain HP management tools and drivers and are great for saving time during the installation process. Naturally you will be upgrading ESXi at some point, but it’s important that you also keep the HP part up-to-date too.
I remember back to a London VMUG long ago a presentation about differences to watch out for between ESX and ESXi during the version 3.5 days. The one that got most people looking around at each other saying “oops, I don’t think we knew that” was configuring a Syslog server for your ESXi servers. vCenter 5 now includes it’s own built in Syslog server so there’s no excuse. Alternatives, such as Kiwi Syslog Server, are available if you don’t want to use the vCenter 5 syslog server.
VMUG, vBeers, vLunch….whatever the occasion, there are always some great conversations and I particularly enjoy finding out what other people are up to in their environments. During vLunch last week, I was talking with Ed Grigson and he asked whether it was possible to use PowerCLI to remove vCenter Plugins that have got into an orphaned state, i.e. the uninstall process did not remove the vCenter plugin. VMware KB article 1025360 details a process whereby you can clean these up by navigating to the vCenter Server with a web browser.
The vCheck PowerCLI script from Alan Renouf is one of the most popular scripts for managing vSphere with PowerCLI. Its an amazing piece of work and I think has in its own small way helped the success of PowerCLI itself, by showing the kind of information it is possible to retrieve from vSphere and present in a great format. The number of people I talk to who use it and the large scale organisations that you would think spend thousands of pounds on expensive monitoring tools that have it as part of the daily monitoring checks never ceases to surprise me.
I recently needed to provide a high level capacity overview per VMware cluster looking at some metrics of interest that were being used as a guide to the capacity state of a cluster. Note: these are by no means definitive or the ones you should be using in your environment, but for these purposes they met the requirements. The metrics I looked at per cluster were the ratio of vCPUs to pCPUs, the amount of Effective, Allocated and average Active Memory and the amount of Free Diskspace.