VMware Infrastructure PowerPack 2.1 released

Hot on the heels of the new release of the VMware VI Toolkit, I just finished uploading version 2.1 of the VMware Infrastructure Management PowerPack for PowerGUI.  This PowerPack facilitates management and automation of VMware Infrastructure servers using the VMware VI Toolkit with PowerGUI’s extendable administrative console.

Version 2.1 of the VMware Infrastructure Management PowerPack includes the following highlights:

  • Significant performance improvements when loading datacenters and clusters.
  • New top-level container nodes to facilitate viewing objects without having to browse into the Managed Hosts node.
  • Links allowing you to browse into log files from hosts.
  • Support for the VMware VI Toolkit 1.5 release.
  • VMotion support for virtual machines.

In addition to these changes, several links have been added and quite a few defects have been fixed.

You can learn more about this PowerPack, including version history and other details here.  You can download it from that location as well.

As always, feedback on this PowerPack and all others is welcome and appreciated.  If you want to see something in the PowerPack, just ask!  You can either contact me directly (see my about page), or you can post your request using the PowerGUI forums.  We’re listening!

Kirk out.

Share this post:

3 thoughts on “VMware Infrastructure PowerPack 2.1 released

  1. Every Time when i click on managed hosts i get this error:

    # ERROR: Unable to index into an object of type System.Management.Automation.Runspaces.ConsolidatedString.
    # At line:393 char:30
    # + if ($_.PSObject.TypeNames[ <<<< 0] -eq ‘CredentialCache’) {

    I have the newest Version from Powegui and the newst VMware Powerpack. Whats wrong?

    1. There seems to be a regression in PowerShell CTP3 that causes this issue. If you are facing this problem, please uninstall CTP3 and then install PowerShell v1, or move the VMware PowerPack to a machine with v1 installed and try again. For other users who have experienced this problem, reverting back to PowerShell v1 has resolved their issue.

      Kirk out.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s