Creating a package to install Microsoft Office 2010 x86

This post is the first in a series of posts explaining which settings I used to create certain packages and applications within SCCM 2012. I hope you find it useful.

First things first, you will need to create an installations settings package. This is done by opening a command prompt from within your Office source folder. An easy way to do this is by navigating to the folder and holding down shift and right clicking in a clear area of the folder. You can then choose “open a command prompt here”. Once the command is open, type the following command:

setup.exe /admin

You can set whichever settings you like here, but you must make sure to accept the EULA and set the display level to none on the licensing and user interface tab.

Setting the EULA and display level







Once you’ve made all the adjustments you need to this, save the file to the updates folder of your source folder as default.msp.

UPDATE: If you are using MAK activation instead of KMS, you will need to add the following code into your config.xml file, located in the ProPlus.WW folder

<Setting Id="AUTO_ACTIVATE" Value="1"/>

I won’t talk you through how to make a package, I’m sure you already know how to do that, the following is a summary of the settings that I have used to get my office package running. The settings are listed by tab, where the settings are different from default, after you have created the package.

Package Settings


This tab is just here for identifying your package. I used:

Name: Microsoft Office 2010 x86
Version: x86
Manufacturer: Microsoft
Language: English

Data Source

This package contains source files should be ticked, and the source path pointing to your source folder

Data Access

On this tab I have ticked the “copy the content in this package to a package share on distribution points” box.

Program Settings


Command line:

setup.exe /adminfile <path to source folder>\Updates\default.msp

Run: Hidden
After running: No Action Required


Program can run: Whether or not a user is logged in
Run Mode: Run with administrator rights
Drive Mode: Runs with UNC name


When this program is assigned to a computer: Run once for the computer
Suppress Program Notifications: Ticked
Allow this program to be installed from the install package task sequence without being deployed: Ticked

Windows Installer

Import the relevant MSI package from your source folder. For Professional Plus, this is ProPlusWW.msi in the ProPlus.WW folder.

I’ve got very fast results with these settings. I hope they help you in tailoring your solution.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.