Silent Installation
From PowerGUI Wiki
The following settings can be made for PowerGUI in silent installs:
Setting PowerGUI installation folder
You can specify an installation folder in msiexec command line this way:
msiexec /quiet /i C:\PowerGUI.1.6.1.639.msi PF_POWERGUI=c:\PowerGUIInstallFolder
Selecting the features to install
You can also specify the list of features to be installed using standard Windows Installer properties like ADDLOCAL, REMOVE, etc. (see http://msdn.microsoft.com/en-us/library/aa367536(VS.85).aspx).
msiexec /quiet /i C:\PowerGUI.x.x.x.xxx.msi ADDLOCAL=PowerGUI,ScriptEditor,PowerPack_LocalSystem PF_POWERGUI=c:\PowerGUIInstallFolder
The features include the components themselves as well as default PowerPacks.
Here is the list of existing PowerGUI features:
PowerGUI - The root feature
UILocalization - GUI localizations
ScriptEditor - PowerGUI Script Editor and Debugger
PSFilesAssociation - Associate PowerShell scripts with PowerGUI Script Editor
PowerPacks - Add-ons for PowerGUI Admin Console (PowerPacks)
PowerPack_ActiveDirectory - Active Directory PowerPack
PowerPack_Network - Network PowerPack
PowerPack_Exchange - Exchange 2007 PowerPack
PowerPack_LocalSystem - Local System PowerPack
PowerPack_ExportActions - Common reporting and export actions
Integration_vSphere - VMWare vSphere Client integration
The default loading behavior is to detect any snapins (i.e. Active Directory) and if found, install the PowerPack for that snapin. If no snapins are detected - Local System and Network PowerPacks are installed. This default behavior can be changed with the ADDLOCAL and REMOVE parameters.
Adding non-default PowerPacks
You can also make PowerGUI automatically install PowerPacks which are not included in the setup. For example any of the packs from PowerGUI Library or custom packs created by you.
For this you need to:
1. Create 'Additional PowerPacks' subfolder in the folder containing the PowerGUI msi file.
2. Put the PowerPack files you want to be installed in that new folder.
