PowerGUI inside VI Client

PowerGUI now plugs into VMware Infrastructure Client. To be precise, starting with version 1.5.1 the setup has VMware Client Integration component which registers both PowerGUI and PowerGUI Script Editor as VI Client plugins.

PowerGUI admin console and script editor can be started right within VI Client

PowerGUI admin console and script editor can be started right within VI Client

The cool thing is that when you start them from VI client they automatically inherit your current connection to VMware infrastructure, so all your VMware management scripts or PowerGUI nodes/actions just work without asking you to connect first – no more additional prompts, having to type the password, etc. – you are already in and everything just works!

I have also updated the VMware PowerPack so it is compatible with the RTM version of VI Toolkit and PowerGUI 1.5.1 – so do not forget to download it too.

Enjoy and please submit your feedback so we keep making the pack even better!

Tags: , , ,


9 Responses to “PowerGUI inside VI Client”

  1. 1 halr9000 July 31, 2008 at 2:02 pm

    Nice! I love the single signon!

  2. 2 jonatj August 1, 2008 at 1:42 am

    Thanks for your work Dmitry. I know this is a beginner’s question, but I promise I tried the VMTN forums and documentation first.

    I installed all the components required, including the VMware powerpack and started up PowerGUI, configured the Connect script with my VirtualCenter server hostname and my login. So far so good, I think it connects me okay. But then I go to the next PowerShell Code tab and the last line says:

    “WARNING: Could not connect using the requested protocol.”

    And every other cmdlet gives me the error:

    “Value cannot be null. Parameter name: key”

    The VMware VI Tookit (Windows) works fine when I type:

    Get-VIServer or Get-VC

    Although I did see this message:

    “There were one or more problems with the server certificate:

    * The certificate’s CN name does not match the passed value.”

    Any suggestions or could you point me in the right direction.

    Many Thanks,


  3. 3 dmitrysotnikov August 1, 2008 at 11:49 am


    Check to make sure you are using the right protocol – e.g. HTTPS instead of HTTP.

    Also, if you start PowerGUI from the VI Client Plugins menu you do not have to use Connect at all and can click Virtual Machines and other nodes right away.


  4. 4 David Moravec August 29, 2008 at 11:19 am

    Also be careful if you are connection from client PC and your proxy server needs authetification. I had the same problem so I added server IP to proxy exclusions.


  5. 5 NiTRo November 2, 2008 at 10:58 pm

    Hi Dmitry,

    Is it planned to add a template deployement function in this powerpack ?

    BTW, the virtual machines function are really great !


  6. 6 Dmitry Sotnikov November 12, 2008 at 11:06 am


    Yes, it is on the roadmap. We are currently building a good VI lab so we can make the VMware powerpack much more feature rich.

    The good thing is that you do not need to wait for us! If you know (or can find) the appropriate cmdlet – go ahead and add the action you need.

    Demos on this page should help: http://powergui.org/documentation.jspa

    Especially this one: http://powergui.org/shares/powergui/sbin/docs/How_to_create_a_PowerPack/How_to_create_a_PowerPack.html


  1. 1 PowerGui integrates with VI Client « Vive Le Velo Trackback on July 31, 2008 at 9:41 am
  2. 2 Episode 36 - Jonathan, Marco, Jonathan, Marco etc… « PowerScripting Podcast Trackback on August 4, 2008 at 3:10 am
  3. 3 PowerPack format adoption « Dmitry’s PowerBlog: PowerShell and beyond Trackback on September 1, 2008 at 10:03 pm

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 )

Twitter picture

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

Facebook photo

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

Connecting to %s

My Recent Tweets


The posts on this blog are provided “as is” with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer - WSO2 or anyone else for that matter. All trademarks acknowledged.

© 2007-2014 Dmitry Sotnikov

July 2008

%d bloggers like this: