One of the announcements during VMworld 2010 in San Francisco that perhaps got a bit obscured by the other “big” announcements, was the release of Onyx 2.0. For those of you that hadn’t heard of Project Onyx before, this nifty little tool captures all SOAP traffic that is passed between your vSphere client or PowerCLI session and the vCenter or ESX(i) server to which you are connected.
And that’s not all, the Onyx program will translate the captured SOAP traffic into PowerShell code. This allows you to see which vSphere APIs are used and how parameter objects for these methods are constructed.
There was another interesting question on the PowerCLI community. Mike was wondering if it would be possible to change the VMware Tools scripts with a PowerCLI script. As far as I can see there are two options available with the VMware Tools scripts.
- You can run the default scripts that are installed on the guests when you install VMware Tools
- You can use Custom scripts and you have to specify the path of these scripts to VMware Tools
To use the 2nd option you will need, as William already pointed out, the VIX APIs.
But if you can live with the first option, and reuse the default scripts, the current PowerCLI build has all you need.
Read more…
A question I get quite regularly is what tools and utilities do I use for developing PowerShell and PowerCLI scripts. The following list should shed a bit of light. A warning, this is my personal selection of tools and utilities and it is not my intention to convince anyone to switch to any of the tools mentioned. Read more…