Tonight I have published a new version of the VMware Infrastructure Management PowerPack. This release (version 2.4.0) is the first release that provides near 100% feature parity between both PowerGUI and the Virtualization EcoShell. I say near 100% feature parity because PowerGUI supports displaying progress dialogs during calls to Write-Progress but the Virtualization EcoShell does not, so PowerGUI users have a minor leg up over the Virtualization EcoShell experience. Depending on what environment you are coming from, you will notice some of the following improvements to this PowerPack:
- Visio 2010 support for vDiagram functionality
- Charts for virtual machines, datastores, and resource configuration data
- Progress bars during the rendering of diagrams created with the vDiagram functionality
- Improved layout in the nodes in the tree
- Simplified connection logic, making it easier for you to reuse scripts generated by the PowerPack
- Additional minor bug fixes
Note that version 4.1 of the VMware PowerCLI is not supported with this release at this time, due to a number of issues. For now the only supported version of the VMware PowerCLI is version 4.0 U1.
If you are an existing user of this PowerPack, you will automatically get notified about the new version. If you haven’t looked at this PowerPack yet and you manage VMware vSphere, Virtual Center, ESX, or ESXi hosts, I strongly encourage you to give this PowerPack a try. You can download it here. It provides an excellent management experience over those VMware hosts, and it’s free!
As usual, many of the enhancements we add in these releases are based on customer feedback on the PowerGUI Forums. If you’d like to see more improvements to this PowerPack, please speak up and let us know on the forums. We’re always listening!
Kirk out.
| Share this post: |  |
 |
 |
 |
 |
 |
 |
Poshoholic 
[…] has just released a new version of the VMware PowerPack which now supports Visio […]
Hi!
I am a very keen user and have used Powergui with the fantastic powerpacks. I have come across an issue and would greatly appreciate your help.
After installing Powergui and the relevant powerpack I can’t generate the Visio diagram using the Vdiagram feature. I have Vision 2010 and 2013 both installed and it fails on both the occassions, The error I get is” Visio 2003 or later is required. At C:\Users\username\AppData\Roaming\Quest Software\PowerGUI\Scripts\4603dc99-244c-4e87-b4ae-b4f0706b4103\VMware.ps1:5184 char:3 + throw $(New-Object System.InvalidOperationException ‘Visio 2003 or later is re … + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I am using PowerCLI 5.5 R2
Can you please help?
Thanks
Hi Rehman,
First, I need to let you know that I haven’t looked at that PowerPack, or PowerCLI for that matter, in quite a while. I don’t use PowerGUI anymore, and I haven’t been involved with PowerGUI for quite a few years now.
That said, there are a few things that I recall that may help you. First, have you opened Visio with the user account that is being used to run the script? This is an absolute requirement because it creates Registry keys/values that are necessary for the Visio functionality to work. If you’ve done that and it still doesn’t work, could you post the rest of the error message that you are seeing? The information in that error (assuming you still get that error) may help me come up with other ideas.
Thanks!
Kirk out.
Hi!
Thank you for your response. I am using my login to run powergui and am using the same account to run vdiagram. The error which I get is Visio 2003 or later is required. At C:\Users\%username%\AppData\Roaming\Quest Software\PowerGUI\Scripts\4603dc99-244c-4e87-b4ae-b4f0706b4103\VMware.ps1:5184 char:3 + throw $(New-Object System.InvalidOperationException ‘Visio 2003 or later is re … + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have removed everything (registry included) and re-installed to see if I can isolate the problem. I have opened Visio with my login as well.
I have also got Visio 2010 and have got Powercli 5.8 and latest version of Powergui.
Hi Kirk, I have managed to fix this, after dabbling through the error I noticed the script didn’t had the variable for Visio 2013, modified that and voila it works now.
Thanks,
Excellent, I’m glad you got it working Rehman. Thanks for letting me know!
Kirk out.
Just to clarify I have got Visio 2013 and 2010 both.
Hello Rehman
Can you tell me, what and where you changed the variables in the script?
Thanks a lot
Nadine
Hi Nadine, I don’t exactly recall as it has been some time now, and unfortunately didn’t had the opportunity to document it. I came across couple of post on the quest forum for powergui and it was making the changes in the powerpack (most likely) so your first port of call should be the quest forum?