restart options (if the machine will be restarted after the installation)

logging options

update options (apply or remove updates)

repair options (only for an installed package)

public properties which are used by the installation

The usual form of the msiexec command line is this:

msiexec.exe <install_option> <path_to_package> [package_parameters]

Install Options

When launching an installation package, you can set the install type through these options:

msiexec.exe [/i][/a][/j{u|m|/g|/t}][/x] <path_to_package>

/i - normal installation

/a - administrative install

/j - advertise the product

u - advertise to the current user

m - advertise to all users

/g - the language identifier used by the advertised package

/t - apply transform to advertise package

/x - uninstall the package

Sample command line:

msiexec.exe /i "C:\Example.msi"

Display Options

The user interface level of the installation can be configured according to the target environment. For example, a package distributed to clients should have a full UI, while a package deployed through Group Policy should have no user interface. Msiexec.exe sets the UI level of the installation through these options:

TipIn the above command line the first GUID is the Patch identifier GUID and the second one is the Product Code of the MSI for which the patch was applied.

Repair Options

If you have an installed package, you can use the Windows Installer command line for repairing it:

msiexec.exe [/f{p|o|e|d|c|a|u|m|s|v}] <product_code>

/f - repair a package

p - repair only if a file is missing

o - repair if a file is missing or an older version is installed

e - repair if file is missing or an equal or older version is installed

d - repair if a file is missing or a different version is installed

c - repair if a file is missing or the checksum does not match the calculated value

a - forces all files to be reinstalled

u - repair all the required user-specific registry entries

m - repair all the required computer-specific registry entries

s - repair all existing shortcuts

v - run from source and recache the local package

Sample command line:

msiexec.exe /fa {AAD3D77A-7476-469F-ADF4-04424124E91D}

In the above command line the GUID is the Product Code of the MSI which will be repaired.

Set public properties

The name of a public property contains only uppercase letters (for example PROPERTY). This type of properties can be set through the command line like this: PROPERTY="value".

Sample command line:

msiexec.exe /i "C:\Example.msi" MY_PROP="myValue"

MSIEXEC.EXE - the MSI executable, the program that performs the actual installation of the application.

/I - this switch informs the Windows Installer to install the specified application (as opposed to removing, reinstalling or repairing the application)

/QB- - this switch instructs the Windows Installer to perform the installation with a basic user interface requiring no dialog boxes to be displayed. You might also use /QN to perform the installation with no user interface at all.

Correct syntax:

msiexec /i A:\Example.msi PROPERTY=VALUE

Incorrect syntax:

msiexec /i PROPERTY=VALUE A:\Example.msi

Property values that are literal strings must be enclosed in quotation marks. Include any white spaces in the string between the marks.

msiexec /i A:\Example.msi PROPERTY="Embedded White Space"

To clear a public property by using the command line, set its value to an empty string.

msiexec /i A:\Example.msi PROPERTY=""

For sections of text set apart by literal quotation marks, enclose the section with a second pair of quotation marks.

Creating a Log FileIf you want to create a log file describing the installation/uninstallation, append /L C:\<path>setup.log to the install/uninstall command. The following is an example for installation: Installation Examplejre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s /L C:\<path>setup.logThe following is an example for uninstalling:

Note:- Adobe Customization Wizard 9 will help you to create MST file for silent installation

WINZIP:-

Team Viewer :--

The /S switch for silent install of TEAMVIEWER WORKS!but you must do the following :download the program (preferably the latest version) ..or ..if you have it on your hard drive , open it... (AND LET IT OPEN! DO NOT CLOSE OR INSTALL THE APLICATION. JUST DUBLE-CLICK IT!!)Then , go to C:\Documents and Settings\Administrator\Local Settings\Temp. There you'll see a folder called TeamViewer. Open that folder. Inside you'll have 2 files. Teamviewer.exe and tvinfo.iniCopy the Teamviewer from that folder and paste wherever you want. After this you can close the other application. With the new teamviewer.exew which you copyed from the temp folder , u can run it sillently. Use the /S Switch. Works with WPI also.

If you find MSiexec has problem then you can run below two commands

msiexec /unregister ---> for unregistering the windows installer

msiexec /regserver---> for registering the windows installer

Released Versions of Windows Installer

The table in this topic identifies the released versions of the Windows Installer.

Windows Installer 3.03.0.3790.2180Released with Windows XP with Service Pack 2 (SP2). Released as a redistributable.

Windows Installer 3.13.1.4000.1823Released as a redistributable. This version is has the same functionality as version 3.1.4000.2435.

Windows Installer 3.13.1.4000.1830Released with Windows Server 2003 with Service Pack 1 (SP1) and Windows XP Professional x64 Edition. Update this version to version 3.1.4000.2435 to address the issue discussed in KB898628.

Windows Installer 4.54.5.6002.18005Released with Windows Vista with Service Pack 2 (SP2) and Windows Server 2008 with Service Pack (SP2.)

Windows Installer 4.54.5.6000.20817Released as a redistributable for Windows Vista.

Windows Installer 4.54.5.6001.22162Released as a redistributable for Windows Server 2008 and Windows Vista with SP1.

Windows Installer 4.54.5.6001.22159Released as a redistributable for Windows XP with Service Pack 2 (SP2) and later, and Windows Server 2003 with SP1 and later.

Windows Installer 5.0 is released with Windows Server 2008 R2 and Windows 7.

To create exe file by using winrar for silent installation / Self Extractor

create SFX archive”. Change the archive name if you like but it must have the .exe extension. Switch to the Advanced tab and select “SFX options” to open Advanced SFX options window.On the General tab in the “Path to extract” box type the path you want to extract the installer to. Make sure it is the same path you have in the antivir.cmd file. Then in the “Run after extraction” box type in the path to the antivir.cmd file.Change to the Modes tab and select the “hide all” and “overwrite existing files” radio buttons.Close the “Advanced SFX Options” window by clicking OK, then click OK on the “Archive name and parameters” window to start creating the installer. The finished installer is created in the antivirpec folder.

Also you can do with 7zip where you will have more options compare to winrar or winzipself extractor.

Office 2007 silent install with SCCM 2007

So here is his tip on how to create a customized MSP file with OCT:

Go to the original package source that contains the Office 2007 setup files

From the directory that contains the Office 2007 setup files, run setup.exe /admin. This should open the Office Customization Toolkit (OCT)

Select to Create a new Setup customization file

In the “Install location and organization name”, set the default installation location and organization name.

Click on Licensing and user interface. Make sure you enter a valid product key, check the EULA checkbox and set Display level to None. Completion notice checkbox should not be checked and Suppress modal should be checked.

Save the MSP file by going to File --> Save. Give the file a name and save it to the Updates folder located in the Office 2007 installation source folder. By saving it to the Updates folder, the /adminfile switch will not need to be used as part of setup.exe. If the file is not saved to the Updates folder, make sure that the /adminfile switch is used as part of setup.exe and that it points to the MSP file just created.

Further more, with OCT you can customize almost everything regarding how your Word/Excel etc. applications will run. What I liked most is the possibility to create the default profile in Outlook if you are using an Exchange server in your organization.

Don’t forget to save the MSP file and to put the file in Updates folder or to use /adminfile <path to MST file> switch .

Hope I will try to post when i get some time

0
comments:

Post a Comment

Attribution

By accessing this Website, you indicate your acknowledgement acceptance of the following terms and conditions. These terms and conditions may change from time to time, and you agree to be bound by any such changes when posted on this Website, including its affiliates, as applicable reserves all of its rights at law and equity, The information and content displayed on this Website, including but not limited to text, graphics, logos, images, audio clips and software, is the property of Public or its licensors, as the case may be, and is protected by copyright laws. While I invite you to browse, no content or information on this Website may be downloaded, reproduced or modified in any manner without the prior written consent of me (PaddyMaddy) or as otherwise expressly provided herein.