VI Toolkit

VI Toolkit Extensions

Today I tested the VI Toolkit extensions.  The VI Toolkit extensions are cmdlets that makes your life easier. Here are some functions of what the cmdlets can do:

6a00d8341c328153ef01053565af86970b-800wi

The VI toolkit extensions require PowerShell V2 CTP 2 and the VI Toolkit. The VI toolkit extension can be downloaded @ http://www.codeplex.com/vitoolkitextensions

Example:

list all VMs by name and list the size of the snapshots

– Open VI-toolkit

– Connect-VIserver VCservername

– To add the extension, use the following command:

Add-Module “D:\Scripts\viToolkitExtensions.psm1”

Get-VM | Get-TkeSnapshotExtended | select Name, VM, SizeMB

Output:

image

Winners VI toolkit scripting contest

The winners of the VI toolkit scripting contest are announced:

– The first prize goes to LucD for his Guest Provisioning System script.

– The Second prize goes to tzamora for his VMware Infrastructure Power Documenter script.

– The Third prize goes to Dan Baskette with his PowerVDI script.

The Healthcheck script that i created has not won 🙁

You can read the rest @ the VMware Powershell Blog

For all VI toolkit contributions check this link

VI Toolkit Update 1 released

 

VMware has released VI Toolkit Update 1. There where performance problems with the get-VM command.

Some users had reported slowness when using the Get-VM cmdlet. The reason turned out to be an odd quirk in querying some types of network adapters, so many people weren’t affected at all. On the other hand, if you were affected, it was pretty annoying. To address this we’ve released Update 1 of our toolkit. If you’ve had trouble with Get-VM, download it things will go a lot smoother. One user reported that his queries went from more than 5 minutes to just over 10 seconds — a world of difference!

This is the only change we made to the toolkit, so don’t expect lots of new functionality when you download, you’ll have to wait a bit longer for that. If you haven’t had any trouble with 1.0 it’s perfectly fine to keep using it until the next release.

Also, many of you are probably eagerly anticipating the results of our scripting contest. I want to thank everyone for participating and point out that the entries are now open to the public. Check it out, there’s a lot of really great stuff in there.