Archive

Archive for May, 2017

Applying Small Updates by Reinstalling the Product

May 1, 2017 No comments

Aa367575.wedge(en-us,VS.85).gifTo propagate the small update to current users (this is a complete reinstall) from the command line

  1. From the command line use either: msiexec /fvomus [path to updated .msi file] or msiexec /I [path to updated .msi file] REINSTALL=ALL REINSTALLMODE=vomus.
  2. The updated .msi file is cached on the user’s computer. Note that it is not possible for the user to reinstall the product using Add/Remove Programs because the updated .msi file is not yet on the user’s computer.

Aa367575.wedge(en-us,VS.85).gifTo propagate a small update to current users (this is a complete reinstall) from a program

  1. From a program, call MsiReinstallProduct and specify REINSTALLMODE_PACKAGE, REINSTALLMODE_FILEOLDERVERSION, REINSTALLMODE_MACHINEDATA, REINSTALLMODE_USERDATA, and REINSTALLMODE_SHORTCUT
  2. The updated .msi file is cached on the user’s computer.

The following method launches a reinstallation of only those features or components that are affected by the small update.

Aa367575.wedge(en-us,VS.85).gifTo propagate a small update to current users (this is a partial reinstall)

  1. Obtain a list of the names of features and components that are affected by the small update.
  2. From the command prompt use: msiexec /I [path to updated .msi file] REINSTALL=[Feature list] REINSTALLMODE=vomus.
  3. The updated .msi file is cached on the user’s computer.

Source: https://msdn.microsoft.com/en-us/library/aa367575(v=vs.85).aspx

Categories: Uncategorized Tags:

Error code 2771, 1635 , 1603 installing Exchange 2010 Rollup