Windows Installer PowerShell Module

Edited Feature: Cmdlets for querying summary information stream [2756]

heaths — Mon, 20 May 2013 16:41:15 GMT

Create cmdlets to query the summary information stream for any storage passed to it, along with substorages (optionally?). For Windows Installer file types, create handlers to display proper property names (perhaps along with standard names) to give more meaning (since PROPIDs are overloaded like Revision Number, Template, etc.).

Edited Feature: Add cmdlet for validation [9423]

heaths — Mon, 20 May 2013 16:41:15 GMT

Add a cmdlet for validating MSIs - maybe even MSPs or MSTs applied to MSIs. The output is an object with properties for the ICE messages. But to easily select records based on messages consider how the table/column/primary keys would be output. Could be some sort of reference to a record that would work with the record selection / update cmdlets.
There should be a parameter to grab the default "darice.cub" from Orca by using a component search. With -Include and -Exclude, first generate inclusions (default is all) then remove exclusions (if any).
According to docs, "validate" is not valid but should actually be "test" as shown below.
Usage:
test-wipackage [-Path] <String[]> [[-CubPath] <String[]>] [-Default] [-Include <String[]>] [-Exclude <String[]>]

Edited Feature: Given a list of products and patches, return would-be sequence of patches [9121]

heaths — Mon, 20 May 2013 16:41:15 GMT

Create a cmdlet that would accept a list of patch packages and/or MSP XML file, and an optional list of product packages or ProductCodes. If no products were provided, then the union of the target ProductCodes should be used. Machine state can be optionally ignored.
Possible definitions:
get-wipatchsequence [-Path] <string[]> [[-ProductPath] <string[]>
get-wipatchsequence [-LiteralPath] <string[]> [[-ProductPath] <string[]>
get-wipatchsequence [-Path] <string[]> [[-ProductCode] <string[]> [-UserContext <UserContexts] [-UserSid <string>]
get-wipatchsequence [-LiteralPath] <string[]> [[-ProductCode] <string[]> [-UserContext <UserContexts] [-UserSid <string>]
The object returned has Sequence, Path (attach PSPath), and ProductCode or product package path (depending on parameterset). The default view would group by product and order by Sequence.

Commented Feature: Provider for mounting MSI files [5778]

heaths — Mon, 20 May 2013 16:39:44 GMT

Create a provider for mounting MSI files as PSDrives so that users can navigate and copy out of the media.
Comments: Given the new read-only stance I'm taking with the module (install package changes should be done in-source using your toolset - like WiX - to make sure everything is valid), this would be overkill. I will consider a cmdlet to extract files or even run an admin installation for a future release. Something like Export-MSIPackageFile.

Edited Feature: Provider for mounting MSI files [5778]

heaths — Mon, 20 May 2013 16:39:44 GMT

Create a provider for mounting MSI files as PSDrives so that users can navigate and copy out of the media.

Edited Feature: Given a list of products and patches, return would-be sequence of patches [9121]

heaths — Mon, 20 May 2013 16:37:20 GMT

Edited Issue: Files are not being signed [9173]

heaths — Mon, 20 May 2013 16:37:02 GMT

The *.ps1 and *.psm1 files are not being signed, even before the code was removed from the *.csproj files. The previous method of using PowerShell didn't always work, but the SignFile task only handles PE files, and XML-based Office files like .docx files. It does not sign all Authenticode-signable files.
The files could be signed prior to check-in after every edit, but this is not easily sustainable. A task could be created either to host PowerShell directly or to properly use the Crypto APIs to Authenticode sign the files.

Created Issue: Installer handles are not being closed [14454]

heaths — Mon, 20 May 2013 16:33:58 GMT

By using a PSPropertyAdapter, installer handles must be kept open so database, view, and record information can be retrieved when needed (which may not be right away). Will probably have to dump the PSPropertyAdapter and just do everything in the cmdlets. The problem is that, unless I use PSNoteProperty (which has no explicit type - just returns Value.GetType()), there's really no supported way to create a concrete-looking object since I can't supportedly extend PSProperty(Info) and no other PSPropertyInfo derivative supports the scenario.

Looking through Reflector - at least for PSv2 and PSv3 - extending PSPropertyInfo may work.

The question will be whether to keep the PSPropertyAdapter in addition to provide a near-consistent view of records no matter how retrieved.

(PS: Same goes for the SummaryInfo, since an open handle is required to get values.)

Closed Feature: Select records from an MSI or MSP database [5779]

heaths — Sun, 19 May 2013 19:29:28 GMT

Implement a cmdlet (select-record?) to select records - either by a SQL expression or for a whole table with a scriptblock for a filter - from either an MSI or MSP database. Another way might be to write a single cmdlet for performing queries and updates to a database.
Comments: Coming in the 2.2 release soon.

Created Issue: No PSPath for component key path starting with "20:\CLSID" [14453]

heaths — Sat, 18 May 2013 11:34:56 GMT

There another registry key root no currently handled by the module that uses "20:", like in "20:\CLSID". This is probably another root ID for HKCR but need to test this out.

Updated Wiki: Documentation

heaths — Tue, 07 May 2013 20:19:52 GMT

Help

The list of features and help resources can be found for each major release in the Help section. You may also view the discussion threads from the tabs above. If you have found a bug or want to see a new features, use the issue tracker from the tabs above. Please be sure to provide sufficient steps to reproduce the problem along with a detailed description of what happen and what you expect to happen.

You may also discuss new feature ideas in the discussion tab.

Current release: 2.1.5

Version 2 provides a snap-in registered to the machine and a module that can be installed by a user without administrative privileges. The module is installed to a user profile but can also be installed to a secure machine location for use by all users. The snap-in and the module provide the same set of cmdlets, but the module does provide additional functions and aliases for backward call-compatibility with version 1 cmdlets.

To use either the module or the snap-in from from this release, you must install PowerShell 2.0. PowerShell 2.0 is included in both Windows 7 by default, and Windows Server 2008 R2 as an optional feature.

Help (v2.1.4) (Applies to 2.1.5)
Formats

Examples

Types sent through the pipeline by these cmdlets are designed to work with standard cmdlets so you can string many cmdlets together. See Examples for a few ideas of what you can do with the Windows Installer PowerShell snap-in.

Updated Wiki: Formats

heaths — Tue, 07 May 2013 20:17:53 GMT

Formats

Several formats are provided for display. You can also view the formats for an output type using the following expression.

get-formatdata -typename (get-msiproductinfo)[0].pstypenames | select -expand format*

To view all predefined views for the psmsi snap-in, use the expressions below.

$formats = dir (get-pssnapin psmsi).ApplicationBase -filter *formats.ps1xml
$formats | %{ [xml]$xml = gc $_.FullName; $xml.Configuration.ViewDefinitions.View } `
| sort {$_.ViewSelectedBy.TypeName}, Name `
| ft @{l="Type"; e={$_.ViewSelectedBy.TypeName} }, Name, @{l="Control"; e={$_.psbase.ChildNodes.ItemOf(2)} } -auto

PackageSource

Displays source list information for patches and products.

Format-Table -View Indexed

PS> get-msiproductinfo | get-msisource | ft -view indexed

 Index Type     Path
 ----- ----     ----
     0 Network  C:\MSOCache\All Users\{90120000-0030-0000-0000-0000000FF1CE}-C\
     0 Network  C:\MSOCache\All Users\{90120000-0021-0000-0000-0000000FF1CE}-C\

Format-List -View Indexed

PS> get-msiproductinfo | get-msisource | fl -view indexed

Index : 0
Type  : Network
Path  : C:\MSOCache\All Users\{90120000-0030-0000-0000-0000000FF1CE}-C\

Index : 0
Type  : Network
Path  : C:\MSOCache\All Users\{90120000-0021-0000-0000-0000000FF1CE}-C\

Format-Table -View Package

PS> (get-msiproductinfo), (get-msipatchinfo) | get-msisource | ft -view package

    ProductCode: {90120000-0030-0000-0000-0000000FF1CE}

Index Type    Path
----- ----    ----
    0 Network C:\MSOCache\All Users\{90120000-0030-0000-0000-0000000FF1CE}-C\

    PatchCode: {7CA106D1-664C-40D4-BD94-5783ED9B7E3E}

Index Type    Path
----- ----    ----
    0 Network \\products\public\Products\Applications\User\Office_2007\Visio_Professional_2007\updates\

PatchInfo

Displays patch information.

Format-Table -View Package

PS> get-msipatchinfo | ft -view package

PatchCode                                   State LocalPackage                      DisplayName
---------                                   ----- ------------                      -----------
{BEE75E01-DD3F-4D5F-B96C-609E6538D419}    Applied C:\Windows\Installer\312e0a2d.msp 2007 Microsoft Office Suite Serv...
{02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}    Applied C:\Windows\Installer\1a9654c8.msp Security Update for Office 2007 ...

Format-List -View Patch

PS> get-msipatchinfo | fl -view patch

PatchCode     : {BEE75E01-DD3F-4D5F-B96C-609E6538D419}
ProductCode   : {90120000-0030-0000-0000-0000000FF1CE}
DisplayName   : 2007 Microsoft Office Suite Service Pack 1 (SP1)
State         : Applied
Uninstallable : False

PatchCode     : {02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}
ProductCode   : {90120000-0030-0000-0000-0000000FF1CE}
DisplayName   : Security Update for Office 2007 (KB947801)
State         : Applied
Uninstallable : True

Format-Table -View Patch

PS> get-msipatchinfo | ft -view patch

PatchCode                                    State  Uninstallable DisplayName
---------                                    -----  ------------- -----------
{BEE75E01-DD3F-4D5F-B96C-609E6538D419}     Applied          False 2007 Microsoft Office Suite Service Pack 1 (SP1)
{02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}     Applied           True Security Update for Office 2007 (KB947801)

Format-Table -View State

PS> get-msipatchinfo | ft -view state

   ProductCode: {90120000-0030-0000-0000-0000000FF1CE}

PatchCode                                   State  Uninstallable DisplayName
---------                                   -----  ------------- -----------
{BEE75E01-DD3F-4D5F-B96C-609E6538D419}    Applied          False 2007 Microsoft Office Suite Service Pack 1 (SP1)
{02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}    Applied           True Security Update for Office 2007 (KB947801)

ProductInfo

Displays product information.

Format-Table -View Package

PS> get-msiproductinfo | ft -view package

ProductCode                             LocalPackage                      ProductName
-----------                             ------------                      -----------
{90120000-0030-0000-0000-0000000FF1CE}  C:\Windows\Installer\a5824.msi    Microsoft Office Enterprise 2007
{90120000-0021-0000-0000-0000000FF1CE}  C:\Windows\Installer\33704f3.msi  Microsoft Office Visual Web Developer 2007

Format-Table -View Product

PS> get-msiproductinfo | ft -view product

ProductCode                             ProductVersion       ProductName
-----------                             --------------       -----------
{90120000-0030-0000-0000-0000000FF1CE}  12.0.6215.1000       Microsoft Office Enterprise 2007
{90120000-0021-0000-0000-0000000FF1CE}  12.0.4518.1066       Microsoft Office Visual Web Developer 2007

Format-List -View Product

PS> get-msiproductinfo | fl -view product

ProductCode    : {90120000-0030-0000-0000-0000000FF1CE}
Manufacturer   : Microsoft Corporation
ProductName    : Microsoft Office Enterprise 2007
ProductVersion : 12.0.6215.1000
InstallDate    : 3/12/2008 12:00:00 AM

ProductCode    : {90120000-0021-0000-0000-0000000FF1CE}
Manufacturer   : Microsoft Corporation
ProductName    : Microsoft Office Visual Web Developer 2007
ProductVersion : 12.0.4518.1066
InstallDate    : 2/14/2008 12:00:00 AM

Updated Wiki: Documentation

heaths — Tue, 30 Apr 2013 23:37:38 GMT

Help

Current release: 2.1.5

Help (v2.1.4) (Applies to 2.1.5)
Formats

Examples

Closed Issue: Cmdlets with PassThru parameters do not chain correctly [5554]

heaths — Tue, 30 Apr 2013 01:02:50 GMT

For those cmdlets that provide a -PassThru switch, they cannot be chained such that the NoteProperty objects they add are all visible.
Repro:
dir | get-msifilehash -passthru | get-msifiletype -passthru | ft name,msi*
Expected:
Name, MSIFileType, MSIHashPart1, MSIHashPart2, MSIHashPart3, and MSIHashPart4 are all displayed.
Result:
Name and MSIFileType are only displayed.

Closed Issue: Typo in Error_InvalidContext [14452]

heaths — Tue, 30 Apr 2013 01:02:31 GMT

The message for Error_InvalidContext reads, "The user context "None" is not validation for this operation." The word "validation" should be "valid".

Created Issue: Typo in Error_InvalidContext [14452]

heaths — Thu, 25 Apr 2013 21:34:07 GMT

The message for Error_InvalidContext reads, "The user context "None" is not validation for this operation." The word "validation" should be "valid".

New Comment on "Get-MSIProductInfo.v2.1.4"

heaths — Sun, 21 Apr 2013 02:28:20 GMT

The Windows Installer APIs do not work across machine boundaries. You can use WMI but won't have quite the same Experience: get-wmiobject Win32_Product -computer name

Commented Issue: Cmdlets with PassThru parameters do not chain correctly [5554]

heaths — Fri, 29 Mar 2013 18:25:54 GMT

Edited Issue: Cmdlets with PassThru parameters do not chain correctly [5554]

heaths — Fri, 29 Mar 2013 18:25:54 GMT

Source code checked in, #a91509e01aa4

Heath Stewart — Sat, 23 Mar 2013 01:24:44 GMT

Add default gitattributes