Rebranding PowerGUI console

Here’s a script which allows you to replace PowerGUI’s default welcome screen to any page of your own.

This is of course a part of our 1.7 feature set enabling PowerGUI use as locked-down customized consoles to use through-out your company – but this particular feature is in fact already available in 1.6.1 – so if there is a page that you like more than what we ship – read on.


The process of replacing the page is very straight-forward:

1. Create a new page in the editor of your choice. The page should be in MHT format. So either use Microsoft Word, or any html editor you like. If the editor does not support MHT format, simply save the page as MHT from Internet Explorer.

2. Put the page on the computer at which you use PowerGUI or a file share somewhere.

3. Run the script either from the command-line or PowerGUI Script Editor. The latter is probably easier – you just need to do File / Search Online and look for PowerGUI:


4. Download the script, type in the filepath in the parameter box and click Start Debugging.


5. Now you can start PowerGUI and enjoy your custom look and feel!


This is something you can start doing right away!

Other features (such as ability to lock down user ability to modify the console and central configuration distribution do require version 1.7 so either apply for the beta or wait just a little longer.

Tags: ,

10 Responses to “Rebranding PowerGUI console”

  1. 1 Andrew Tearle February 12, 2009 at 7:51 am

    Found that quotes around $mhtpath made the difference …

    # Set the new value and save the file
    $node.Value = “$mhtpath”

  2. 2 Dmitry Sotnikov February 12, 2009 at 12:05 pm

    Really? Very weird. So in your case this wouldn’t work without quotes but executes just fine with them?

    Which version of PowerShell is that?

    Does the $mhtpath have spaces?

  3. 3 Andrew Tearle February 12, 2009 at 10:52 pm

    Initially it would not proceed
    saying that the xmlnode needed a string ..
    so I tried quotes around it

    “Cannot set “value” because only strings can be used as values to set XmlNode properties.”

  4. 4 Andrew Tearle February 12, 2009 at 10:59 pm

    And Yes the path has spaces in !
    Something I should perhaps have realised,
    Thanx Dmitry.

  5. 5 piaqt February 14, 2009 at 2:37 am

    Um… Couldn’t you just edit the current welcome screen?

  6. 6 Dmitry Sotnikov February 15, 2009 at 1:18 pm


    1. Open the home.mht file from the PowerGUI profile folder (%appdata%\Quest Software\PowerGUI) in Word, notepad or another editor.

    2. Make your edits.

    3. Save under a different name.

    Then follow the steps from this blog post.

  1. 1 What’s new in PowerGUI 1.7 « Dmitry’s PowerBlog: PowerShell and beyond Trackback on February 26, 2009 at 12:00 pm
  2. 2 Release: PowerGUI 1.7 « Trackback on February 26, 2009 at 1:04 pm
  3. 3 PowerGUI 1.7 | Trackback on March 6, 2009 at 1:14 pm
  4. 4 Video: Rebranding PowerGUI « Dmitry’s PowerBlog: PowerShell and beyond Trackback on April 20, 2009 at 8:53 am

Leave a Reply

Fill in your details below or click an icon to log in: Logo

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

Google photo

You are commenting using your Google 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

February 2009

%d bloggers like this: