MSP Center Plus supports installing and uninstalling software applications in MSI and EXE
formats. Any software that supports silent mode of installation (without user intervention) can be
deployed using MSP Center Plus. Deploying software using MSP Center Plus is a simple two-step
process:

Add the software package to the Software Repository maintained by MSP Center Plus. The package once created can be used to install / uninstall the software from the client computers any number of times by defining the configuration (step 2).
Define an Install Software configuration and deploy. Separate configurations have to be defined for deploying software to users and computers.

1.1 Pre-requisites

Software Installation using MSP Center Plus requires the following pre-requisites to be met:

Need to create a network share for saving the software executables.
The network share should have sufficient access privileges for authenticated users and everyone.
The network share should be reachable from all the computers to which the software is being installed.

2 Supported Applications Format

MSP Center Plus supports installing both MSI and EXE based software applications. One of the
requirements is that the software has to support silent installation, meaning it should not wait for
any inputs from the user during installation. Inputs, if any, should be accepted as command line
arguments.

MSI – MSI refers to Microsoft installer programs. Most popular applications, like MSOffice, Skype, etc., provide an MSI option to install in Windows operating systems.
MSIEXEC/EXE /ISS/ Command – Refers to a standalone executable to install any legacy application that can be installed silently. For example, installing applications like AdobeReader.exe, Skype.exe or registering a DLL using regsvr32.exe <dll-name>, etc., can be done using this option.

3 Adding a Package

The first step in installing the software applications is to add them into the package repository. Once the packages are added, it can then be used to deploy them on to the client computers. To add a package in MSP Center Plus, go to Desktop Management--> Admin --> Software Repository --> Add Package.

3.1 Adding a Package for MSI Based Applications

To add a package for installing an MSI based application, select the Package type as MSI

3.1.1 Specifying the Package Details

This step is mandatory for all the packages that are added in MSP Center Plus.

Package Name	Name of the Software Package
Select the path type	The path to the MSI can be either a network path or HTTP path: Network Path: If the software has to be installed in computers in the same LAN, select this option. The network path specified here should be a shared folder with read access to “Everyone” group. HTTP Path: If the software has to be installed in computers in branch offices over the VPN tunnel or internet, select this option
Add Files to Upload	When the HTTP path is selected, browse and select the installables, which will be uploaded to the MSP Center Plus Server
MSI File Name with network path	When the Network Path option is selected, specify the name of the MSI file with its complete network path. This path should have all the related files and should have necessary read & execute permissions. Example: \\MyServer\MSIApps\Skype\skype.msi. When the HTTP Path option is selected, just specify the name of the MSI file here.

3.1.2 Specifying Installer/Uninstaller Settings

This step is required only if the application being installed supports customization prior to installation or if it requires any specific arguments for installation/uninstallation.

MSI Root Path	If the installables have to be copied to individual computers before installation, the directory that has to be copied should be specified here.
MST file name with Network path	For applications that support customizations prior to installation, the customization file should be specified here.
path	For example, MS Office 2003 installation can be customized by specifying the license keys, choosing the components to install, etc., using the Microsoft Office Resource Kit Tools. After customization an .MST file gets created. The MST file should also be placed in the network share where all the other installation files are present. Specify the location of the MST file with the network path here. If the copy option is selected while deploying the application, the location of the MST file specified here should be relative to the MSI Root Path. If the MSI Root Path is displayed as \\MyServer\Shares\MSIApps and if the MST File is in \\MyServer\Shares\MSIApps\Office2003\Custom.mst, specify the location as Office2003\Custom.mst. Multiple mst files can be specified as semi-colon separated. If the HTTP option is selected as the path, just specify the name of the MST File here.
Install Arguments to MSI	Application specific installation parameters can be specified here. For example, for skype, specify parameters like installlevel=10. This field can be left blank, if the application does not have any specific arguments.
Uninstall Arguments to MSI	Application specific uninstallation parameters can be specified here. For example, REBOOT=ReallySuppress

3.1.3 Specifying Package Properties

This step is optional and can be skipped, if not required.

Manufacturer	Name of the software vendor
Version	The software version
Language	The software language version
Package Description	Description of the software package

3.1.4 Specifying Pre-Installation Commands

This step is optional and can be skipped, if not required.

MSP Center Plus supports executing pre-installation commands or scripts that have to be executed prior to installing the software application. For example, you may wish to clean up the temp directory or make some directory changes prior to installation. The software installation can also be aborted if the pre-installation is not successful.

The scripts or the commands specified here will be executed in all the client computers. Make sure that a valid command that will execute in all the client computers is specified here.
Examples:

wscript.exe \\MyServer\Scripts\pre-install.vbs
\\MyServer\Scripts\pre-install.bat
rmdir /s /q temp

Script / Software Name	Specify the commands or script that has to be executed before installing the software.
Arguments	Specify the arguments for the pre-installation script, if any
Continue installation if the exit code is	Select this option and specify the exit code to check for successful preinstallation process before proceeding with the software installation. If the pre-installation fails, the installation will abort.

3.1.5 Specifying Post-Installation Commands

This step is optional and can be skipped, if not required.

After successful installation of the software, the administrator may wish to customize the installed application by changing the registry value or the configuration files, or to clean up the temp directory, etc. In such cases, executing post installation will be very handy. The scripts or the commands specified here will be executed in all the client computers. Make sure that a valid command that will execute in all the client computers is specified here.

Examples:

wscript.exe \\MyServer\Scripts\post-install.vbs
\\MyServer\Scripts\post-install.bat
rmdir /s /q Temp

Script/Software name	Specify the commands or script that has to be executed after installing the software.
Arguments	Specify the arguments for the post-installation script, if any.
Successful if the Exit Code is	Select this option and specify the exit code to verify whether post installation has been successful. If post-installation is not successful, the software will not be uninstalled.

3.1.6 Specifying Pre-Uninstallation Commands

This step is optional and can be skipped, if not required.

MSP Center Plus supports executing pre-uninstallation commands or scripts that have to be executed prior to uninstalling the software application. The software uninstallation can also be aborted if the pre-uninstallation is not successful.

The scripts or the commands specified here will be executed in all the client computers. Make sure that a valid command that will execute in all the client computers is specified here.

Examples:

wscript.exe \\MyServer\Scripts\pre-uninstall.vbs
\\MyServer\Scripts\pre-uninstall.bat
mkdir MyDirectory

Script/Software name	Specify the commands or script that has to be executed before uninstalling the software.
Arguments	Specify the arguments for the pre-uninstallation script, if any.
Continue uninstallation if the exit code is	Select this option and specify the exit code to check for successful preuninstallation process before uninstalling of the software. If the preinstallation fails, the uninstallation will abort.

3.1.7 Specifying Post-Uninstallation Commands

This step is optional and can be skipped, if not required.

After successful uninstallation of the software, the administrator can configure to run a command or script in all the client computers. This is optional and can be specified based on the requirement. While MSP Center Plus displays the execution status of the post-uninstallation command, it does not re-install the software if it is unsuccessful.

The scripts or the commands specified here will be executed in all the client computers. Make sure that a valid command that will execute in all the client computers is specified here.

Examples:

wscript.exe \\MyServer\Scripts\post-uninstall.vbs
\\MyServer\Scripts\post-uninstall.bat
rmdir /s /q MyDirectory

Script/Software name	Specify the commands or script that has to be executed after uninstalling the software.
Arguments	Specify the arguments for the post-uninstallation script, if any.
Successful if the Exit Code is	Select this option and specify the exit code to verify whether post uninstallation has been successful. If post-installation is not successful, the software will not be re-installed.

3.2 Adding a Package for EXE Based Applications

To add a package for installing an EXE based application, select the Package type as
MSIEXEC/EXE /ISS/ Command

3.2.1 Specifying the Package Details

This step is mandatory for all the packages that are added in MSP Center Plus.

Package Name	Name of the Software Package
Select the path type	The path to the EXE/Command can be either a network path or HTTP path: Network Path: If the software has to be installed in computers in the same LAN, select this option. The network path specified here should be a shared folder with read access to “Everyone” group. HTTP Path: If the software has to be installed in computers in branch offices over the VPN tunnel or internet, select this option
Add Files to Upload	When the HTTP path is selected, browse and select the installables, which will be uploaded to the MSP Center Plus Server
Installation Command with Switches/Arguments	The command to be executed in the client computers for installing the application must be specified here. The command specified here will be "as such" executed in all the client computers. If the application will be installed directly from the network share, the absolute path can be specified (\\MyServer\Shares\MyApplicaton\Setup.exe). If you use the copy option in the Software Installation configuration before installing the software, specify the relative path from the EXE Root Directory.
Uninstallation Command with Switches/Arguments	The command to be executed in the client computers for uninstalling the application must be specified here. The command specified here will be "as such" executed in all the client computers.

3.2.2 Specifying Installer/Uninstaller Settings

This step is required only if the software has to be installed from the network share. The EXE Root Directory must be a directory in the network share from where all the commands will be executed. This directory should have access to all the executables that are required to install the application.

3.2.3 Specifying Package Properties

This step is optional and can be skipped, if not required.

Manufacturer	Name of the software vendor
Version	The software version
Language	The software language version
Package Description	Description of the software package

3.2.4 Specifying Pre-Installation Commands

wscript.exe \\MyServer\Scripts\pre-install.vbs
\\MyServer\Scripts\pre-install.bat
rmdir /s /q temp

Script/Software name	Specify the commands or script that has to be executed before installing the software.
Arguments	Specify the arguments for the pre-installation script, if any.
Continue installation if the exit code is	Select this option and specify the exit code to check for successful preinstallation process before proceeding with the software installation. If the pre-installation fails, the installation will abort.

3.2.5 Specifying Post-Installation Commands

This step is optional and can be skipped, if not required.

After successful installation of the software, the administrator may wish to customize the installed application by changing the registry value or the configuration files, or to clean up the temp directory, etc. In such cases, executing post installation will be very handy.

The scripts or the commands specified here will be executed in all the client computers. Make sure that a valid command that will execute in all the client computers is specified here.

Examples:

wscript.exe \\MyServer\Scripts\post-install.vbs
\\MyServer\Scripts\post-install.bat
rmdir /s /q Temp

Script/Software name	Specify the commands or script that has to be executed after installing the software.
Arguments	Specify the arguments for the post-installation script, if any.
Successful if the Exit Code is	Select this option and specify the exit code to verify whether post installation has been successful. If post-installation is not successful, the software will not be uninstalled.

3.2.6 Specifying Pre-Uninstallation Commands

wscript.exe \\MyServer\Scripts\pre-uninstall.vbs
\\MyServer\Scripts\pre-uninstall.bat
mkdir MyDirectory

Script/Software name	Specify the commands or script that has to be executed before uninstalling the software.
Arguments	Specify the arguments for the pre-uninstallation script, if any.
Continue installation if the exit code is	Select this option and specify the exit code to heck for successful preuninstallation process before uninstalling of the software. If the preinstallation fails, the uninstallation will abort.

3.2.7 Specifying Post-Uninstallation Commands

wscript.exe \\MyServer\Scripts\post-uninstall.vbs
\\MyServer\Scripts\post-uninstall.bat
rmdir /s /q MyDirectory

Script/Software name	Specify the commands or script that has to be executed after uninstalling the software.
Arguments	Specify the arguments for the post-uninstallation script, if any.
Successful if the Exit Code is	Select this option and specify the exit code to verify whether post uninstallation has been successful. If post-uninstallation is not successful, the software will not be re-installed.

3.2.8 Using ISS Files in Software Deployment

EXE files created using InstallShield can be installed silently by creating ISS files (answer files). Deploying InstallShield EXE files silently has two parts:

Recording the inputs in n file (ISS) using a single computer
Using the ISS file created in step 1 to install the software using MSP Center Plus on multiple computers

Note: The example shown in the steps is for installing VNC. The same method can be followed for any InstallShield Setup.exe files.

Step I - Recording the inputs in a file (ISS) using a single computer

Goto Command (Start -> Run -> cmd) prompt
Navigate to the folder (ex.C:\software\Winvnc)
Type in C:\software\Winvnc\Setup.exe /r /f1”c:\software\Winvnc\silentinstall.iss”
You'll be asked for inputs on confirmation , installation directory. etc., (make sure you provide details which can be commonly used on other computers also)
Once the installation is over, check the c:\software\Winvnc\ folder for silentinstall.iss

Step II - Using the ISS file to install the software in multiple computers

From the Software Deployment page, goto EXE
Configure the 'Installation Command with Switches/Arguments' \\shareserver\Software\winvnc\Setup.exe /s /f1"\\shareserver\software\Winvnc\silentinstall.iss"
Specify the root directory as \\share-server\Software\winvnc
Now create configuration and install the software

4 Creating Software Deployment with various Options

Once the packages are added to the software repository, the administrator can then define a configuration using MSP Center Plus to install the software applications to the client computers. To define a configuration, select Desktop Management--> Software Repository--> Install Software (of Users or Computers).

4.1 Selecting the Package

While defining the configuration, the first step is to select the application type as MSI or EXE. Then, the appropriate package has to be selected from the dropdown list. For installing the application, the Operation type has to be Install and Remove for uninstalling the application.

4.2 Run As

MSP Center Plus supports installing or uninstalling the application as a specific user. For example, if the application has to be installed with administrator privileges, the Run As field should have the username who has administrative privileges in all the client computers. The password of this user has to be specified in the Password fields.

4.3 Copy File / Folder

MSP Center Plus supports copying the necessary installable to the client computers before installing or uninstalling the applications. This is optional and when selected will speedup the unstallation/uninstallation process.

4.4 Scheduled Deployment

The administrator has an option to deploy the software after a specific date/time. To schedule a software deployment, he/she can select the “Schedule time to perform the operation” and specify the date and time after which the software has to be installed/uninstalled.

It may be noted that, when a configuration is deployed to the client computers for installing the software the actual deployment happens as below:

For Computer Configurations:

Installation / Uninstallation Option	Actual Deployment Schedule
During or After Startup	Within 90 minutes if the computer is up 0r during the next startup.
During Startup	During the next computer startup after the scheduled time.
After Startup	Within 90 minutes if the computer is up or 90 minutes after the next startup

For User Configurations:

User has logged on to the domain	Within 90 minutes
User has not logged on to the domain	When the user logs in to the domain

4.5 Selecting the Target Computers/Users for Deployment

The next step is to select the target computers or users for deploying the software. MSP Center Plus provides an option to select all the users/computers of a site, domain, OU etc. Also, it provides options to exclude specific computers based on the Target Type, OS Type or the Machine Type.

4.6 Deploying the Software

After specifying all the required inputs for the configuration, the administrator has to deploy the software in all the specified target computers/users. To deploy the configuration, click the Deploy button. The configuration can also be saved as a draft to be deployed at a later stage.

5 Popular Applications with their Deployment Options

This section will provide the details on installing various applications using MSP Center Plus along with the options that have to be provided in the installation and uninstallation options while creating a package.

For application that requires some additional steps prior to creating a package, like MS Office 2003, MS Office 2007, QuickTime Player etc., the complete steps are provided in the sections below.

Requirements:

The application installable (MSI or the EXE File) should be located in a network share.
The network share should have read permission to the “Everyone” group.
The location of the executable should be specified while adding the package in MSP Center Plus

The table below lists the Installation and uninstallation options for various applications:

5.1 EXE Based Applications

Application Name	Installation Command with Switches/Arguments	Uninstallation command with Switches/Arguments	Notes
MS Office 2003 Service Packs	<filename> /Q	NA	Service Packs cannot be uninstalled
MS Office 2007 Service Packs	<filename> /Q	NA	Service Packs cannot be uninstalled
Compatibility Pack for MS Office XP/2003 to view /edit Office 2007 formats	<filename> /q /passive	Not Known
Internet Explorer 7	Not Known	<filename> %SystemRoot%\ie7\spunin st\spuninst.exe /q
Internet Explorer 8	<filename> /quiet /passive /update-no /norestart	Not Known
VNC 4.1.1	To install Server Alone: <filename> /VERYSILENT /COMPONENTS="!vncviewer, winvnc" /TASKS="installservice, launchservice"	%programfiles%\RealVNC\V NC4\unins000.exe /VERYSILENT	The ‘!’ symbol can be used to choose the components that should not be installed
	To install Server & Viewer: /VERYSILENT /COMPONENTS="vncviewer, winvnc" /TASKS="!quicklaunchicon, desktopicon, installservice, launchservice"
Macromedia Flash	<filename> /s	Not Known
Macromedia Shockwave Flash	<filename> /S	Not Known
Adobe Acrobat Reader 8.0	<filename>/sALL /rs /l /msi"/qb‐! /norestart ALLUSERS=2 EULA_ACCEPT=YES SUPPRESS_APP_LAUNCH=YES"	msiexec /x %programfiles%\Adobe\Read er 8.0\Setup Files\{AC76BA86‐7AD7‐1033‐ 7B44‐ A80000000002}\AcroRead.m si /qn
Adobe Acrobat Reader 9.0	<filename>/sAll /rs /l /msi"/qb‐ ! /norestart ALLUSERS=1 EULA_ACCEPT=YES SUPPRESS_APP_LAUNCH=YES"	msiexec /x %programfiles%\Adobe\Read er 9.0\Setup Files\{AC76BA86‐7AD7‐1033‐ 7B44‐ A90000000001}\AcroRead.m si /qn
Adobe Acrobat Reader 9.1	<filename> /sAll /rs /l /msi"/qn /norestart ALLUSERS=1 EULA_ACCEPT=YES AgreeToLicense=Yes SUPPRESS_APP_LAUNCH=YES"	Not Known
Adobe Acrobat Reader versions below 8	<filename> /s	Not Known
WinRAR3.7.1	<filename> /S	%programfiles%\winrar\uni nstall.exe /s
CCleaner2.0.3	<filename> /S	%programfiles%\CCleaner\ uninst.exe /S
Google Toolbar for IE Version: 5.0.1112.3348- big/en (GGLL) Notifier Version: 3.0.914.9778	<filename> /q /d	Not Known
Google Talk	<filename> /S	%programfiles%\Google\G oogle Talk\uninstall.exe /S
.NET Framework 2.0	<filename> ::/q:a /c:"install /q"	%systemroot%\Microsoft.N ET\ Framework\v2.050727\Micr osoft .NET Framework 2.0\install.exe /qu
.NET Framework 3.0	Dotnet3setup.exe /q /norestart	Not Known
.NET Framework 3.5	dotnetfx35.exe /PASSIVE /NORESTART	Not Known
VLC Media Player	<filename> /S	%programfiles%\VideoLAN \VLC\uninstall.exe /S
Winamp	<filename> /S	%programfiles%\Winamp\ UninstWA.exe /S
Real Player	<filename> /S	Not Known	Make sure the Internet Browsers are closed, when installing the RealPlayer. This requirement is not part of Desktop Central, closing the browser is advised by RealNetworks.
Mozilla ThunderBird	"Thunderbird Setup 2.0.0.9.exe" -ms	%programfiles%\Mozilla Thunderbird\uninstall\helpe r.exe /s
Mozilla Firefox	"Firefox Setup 2.0.0.12.exe" – ms	%programfiles%\Mozilla Firefox\uninstall\helper.exe /s
Jre 1.6.6	jre-6u6-windows-i586-p.exe /s /v "/qn ADDLOCAL=ALL IEXPLORER=1 NETSCAPE=1 MOZILLA=1"
Tugzip 3.5	tugzip35.exe /VERYSILENT	%programfiles%\TUGZip\un ins000.exe /VERYSILENT
Limewire	-	%programfiles%\LimeWire\ uninstall.exe /S
BitlordV2.0	-	%programfiles%\BitLord2\u nins000.exe" /SILENT	Versions below 2.0 do not have an silent option for uninstallation.
Morpeuz	-	%ProgramFiles%\Morpheu s Download Booster\unins000.exe /SILENT

5.2 MSI Based Applications

Application Name	Installer/Uninstaller Settings – Install Arguments to MSI	Notes
Adobe Flash Player Plugin 9.0	Not required	The MSI file should be in the network share.
Adobe Acrobat Reader 8.0	Not required
Skype 3.6		The value for the INSTALLLEVEL can vary depending on the options chosen to install. For example, for installing just phone it should be 1.

5.3 Installing MSP Based Applications

While the major versions of the applications are either available in the EXE or the MSI format, minor updates to some software applications (ex. Updates to Adobe software) are distributed in MSP format. MSP Center Plus also provides an option to install these updates using the Software Deployment module.

These updates have to added as EXE packages as explained in section 3.2

The Installation Command with Switches and Arguments should be:
msiexec /update <the msp file name> /qn

The EXE Root directory should be the network share that contains the MSP files

5.4 Installing MS Office 2003

Steps involved in deploying MS Office 2003 using MSP Center Plus

Creating an Administrative Installation Point
Customizing Installation
Adding the Software Package in MSP Center Plus
Creating and Deploying the Configuration

5.4.1 Creating an Administrative Installation Point

Before deploying MS Office 2003 application to large number of users, it is required to create an administrative installation point on a network server from where the setup can be run. Given below are the steps to create an administrative installation point:

Create a share on a network server for the administrative installation point. The network share should have read permission to the “Everyone” group. The network share must have at least 550 megabytes (MB) of available hard disk space.
Insert the Office 2003 CD and type setup.exe /a on the command line. If you are using the Office 2003 Select CD, type the name of the Setup program for the package you are installing. For example, if you are installing Office 2003 Professional from the Select CD, type SetupPro.exe /a on the command line.
Specify the organization name that has to be defined for all users who install Office from this administrative installation point.
Specify the network server and share that is created in step 1 as the installation location
Enter the 25-character Volume License Key and click Next. The Volume license key specified here should be a valid one. Users who install Office 2003 from this administrative image do not need to enter the product key when they install Office 2003 or start an Office 2003 application for the first time.
Accept the end-user license agreement and click Install. Accepting the agreement here, means accepting on behalf of all users who install Office from this administrative installation point.

Setup copies the files from the Office 2003 CD to the administrative installation point, extracts the compressed cabinet (CAB) files, and creates a hierarchy of folders in the root folder of the share.

5.4.2 Customizing Installation

The next step is to customize the installation as required. For example, it can be customized to install only outlook in all the computers or to remove the previous installation before installing the latest, etc.

1. Download and install the Microsoft Office Resource Kit Tools (ork.exe). It can be downloaded from:
http://www.microsoft.com/downloads/details.aspx?FamilyID=4bb7cb10-a6e5-4334-8925-3bcf308cfbaf&displaylang=en
From the Microsoft Office 2003 Resource Kit Tools and select Custom Installation Wizard.
The first screen of the 22 screen wizard will be shown.
Choose the MSI file from the Office2003 folder that is in the network share. That would be PRO.msi for Office2003 Professional
Follow the wizard to specify all the other options as required.
Create a new MST file
Name it .MST, say custom.MST, in the network shared folder where the Office 2003 administrative install is located.
Now the office customization is ready.

5.4.3 Adding the Software Package in MSP Center Plus

Now that the Administrative installation and customization is completed, the next step is to add the package in MSP Center Plus as explained in section 3.0. Given below are the options specific to Office 2003:

The application type is MSI
The MSI File name should be the selected from the network share where the administrative installation point has been created. For example, the file name should be PRO.msi for Office2003 Professional.
Installer/Uninstaller Settings – MST file name with Network path: custom.MST

5.4.4 Creating and Deploying the Configuration

The final step is to create a configuration for deploying Office 2003 to users/computers as discussed in section 4.0

5.5 Installing / Uninstalling Office 2007

Steps involved in deploying Office 2007:

Customizing Installation
Adding the Software Package in MSP Center Plus
Creating and Deploying the Configuration

5.5.1 Customizing Installation

MS Office 2007 installation can be customized in two ways:

By creating an MSP File containing the customizations
By Using config.xml File

5.5.1.1 By creating an MSP File

The first step to deploy Office 2007 is to customize the installation and copy the necessary files
to a network share

Create a share on a network server. The network share should have read access to “Everyone” group.
Insert the Office 2007 CD and copy the contents of the CD to the share created in step 1.
Open a command prompt and change directory to the network share and type setup.exe /admin. This will open the customization UI.
Select the Licensing and User Interface option and specify the license key. Select the Display Level as None and select the Suppress Modal check box.
Similarly, select all the other options as required.
After customizing all the required options, select File--> Save As option to save the customization. The file will be in .MSP format and should be saved in the root directory of the network share (same as where the setup.exe is located).

5.5.1.2 By Using Config.xml File

The first step to deploy Office 2007 is to customize the installation and copy the necessary files
to a network share

Create a share on a network server. The network share should have read access to “Everyone” and “Authenticated Users”.
Insert the Office 2007 CD and copy the contents of the CD to the share created in step 1.
Depending on the MS Office version, the location of the config.xml varies. For example, for Standard version, the file to be edited will be under Standard.WW. Similarly, for Professional and Enterprise versions, the file will be under Professional.WW and Enterprise.WW respectively.
Edit the config.xml file based on the version and make the changes as shown below and save. The changes shown in bold are mandatory. The PIDKEY, USERNAME, COMPANTNAME, INSTALLLOCATION shown below are indicative; you need to specify as required:

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />

<Logging Type="standard" Path="%temp%" Template="Microsoft Office Standard Setup(*).txt" />

<PIDKEY Value="bdq32qvxbmrfgfdgvyxdxdrmj" />

<USERNAME Value="DesktopCentral" />

<COMPANYNAME Value="AdventNet" />

<INSTALLLOCATION Value="%programfiles%\Microsoft Office" />

Additional Reference : http://technet.microsoft.com/enus/library/cc179195.aspx#ConfigxmlElementQuickReference

5.5.2 Adding the Software Package in MSP Center Plus

The next step is to add the package in MSP Center Plus as explained in section 4.0. Given below are the options specific to Office 2007:

The application type is EXE
The EXE File name should be the selected from the network share where the MSP file is located.
Installation Command with Switches/Arguments:

If you are using MSP File
\\serverName\<ShareName>\setup.exe /adminfile
\\serverName\<ShareName>\<MSP File name>
If you are using config.xml
\\serverName\<ShareName>\setup.exe /config
\\serverName\<ShareName>\Standard.WW\config.xml

EXE Root Path: \\serverName\<ShareName>\

5.5.3 Creating and Deploying the Configuration

The final step is to create a configuration for deploying Office 2007 to users/computers as discussed in section 4.0.

5.6 Installing QuickTime Player

Steps involved in deploying QuickTime Player:

Extracting the MSI from the EXE
Adding the Software Package in MSP Center Plus
Creating and Deploying the Configuration

5.6.1 Extracting the MSI from EXE

Download the QuickTime Player.
Clear the contents of %TEMP% directory.
Run the setup file up to the “Welcome to QuickTime” screen and cancel the installation.
Copy the quicktime.msi available in the %TEMP% directory and put it in a network share.

5.6.2 Adding the Software Package in MSP Center Plus

First add the package in MSP Center Plus as explained in section 3.0. Given below are the options specific to QuickTime Player:

The application type is MSI.
The MSI File name should point to the quicktime.msi file that is located in a network share.
Installer/Uninstaller Settings – Arguments to MSI: issetupdriven=1 /q

5.6.3 Creating and Deploying the Configuration

The final step is to create a configuration for deploying QuickTime player to users/computers as discussed in section 5.0

5.7 Installing Winzip 11.1

Steps involved in installing Winzip:

Installing Winzip Manually to get the required files
Adding the Software Package in MSP Center Plus
Creating and Deploying the Configuration

5.7.1 Installing Winzip manually to get the required files

Run winzip111.exe in a machine and install manually
Copy the installation folder (c:\Program Files\WinZip) to a network share

5.7.2 Adding the Software Package in MSP Center Plus

Add the package in MSP Center Plus as explained in section 4.0. Given below are the options specific to WinZip 11.1:

The application type is EXE.
The EXE Root directory should be the directory that contains WINZIP32.EXE and should be in the network share.
Installation Command with Switches/Arguments: WINZIP32.EXE /noqp /autoinstall
Uninstallation Command with Switches/Arguments:

“%programfiles%\Winzip\WINZIP32.EXE” /uninstallx

5.7.3 Creating and Deploying the Configuration

The final step is to create a configuration for installing WinZip to users/computers as discussed in section 4.0

5.8 Installing Adobe Acrobat Reader with Customization

Steps involved in installing customized Acrobat Reader:

Extracting the MSI from the EXE
Customizing the Installation
Adding the Software Package in MSP Center Plus
Creating and Deploying the Configuration

6.8.1 Extracting the MSI from the EXE

Execute the "AdbeRdr80_en_US.exe". Wait till the installation wizard initiates.
Type %temp% from Start--> Run
You will find Adobe Reader 8 folder created in the temp directory. Copy the AcroRead.msi, Setup.ini, and data1.cab files from there to a separate folder.
Exit the installation wizard.

5.8.2 Customizing the Installation

Open the AcroRead.msi from Adobe Customization Wizard.
For installation options, select “Silently(No Interface)” and “Suppress Reboot” options available under Run Installation.
Make the necessary customizations and select Transform--> Generate Transform from the top quick links.
Specify a name for the Transform file and save.

5.8.3 Adding the Software Package in MSP Center Plus

Create a network share and copy the AcroRead.msi, Setup.ini, data1.cab, and the Transform
file to that share.

Add the package in MSP Center Plus as explained in section 3.0. Given below are the options
specific to Adobe Acrobat Reader 8.0:

The application type is MSI
The MSI File name should be the selected from the network
Installer/Uninstaller Settings – MST file name with Network path: custom.MST

5.8.4 Creating and Deploying the Configuration

The final step is to create a configuration for installing Acrobat Reader 8 to users/computers as discussed in section 4.0

RSS of this page