So wouldn’t it be great if we could somehow show the results of our Powershell VI Toolkit scripts inside the VI Client? Well, we can! Let’s take a closer look at Custom Fields / Custom Attributes. Hugo Peeters is is on the loose again ! :-) Read more at Īlthough I spend quite some time in the Powershell Command Line Interface, the main tool for managing the Virtual Infrastructure remains the VI Client. Tested management against Virtual Center 2.0, ESX 3.0x and 3.5, ESXi 3.5 and Virtual Server 2.0 (note: management of Virtual Center 2.0 requires version 1.0 of the VMware VI Toolkit).Ĭontinue reading 'PowerGUI’s VMware Powerpack available for download' ».Added single sign-on support (note that connecting to multiple hosts using the same username but different passwords is currently not supported, but we are working on that and will provide support for this soon).Improved the performance of many nodes, links and actions.Exposed many more VMware Infrastructure objects through topological views and through integration in the hierarchy.Added support for browsing the VMware Inventory hierarchy (includes Hosts and Clusters, Virtual Machines and Templates, Networks and Datastores), including being able to browse directly into the file system on the datastores.Reorganized the PowerPack structure to facilitate easier management of multiple hosts and to allow users to retrieve objects from one or more of the hosts they are managing whether they are already connected or not.

Just wanted to let you know that the download and updated information is available on the PowerGUI website at the following link.

Alternative to sapien powershell studio