What’s new in PowerGUI 1.7

We have just posted version 1.7 on PowerGUI.org.

Once Darin is back from VMWorld he will update the changelog page at PowerGUI.org but here’s a quick What’s new from me.

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.

3. Ability to change the welcome page to something more meaningful for your organization.

And then there are multiple smaller changes:

4. Multiline comments for PowerShell v2 (<# #>).

5. Icons in the grid and dynamic nodes.

6. Multiple bugfixes based on reports we got from our community forums. We’ll hopefully follow-up on all of them next week.

Download the new version and let us know what you think.

As usual, for existing PowerGUI customers we will only turn on automated update in a week or so, so feel free to go to PowerGUI.org and download the new version right away without waiting for us.

Tags: , ,

4 Responses to “What’s new in PowerGUI 1.7”


  1. 1 McShell February 27, 2009 at 9:38 am

    I am using it right now, looking good so far.

    Minor issues still in this version:

    1) MSI Installer: INSTALLDIR property not supported? I am using PS scripts to install all my important apps, of course.
    $dest = …
    msiexec.exe /i “PowerGUI.1.7.0.686.msi” INSTALLDIR=$dest | Out-Null

    2) I’d like to change font for Console window as well – default is hard to work with on high res display

    3) Console autocomplete/IntelliSense bad for file navigation (works fine in PowerShell ISE)

    4) unnecessary languages should not install by default
    –> \PowerGUI>Remove-Item ar,da,el,es,fr,ja,ko,no,pl,pt-BR,ru,sv,tr,zh-CHS -Recurse

  2. 2 McShell February 27, 2009 at 9:48 am

    Ok, regarding issue 1) I just found info by accident:

    http://wiki.powergui.org/index.php/Silent_Installation

    Property name “PF_POWERGUI” is hard to guess but at least it’s in the wiki.

    msiexec /quiet /i C:\PowerGUI.1.6.1.639.msi PF_POWERGUI=c:\PowerGUIInstallFolder

  3. 3 Dmitry Sotnikov February 27, 2009 at 12:03 pm

    Thanks for the comments!

    First and foremost, please-please-please, submit such reports through the forums at powergui.org: http://powergui.org/forumindex.jspa?categoryID=55 – this would ensure that they get into our change request tracking system.

    Now to the points you raised:

    1. OK, glad you found the documentation.

    2. Logged that as a change request. By the way, I assume that what you want is just make the PowerShell Console pane use the same font as the script editing tabs, correct? I don’t really see a reason for these to be separate settings, do you?

    3. Could you please post to the powergui.org forums specific repro steps for the cases when file path intellisense does not work properly for you?

    4. Not sure I see a reason why not to install all languages by default. These packages are tiny. If you really care about these kilobytes – you can turn them off during the installation process but most people won’t even notice the disk space they consume. On the other hand, you never know which languages are going to be needed (especially in a multi-user environment.)

    Dmitry


  1. 1 Episode 61 - Joe Pruitt from F5 and the ABCs of PowerShell « PowerScripting Podcast Trackback on March 3, 2009 at 3:25 am

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 )

Google+ photo

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

Connecting to %s




My Recent Tweets

Legal

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

February 2009
M T W T F S S
« Jan   Mar »
 1
2345678
9101112131415
16171819202122
232425262728  

%d bloggers like this: