How to Automate the Installation of Office 2010 with only Application you want via MDT 2010 Update 1

In MDT 2010 Update 1 you can continue to install / deploy Office applications as defined in the Deployment Share.

Now when you are running the wizard in MDT one of the questions request the command line installation instructions. This time we want to install some of Office 2010 applications:

1. You need to use the setup.exe /admin command via command prompt to access Office 2010 Customization Tool and as result create an .msp file.

2. This .msp file will then need to be set as the installation option during automated installations. Define the optons as you need yet keep in mind to select the Accept the End User Agreement and the Do Not Cancel option as well. The Suppress Mode can be left on Basic.

3. Once created the file can be copied to \admin\en-us\ inside the Office 2010 as in the example below:

setup.exe /adminfile .\admin\en-us\config.msp:

To work…

Isvet MVP

How to Automate the Installation of .msi you want via MDT 2010 Update 1

In MDT 2010 Update 1 you can continue to install / deploy .msi applications as defined in the Deployment Share.

During the MDT Applications wizard one of the parameters to configure is the command line. This time we want to install .msi application packages:

1.Identify the true name / complete name of the .msi. For example:

the complete name of this application is essbe_nt64_enu.msi

2. You need to use the msiexec /i  as prefix to the name of the .msi application package name.

msiexec /i essbe_nt64_enu.msi /passive

Note: The /passive is a non-user interaction switch for the ESET ESS application used in this example. To find out our applications switches you may drag them to to a cmd and just add the /? .

On the move…

Isvet MVP