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

Dmitry

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

BTW, the virtual machines function are really great !

Thanks

Dave

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.

Dmitry

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,

jonatj