Install-MSIPatch

Synopsis

Installs a patch package or packages for all or only specified products.

Syntax

Install-MSIPatch [-Path] <string[]> [-PassThru] [-ProductCode <string[]>] [-UserContext <UserContexts>] [-UserSid <string>] [-Log <string>] [-Properties <string[]>] [-Chain] [-Force] [<CommonParameters>]

Install-MSIPatch -Patch <PatchInstallation[]> [-PassThru] [-ProductCode <string[]>] [-UserContext <UserContexts>] [-UserSid <string>] [-Log <string>] [-Properties <string[]>] [-Chain] [-Force] [<CommonParameters>]

Install-MSIPatch -LiteralPath <string[]> [-PassThru] [-ProductCode <string[]>] [-UserContext <UserContexts>] [-UserSid <string>] [-Log <string>] [-Properties <string[]>] [-Chain] [-Force] [<CommonParameters>]

Description

You can install one or more patch packages to all installed targets products or to just a subset of products.

Progress, warnings, and errors during the install are sent through the pipeline making this command fully integrated.

Parameters

-Chain <SwitchParameter>

Whether to install all packages together.

Required? false
Position named
Default value|
Accepts pipeline input? false
Accept wildcard charactrs? false

-Force <SwitchParameter>

Whether to suppress all prompts.

Required? false
Position named
Default value|
Accepts pipeline input? false
Accept wildcard charactrs? false

-LiteralPath <string[]>

The path to a patch package to install. The value of -LiteralPath is used exactly as typed. No characters are interpreted as wildcards.

Required? true
Position named
Default value|
Accepts pipeline input? true (ByPropertyName)
Accept wildcard charactrs? false

-Log <String>

The path to the log file. This use the file name as the base name and will append timestamp and product-specific information.

Required? false
Position named
Default value|
Accepts pipeline input? false
Accept wildcard charactrs? false

-PassThru <SwitchParameter>

Whether to pass the newly installed patch information after installation to the pipeline.

Required? false
Position named
Default value|
Accepts pipeline input? false
Accept wildcard charactrs? false

-Patch <Microsoft.Deployment.WindowsInstaller.PatchInstallation[]>

Information about a patch or patches to install to other products.

Required? true
Position named
Default value|
Accepts pipeline input? true (ByValue)
Accept wildcard charactrs? false

-Path <string[]>

The path to a patch package to install. Wildcards are permitted. You can specify * in any part of the path to select all matching files.

Required? true
Position 0
Default value|
Accepts pipeline input? true (ByValue, ByPropertyName)
Accept wildcard charactrs? true

-ProductCode <string[]>

The ProductCode or ProductCodes to which the patch or patches should be applied.

Required? false
Position named
Default value|
Accepts pipeline input? true (ByPropertyName)
Accept wildcard charactrs? false

-Properties <string[]>

Additional property=value pairs to pass during install.

Required? false
Position named
Default value|
Accepts pipeline input? true (FromRemainingArguments)
Accept wildcard charactrs? false

-UserContext <Microsoft.Deployment.WindowsInstaller.UserContexts>

The user context for the product listed in the ProductCode parameter.

Required? false
Position named
Default value Machine
Accepts pipeline input? true (ByPropertyName)
Accept wildcard charactrs? false

-UserSid <String>

The user security identifier for product listed in the ProductCode parameter.

Required? false
Position named
Default value|
Accepts pipeline input? true (ByPropertyName)
Accept wildcard charactrs? false

Outputs

  • Microsoft.Deployment.WindowsInstaller.PatchInstallation: Information for the newly installed patch or patches.

Examples

Example 1

install-msipatch .\example.msp MSIFASTINSTALL=2
Install the example.msp patch package for all installed target products with MSIFASTINSTALL set to only do file costing before installation.

Example 2

get-msiproductinfo -name TEST | install-msipatch .\example.msp -log $env:TEMP\patch.log -passthru
Install the example.msp patch package only for the product with ProductName "TEST" and log to the TEMP directory.

Return information about the patch after logging.

Related Links


Last edited Jul 2, 2013 at 7:56 AM by heaths, version 1

Comments

No comments yet.