Vizioncore released the beta version of the Virtualization EcoShell.
The goal of the Vizioncore Virtualization EcoShell is to provide a freeware desktop application for novice and expert IT administrators leveraging Windows PowerShell scripts across their multi-platform virtual environments.
Fostered and supported by The Virtualization EcoShell Initiative (VESI) – an online community-driven Web site sponsored by Vizioncore – the Virtualization EcoShell is enhanced by the participation of community members through the exchange of new ideas, value-add services and extendable scripts. To become a member of the VESI community, please visit VESI Registration.
One of the best features is based on a script from Alan Renouf (vdiagram) and it’s called Generate vDiagram.
With this feature/script you can generate a Visio drawing of your VI environment. You can choose the following options:
If all the options are set to true, the script will generate three workspaces in Visio with three different vDiagrams. The diagram will look like this:
In this little video, you will learn how to post PoSH code to your blog, using Windows Live Writer. I learned this little trick in PowerGUI from Alan Renouf over at http://www.virtu-al.net/. Thanks again Alan.
Just click on the image below to open the screencast.com site.
The key new scenario which we wanted to support was creating custom PowerGUI-based consoles: branding them, locking them down, distributing to administrators (e.g. helpdesk), and then having automatically updated whenever you make changes to the central configuration.
The main pieces of this scenario were:
1. Lockdown mode: this allows you to disable and/or hide any functionality in the PowerGUI admin console. Simply open the file quest.powergui.Lockdown.xml in PowerGUI profile folder (%appdata%\Quest Software\PowerGUI). You can just replace all true with false (in that case users won’t even be able to click an action or change order of columns), or be more granular.
2. Central configuration update: Redirections.xml from PowerGUI profile folder lets you make PowerGUI pull its configuration and/or lockdown information from another location (e.g. file share). PowerGUI also checks for the configuration version, which lets you force the UI update whenever you change anything in your custom console.
[Editor] Dockable & re-arrangeable panes – now you can re-arrange the 3 panes (script, variables, and PowerShell console) any way you like, or even undock any of them and place it outside the main window – I myself am doing that to the PowerShell Console one, making it really large, and placing on my second monitor – makes so much difference!
[Debugger] Almost instant debugger start – this used to take significant time for larger scripts in our previous releases.
[Debugger] Ability to step into external scripts.
[Editor] Customizable toolbar and hotkeys – the first thing I did with that was placing Copy As HTML to the toolbar – this is the feature I am using all the time to blog my PowerShell code.
[Admin Console] Much improved column selection dialog box (the one you get when right-clicking the grid header and choosing More).