The Yellow Highlighter – MooreMN

20091107

Adobe Reader 9.2 – Customizing the MSI

Filed under: Adobe, Software, Software Deployment — mooremn @ 10:27 AM

Adobe Reader  allows for the viewing and printing of PDF files.  Available as a free download from Adobe, the full version of Adobe Reader 9.2x is available as both a Windows installer file (.msi) or an executable (.exe) at:
ftp://ftp.adobe.com/pub/adobe/reader/win/9.x/9.2/enu/

See MooreMN Downloads for links to more Adobe download resources.

You can use the Adobe Customization Wizard 9 to customize the Adobe Reader MSI file and specify the default application behavior of Adobe Reader 9 prior to deployment. This is particularly useful if you will be deploying Adobe Reader to multiple systems and desire a standardized installation.  The Adobe Customization Wizard can directly edit the MSI file or create a transform file (.mst), which can be used to pass customizations to the Adobe Reader MSI file during installation.

The example will focus on a basic customization of the Adobe Reader 9.2 MSI and the generation of a transform file.
This brief walk thru will illustrate making the following customizations to the transform file:
  -  Remove the Adobe Reader desktop shortcut
  -  Suppress the End User License Agreement (EULA) for the user
  -  Disable Auto Updates
  -  Disable ad prompts
  -  Enable Reader Auto-Complete

You will first need to install the Adobe Customization Wizard 9.  To download the Customization Wizard see the link ‘Adobe Customization Wizard 9′ below.

Opening the Adobe Reader 9.2 MSI file within the Adobe Customization Wizard
Download the Adobe Reader 9.2 installer file (AdbeRdr920_en_US.msi)
Open the Adobe Customization Wizard 9
From the topline menu, select File/Open Package
Browse to and open the installer file AdbeRdr920_en_US.msi
The installer can now be customized

Customizing Adobe Reader 9.2 Options

  • Remove the Adobe Reader desktop shortcut
    From the menu options on the left, select ‘Shortcuts’
    On the right hand side, under ‘Desktop’ right click on ’Adobe Reader 9′ , and select ‘Remove’
  • Suppress the End User License Agreement (EULA) for the user
    From the menu options on the left, select ‘EULA and Document Status’
    On the right hand side, check ‘Suppress display of End User License Agreement’
  • Disable Auto Updates
  • Disable ad prompts
    From the menu options on the left, select ‘Online and Acrobat.com Features’
    On the right hand side, check the following options:
    Disable all udates
    In Adobe Reader, disable Help > Disable Purchase Adobe Acrobat
    Disable Viewing of PDF with Ads for Adobe PDF
  • Enable Reader Auto-Complete
    From the menu options on the left, select ‘Comments and Forms’
    On the right hand side, under the Auto-Complete option, select ’Basic’
    Check, ‘Remember numerical Data’

Generating the Adobe Reader 9.2 Transform
Note:  If you prefer to save the changes directly to the MSI, creating the Transform file is not neccesary.

After completing the neccesary customizations, from the topline menu, select Transform / Generate Transform
A ‘Save As’ window opens with the ‘Save as type’ *.mst default displayed.
Name the transform file AdbeRdr920_en_US.mst
By default the transform file is saved in the same folder as the base .msi file.
Close the Adobe Customization Wizard. You will have the option to save the  changes directly to the MSI file; having created the MST, this is redundant and not neccesary.

Installing Adobe Reader 9.2 Using the Transform File
Once a transform file has been created, you can use basic Windows Installer command-line syntax to include the transform in the execution of an installation.
For example, to perform a silent installation that incorporates the custom options of the created transform use the following command-line:
msiexec.exe /i “AdbeRdr920_en_US.msi” TRANSFORMS=”AdbeRdr920_en_US.mst” /qb-!

Notes:
For more information regarding usage of the Adobe Customization Wizard see the link ‘Adobe Customization Wizard 9′.
Other options are available thru the Windows Installer command-line.  See the link ‘Basic Windows Installer  Command-Line – V3 thru V4.5′ for additional options.

Links:
Adobe Customization Wizard 9
http://mooremn.wordpress.com/2009/09/01/adobe-customization-wizard-9

Customizing Adobe Application Through Adobe Customization Wizard 9
http://www.symantec.com/connect/articles/customizing-adobe-application-through-adobe-customization-wizard-9

Deploying Adobe Reader 9
http://www.adobe.com/devnet/acrobat/pdfs/deploying_reader9.pdf

Basic Windows Installer  Command-Line – V3 thru V4.5
http://mooremn.wordpress.com/2009/08/30/windows-installer-v3-thru-v4-5-microsoft-basic-use/

AppDeploy:
http://www.appdeploy.com/packages/detail.asp?id=1328
http://www.appdeploy.com/packages/detail_pf.asp?id=1328

20091001

Group Policy – Installing the Group Policy Management Console SP1

Filed under: Downloads, Microsoft, Software — mooremn @ 12:00 PM

Microsoft’s Group Policy Management Console with SP1 (GPMC) improves upon the native method of editing Group Policy  by providing a more developed console that brings together management of Group Policy across a domain or enterprise. The GPMC snap-in provides easier access to Group Policy settings for the purpose of editing, managing and implementing Group Policy changes.  It is a tool to more easily understand, deploy, manage, and troubleshoot Group Policy and can be used to manage Windows Server 2000 and 2003 based Group Policy implementations.

The GPMC runs on Windows XP Professional SP1 and Windows Server 2003 computers and can manage Group Policy in either Windows 2000 or Windows Server 2003 domains.

The GPMC is available as a free download from Microsoft.  See MooreMN Downloads for a link to the Group Policy Management Console download page.

Make sure you check system requirements before installing, .Net Framework v1.1 is required for the GPMC to run.

After downloading, to install the GPMC, simply run the gpmc.msi package and follow the prompts, it’s a quick and painless install.

After installation of the GPMC, you can open the snap-in using any of the following methods:

  • You can open a stand alone GPMC. From the Start button, select Run, type GPMC.msc, and click OK.
  • A Group Policy Management shortcut is added to your Administrative Tools folder.
  • To add the GPMC snap-in to an existing custom Microsoft Management Console (MMC):
    - Open your existing custom MMC.
    - From the File menu, choose Add/Remove Snap-in…, and then select Add.
    - In the Add Standalone Snap-in dialog box, find and select Group Policy Management and click Add.
    - Select Close, then select OK.

Notes:
Much of this articles information is excerpted from Microsofts Group Policy Management Console with Service Pack 1 download page. For more information including detailed system and domain/enterprise requirements and limitations, check the download page, it’s a pretty quick read.

Links:
Enterprise Management with the Group Policy Management Console
http://www.microsoft.com/windowsserver2003/gpmc/default.mspx

Windows Server Group Policy Home – TechNet
http://technet.microsoft.com/en-us/windowsserver/grouppolicy/default.aspx

Group Policy – Wikipedia
http://en.wikipedia.org/wiki/Group_Policy

20090905

Java SE Runtime Environment 6 (Java 6) – Silent Uninstall (.msi)

Filed under: Software, Software Deployment, Sun — mooremn @ 10:07 PM

The default behavior of Java SE 6 now upgrades (uninstalls previous versions of Java SE 6).  This change in the default behavior appears as of Java SE 6u11.  However, versions of Java SE 6 older than update 10 are not uninstalled (they remain listed as seperate full installations of Java under ‘Add/Remove Programs’).  The old default behavior would install version after version until systems might have a half dozen or more Java installs on them. Versions of Java 6 update 1 thru Java update 7 can be uninstalled using the appropriate msiexec command line syntax as shown below.

When uninstalling Java, web browsers need to be closed.

:Uninstall Java SE RunTime Ver 1.6.0_07
msiexec /x {3248F0A8-6813-11D6-A77B-00B0D0160070} /norestart /qb-!

:Uninstall Java SE Run-Time Ver 1.6.0_06
msiexec /x {3248F0A8-6813-11D6-A77B-00B0D0160060} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_05
msiexec /x {3248F0A8-6813-11D6-A77B-00B0D0160050} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_04
msiexec /x {3248F0A8-6813-11D6-A77B-00B0D0160040} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_03
msiexec /x {3248F0A8-6813-11D6-A77B-00B0D0160030} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_02
msiexec /x {3248F0A8-6813-11D6-A77B-00B0D0160020} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_01
msiexec /x {3248F0A8-6813-11D6-A77B-00B0D0160010} /norestart /qb-!


With the default behavior of JavaSE Runtime 6 now performing an upgrade, you likely won’t ever need to run these commands, but the newer versions are listed here with their product IDs.

:Uninstall Java SE RunTime Ver 1.6.0_16
msiexec /x  {26A24AE4-039D-4CA4-87B4-2F83216016FF} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_15
 msiexec /x {26A24AE4-039D-4CA4-87B4-2F83216015F0}/norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_14
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83216014F0}/norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_13
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83216013F0}/norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_12
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83216012F0} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_11
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83216011F0} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_10
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83216010F0} /norestart /qb-!

Links:
Java Silent Install / Silent Uninstall (exe):
http://java.sun.com/javase/6/docs/technotes/guides/deployment/deployment-guide/silent.html

Java SE Runtime Environment 6 (Java 6 Update 16) – Silent Install (.exe)

Filed under: Software, Software Deployment, Sun — mooremn @ 8:44 PM

Sun’s Java Standard Edition (Java SE) Runtime Environment is used to deploy portable applications or applets for general use on workstations. Due to its wide user base, it is seen by hackers as a potential point of attack when looking to affect a large number of computer systems.

Sun regularly provides updates to patch security vulnerabilities to the Java Runtime Environment.  This series of articles provides basic guidance and additional references in automating the deployment process of Java.

The Java SE Runtime Environment is available as a free download from Sun.  See MooreMN Downloads for links to Java download resources.

Common Command-line Options:
/s  –  silent installation, there is no progress indicator. If incorrect syntax is used, the Windows Installer options window will be displayed.
/v  –  pass command-line arguments to Msiexec
IEXPLORER=1  –  indicates that the Java Plug-in should be registered with the Internet Explorer browser
MOZILLA=1  –  indicates that the Java Plug-in should be registered with Mozilla 1.1 and later and Netscape browsers
REBOOT=Suppress  –  if used, indicates that if locked files are encountered the computer should not be rebooted
INSTALLDIR=<Path>  –  if used, specifies the explicit drive and path of the installation.

Examples:
Silent install, Java IE Plug-in registered, do not reboot:
jre-6u16-windows-i586-p.exe /s IEXPLORER=1 REBOOT-Suppress

Silent install, Java installed to an alternate directory.  In these two examples either INSTALLDIR statement is valid:
jre-6u16-windows-i586.exe /s INSTALLDIR=C:\AltJavaFolder
jre-6u16-windows-i586.exe /s /v”INSTALLDIR=C:\AltJavaFolder”

Notes:
When installing, browsers need to be closed.

The default behavior of JavaSE 6 now upgrades (uninstalls previous versions of JavaSE 6).  This change in the default seems to have appeared as of JavaSE 6u11.  However, versions of JavaSE 6 older than 10 are not uninstalled (they remain as a seperate full installation of Java under ‘Add/Remove Programs’).  The old default behavior would install version after version until systems might have a half dozen or more Java installs on them.

This feature release (update 16) does not contain any new fixes for security vulnerabilities to Java SE 6 Update 15.  Users who have Java SE 6 Update 15 have the latest security fixes and do not need to upgrade to this release to be current on security fixes.

Links
Java Silent Install / Silent Uninstall (exe)
http://java.sun.com/javase/6/docs/technotes/guides/deployment/deployment-guide/silent.html

AppDeploy
http://www.appdeploy.com/packages/detail.asp?id=38
While I use AppDeploy often when needing advice on how to tackle  a software push, the Java thread has grown into a bit of a chaotic mess.  However, some useful info does exist within the thread.

Java SE Runtime Environment 6 (AKA Java 6 Update 16) – Extracting the MSI

Filed under: Software, Software Deployment, Sun — mooremn @ 12:13 AM

Sun’s Java Standard Edition (Java SE) Runtime Environment is used to deploy portable applications or applets for general use on workstations. Due to its wide user base, it is seen by hackers as a potential point of attack when looking to affect a large number of computer systems.

Sun regularly provides updates to patch security vulnerabilities to the Java Runtime Environment.  This series of articles provides basic guidance and additional references in automating the deployment process of Java.

The Java SE Runtime Environment is available as a free download from Sun.  See MooreMN Downloads for links to Sun Java download resources.

————————————————–
To Extract the MSI within the Java 6 Update

Download the Java 6 Update 16

Execute jre-6u16-windows-i586.exe
When the Java setup ‘Welcome Folder’ screen appears, you will find the folder that contains the files needed for installation in the default extraction location based on OS.  After locating the files, copy them to a working folder for later work with the MSI installer. Cancel the JavaSE 6 setup.
The installer files are extracted to the default ‘Setup Files’ folder as shown below.

Default ‘Setup Files’ folder
XP – %UserProfile%\Local Settings\Application Data\Sun\Java\jre1.6.0_16
W7 – \Users\%username%\AppData\LocalLow\Sun\Java\jre1.6.0_16

Notes:
When installing, browsers need to be closed.

It seems the Default behavior of JavaSE 6 now upgrades (removes previous versions of JavaSE 6).  This change in the default seems to have appeared with JavaSE 6u11.  However, versions JavaSE 6u9 and older are not upgraded (they remain as a seperate full installation of Java under ‘Add/Remove Programs’).
The old default behavior would install version after version until systems might have a half dozen or more Java installs on them.

This feature release (update 16) does not contain any new fixes for security vulnerabilities to Java SE 6 Update 15.  Users who have Java SE 6 Update 15 have the latest security fixes and do not need to upgrade to this release to be current on security fixes.

Links
Extracting the Java MSI installer for deployment
http://www.java.com/en/download/help/6000070500.xml

Java Runtime Environment – Windows Installation for JavaSE 6u10
http://java.sun.com/javase/6/docs/technotes/guides/jweb/otherFeatures/jre_install.html

Java Runtime Environment – Update Scenarios for JavaSE 6u10
http://java.sun.com/javase/6/docs/technotes/guides/jweb/otherFeatures/jre_update_scenarios.html

AppDeploy
http://www.appdeploy.com/packages/detail.asp?id=38
While I use AppDeploy often when needing advice on how to tackle  a software push, the Java thread has grown into a bit of a chaotic mess.  However, some useful info does exist within the thread.

20090901

Adobe Customization Wizard 9

Filed under: Adobe, Software, Software Deployment — mooremn @ 12:15 AM

Adobe Customization Wizard 9 is a utility designed to customize the installer and application features of Adobe Acrobat 9 and Adobe Reader 9 prior to deployment.  It provides a graphical interface to access the Windows Installer options for Acrobat and Adobe Reader.

The Adobe Customization Wizard 9 is available as a free download from Adobe.  See MooreMN Downloads for links to Adobe download resources.

When installing or deploying Adobe Acrobat or Adobe Reader, the Adobe Customization Wizard simplifies the generation of a transform file (.mst), allowing for a standardized custom installation.  The Adobe Customization Wizard allows you to enter serial numbers, suppress the End User License Agreement (EULA), and control most customization options that may be desired for a specific installation or  deployment.

The Adobe Reader can be downloaded as either a single Windows Installer file (.msi) or as an executable (.exe).  If you have downloaded the executable you’ll first need to extract the packaged files, which includes the AcroRead.msi file, and then use the Adobe Customization Wizard 9 to modify its default options.  More information on extracting the MSI file are available below under Links:

Once the files are extracted, you can open the AcroRead.msi file using the Customization Wizard and begin selecting desired modifications to the default installation options, then save your choices by selecting ’Save Package’, which will by default generate a transform file named AcroRead.mst in the same folder as the AcroRead.msi. 

Using Adobe Customization Wizard 9 is fairly intuitive.  As such, there is really no need to go into much detail.  Symantec of all sites, has a nice article that breaks down the various options available with screenshots, and should provide enough detail for anyone wanting a little insight into its operation.  See the link below ‘Customizing Adobe Applications Through Adobe Customization Wizard 9′ for an introduction to the Customization Wizards interface.

Notes:
When deploying software via Group Policy, you can specify a transform file when setting up a new Software Package for deployment by selecting ‘Advanced’ instead of the default ‘Assigned’  for your deployment method. Transforms can be added under the ‘Modifications’ tab only if ‘Advanced’ is selected and only during the initial creation of a software package.

Links:
Adobe Customization Wizard 9 Features and Benefits
http://www.adobe.com/support/downloads/detail.jsp?ftpID=3993

Adobe Reader 9.1x – Extracting the MSI
http://mooremn.wordpress.com/2009/09/01/adobe-reader-9-1x/

Customizing Adobe Applications Through Adobe Customization Wizard 9
http://www.symantec.com/connect/articles/customizing-adobe-application-through-adobe-customization-wizard-9

Deploying Adobe Reader 9
http://www.adobe.com/devnet/acrobat/pdfs/deploying_reader9.pdf

Adobe Reader 9.1x – Patching the Base MSI File

Filed under: Adobe, Installers, Software, Software Deployment — mooremn @ 12:10 AM

Adobe Reader  allows for the viewing and printing of PDF files. 

Adobe Reader is available as a free download from Adobe.  See MooreMN Downloads for links to Adobe download resources.

Adobe Reader 9.1x – Extracting the MSI:
http://mooremn.wordpress.com/2009/09/01/adobe-reader-9-1x/

Integrating Upgrade Patches into the Base Adobe Reader MSI File:
After downloading and extracting the base Adobe Reader 9.10 installation files into a working folder, also download and copy the the following Adobe Reader Update patches into the working folder.
AdbeRdrUpd912_all_incr.msp
AdbeRdrUpd913_all_incr.msp
->AdbeRdrUpd911_all_incr.msp is not needed.  AdbeRdrUpd912_all_incr.msp includes the 9.11 fixes.

Integrate the Adobe Reader 9.12 patch
Execute the command:
     msiexec.exe /a “AcroRead.msi” /p AdbeRdrUpd912_all_incr.msp

The Adobe Reader 9.1.2 Welcome screen will appear, select next.
The Adobe Reader 9.1.2 Network Location screen will appear, with the location of the current working folder filled in.  Add a subfolder to hold the extracted files such as C:\WorkingFolder\912.
Select Install, when the extraction is complete, select Finish.
The AcroRead.msi file should now have a current date/time stamp. It should also be about 30kb smaller
The 912 folder and its contents can be deleted.
Test the now updated AcroRead.msi to confirm it has been patched to 9.1.2.
AdobeReader912

Integrate the Adobe Reader 9.13 patch
Execute the command:
     msiexec.exe /a “AcroRead.msi” /p AdbeRdrUpd913_all_incr.msp

The Adobe Reader 9.1.3 Welcome screen will appear, select next.
The Adobe Reader 9.1.3 Network Location screen will appear, with the location of the current working folder filled in.  Add a subfolder to hold the extracted files such as C:\WorkingFolder\913.
Select Install, when the extraction is complete, select Finish.
The AcroRead.msi file should now have a current date/time stamp.
The 913 folder and its contents can be deleted.
Test the now updated AcroRead.msi to confirm it has been patched to 9.1.3.
AdobeReader913

->The Adobe Reader 9.13 patch will not patch the Adobe Reader 9.10 msi. If you run this command against the base Adobe Reader 9.10 msi, you will receive a Windows Installer error:  “The upgrade patch cannot be installed by the Windows Installer Service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program”.

Patch During Initial Installation (Installing Adobe Reader 9.10 Base install with patches)
In this example, the Acroread.msi file is at version 9.1.0. 
To apply a patch the first time the application is installed, the PATCH property must be set on the command line.
Using command-line, this will install Adobe Reader 9.10, and patch Adobe Reader to version 9.1.3.
Specify the full path to the patch(es) on the command line as “PATCH=path\patch.msp”.

Execute the command 
     msiexec.exe /i AcroRead.msi TRANSFORMS=AcroRead.mst PATCH=”C:\WorkingFolder\AdbeRdrUpd912_all_incr.msp;C:\WorkingFolder\AdbeRdrUpd913_all_incr.msp” /norestart /qb-!
Note:  Due to word wrap make sure to capture the entire command

Install the patch only on a system that has Adobe Reader 9.1.0 (not tested)
If a system already has Adobe Reader 9.1.0 it can be patched as shown.
msiexec /p AdbeRdrUpd912_all_incr.msp REINSTALL=ALL REINSTALLMODE=omus /qb-!
msiexec /p AdbeRdrUpd913_all_incr.msp REINSTALL=ALL REINSTALLMODE=omus /qb-!

Links:
Windows Installer V3 thru V4.5 – Microsoft – Full Command Line Options
http://mooremn.wordpress.com/2009/08/30/windowsinstallerv45-mscommand-line

Patching Initial Installations
http://msdn.microsoft.com/en-us/library/aa370581(VS.85).aspx

AppDeploy:
http://www.appdeploy.com/packages/detail.asp?id=1328

How to Apply Patches (.msp) to Group Policy Deployed Software (.msi)
http://www.404techsupport.com/2009/06/26/how-to-apply-patches-msp-to-group-policy-deployed-software-msi/

Adobe Reader 9.1x – Extracting the MSI

Filed under: Adobe, Software, Software Deployment — mooremn @ 12:00 AM

Adobe Reader  allows for the viewing and printing of PDF files.

Adobe Reader is available as a free download from Adobe.  See MooreMN Downloads for links to Adobe download resources.

AdbeRdr910_en_US.exe -nos_o”./WorkingFolder” -nos_ne
In this example the installer files are extracted to a sub folder of the current directory named  ‘WorkingFolder’

AdbeRdr910_en_US.exe -nos_ne
In this example the installer files are extracted to the default ‘Setup Files’ folder as shown below.

AdbeRdr910_en_US.exe
In this ‘old school’ method, when the Adobe Reader 9.1 setup ‘Destination Folder’ screen appears, you will find the folder that contains the files needed for installation in the default extraction location based on OS.  After locating the files, copy them to a working folder for later work with the MSI installer. Cancel the Adobe Reader 9.1 setup, the default folder will be removed.
In this example the installer files are extracted to the default ‘Setup Files’ folder as shown below.

Default ‘Setup Files’ folder
XP – %UserProfile%\Local Settings\Application Data\Adobe\Reader 9.x\Setup Files
Vista – \Users\%username%\AppData\Local\Adobe\Reader 9.1\Setup Files

Notes:
AdbeRdr910_en_US.exe
Without acrobat.com and Adobe Air. 26MB

AdbeRdr910_en_US_Std.exe
With acrobat.com and Adobe Air. 42MB

Links:
Extracting the Adobe Reader 9.1x MSI installer for deployment
http://kb2.adobe.com/cps/404/kb404146.html
http://mooremn.wordpress.com/2009/08/25/fead-optimizer-netopsystems-command-line/

Adobe Reader 9.1x – Patching the Base MSI File
http://mooremn.wordpress.com/2009/09/01/adobereader91x-patchingthebasemsi/

Deploying Adobe Reader 9
http://www.adobe.com/devnet/acrobat/pdfs/deploying_reader9.pdf

AppDeploy:
http://www.appdeploy.com/packages/detail.asp?id=1328
http://www.appdeploy.com/packages/detail_pf.asp?id=1328

20090830

Windows Installer V3 thru V4.5 – Microsoft – Basic Use

Filed under: Installers, Microsoft, Software, Software Deployment — mooremn @ 7:15 AM

The Microsoft Windows Installer (MSI) is the application installation and configuration service for Windows.

Common Options:

Install Options:
Install a product
/i {Product.msi}

Administrative install – Installs or extracts a product to a drive or network point
/a {Product.msi}

Uninstall the product
/x {Product.msi or ProductCode}

Display Options
Quiet mode, no user interaction
/quiet

Unattended mode – progress bar only
/passive

Set user interface level to No UI
/qn

Set user interface level to Basic UI
/qb

Restart Options
Do not restart after the installation is complete
/norestart

Always restart the computer after installation
/forcerestart

Setting Public Properties
[PROPERTY=PropertyValue]

Examples:
To start an install of Adobe Reader:
msiexec.exe /i “AcroRead.msi”

To start an uninstall of Adobe Reader:
msiexec.exe /x “AcroRead.msi”

To perform a silent install of Adobe Reader:
msiexec.exe /i “AcroRead.msi” /q

To perform a silent uninstall of Adobe Reader:
msiexec.exe /x “AcroRead.msi” /q

To perform a silent uninstall of Java SE Run-Time Ver 6 update 7 using the product code:
msiexec /x {3248F0A8-6813-11D6-A77B-00B0D0160070} /qb-!

To perform a silent install of Adobe Reader and force a restart after completion:
msiexec.exe /i “AcroRead.msi” /q /forcerestart

Links:
Windows Installer V3 thru V4.5 – Microsoft – Full Command Line Options
http://mooremn.wordpress.com/2009/08/30/windowsinstallerv45-mscommand-line/ 

Overview of the Windows Installer Technology
http://support.microsoft.com/kb/310598

Windows Installer
http://en.wikipedia.org/wiki/Windows_Installer

Windows Installer V3 thru V4.5 – Microsoft – Full Command Line Options

Filed under: Installers, Microsoft, Software Deployment — mooremn @ 7:04 AM

Windows ® Installer. V 3.01.4001.5512
Windows ® Installer. V 4.5.6001.22159

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
     Installs or configures a product
/a <Product.msi>
     Administrative install – Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
     Advertises a product – m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
     Uninstalls the product

Display Options
/quiet
     Quiet mode, no user interaction
/passive
     Unattended mode – progress bar only
/q[n|b|r|f]
     Sets user interface level
     n – No UI
     b – Basic UI
     r – Reduced UI
     f – Full UI (default)
/help
     Help information

Restart Options
/norestart
     Do not restart after the installation is complete
/promptrestart
     Prompts the user for restart if necessary
/forcerestart
     Always restart the computer after installation

Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
     i – Status messages
     w – Nonfatal warnings
     e – All error messages
     a – Start up of actions
     r – Action-specific records
     u – User requests
     c – Initial UI parameters
     m – Out-of-memory or fatal exit information
     o – Out-of-disk-space messages
     p – Terminal properties
     v – Verbose output
     x – Extra debugging information
     + – Append to existing log file
     ! – Flush each line to the log
     * – Log all information, except for v and x options
/log <LogFile>
     Equivalent of /l* <LogFile>

Update Options
/update <Update1.msp>[;Update2.msp]
     Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
     Remove update(s) for a product

Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
     Repairs a product
     p – only if file is missing
     o – if file is missing or an older version is installed (default)
     e – if file is missing or an equal or older version is installed
     d – if file is missing or a different version is installed
     c – if file is missing or checksum does not match the calculated value
     a – forces all files to be reinstalled
     u – all required user-specific registry entries (default)
     m – all required computer-specific registry entries (default)
     s – all existing shortcuts (default)
     v – runs from source and recaches local package

Setting Public Properties
     [PROPERTY=PropertyValue]

Consult the Windows Installer SDK for additional documentation on the command line syntax.

Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.

Notes:
To display these MSI options, type msiexec from Run.. or a command prompt.

Older Posts »

Blog at WordPress.com.