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.