Deploy Office 2007 or 2010 using Configuration Manager 2012

Deploying Microsoft Office 2007 or 2010 using  System Center 2012 Configuration Manager is a fairly simple and painless process. I’m going to assume you’ve sorted out your Office updates and customised your deployment msp to suit your needs. Once that’s done, here’s how I did it to successfully deploy either of these versions of office:


Ensure you have configured your .msp file first by running the Microsoft Office Customization Tool.  To do this, run the office setup with the /admin parameter eg:

setup.exe /admin

This will launch the OCT wizard.  Make sure you complete the licensing options (in my screenshot below we are using a KMS server), ensure that you tick ‘I accept the terms in the License Agreement’ and set display level to ‘None’ with ‘Suppress Modal’ being the only box ticked.

Complete the rest of the sections as you desire.

When you have finished your configuration, save the .msp file and place it in the ‘Updates folder’ in your Office directory.  For example, place it in ProPlusx86\Updates.  In there you will find various other msp files.  To ensure that it is read first, I named mine with a 1_ prefix.

Initial Configuration Stage:

– Create a new application:

– Browse to the ‘version’WW.msi file where you have placed your source media.  The name of this file will be dependent on which version of Office you are trying to deploy.  For instance, if you are deploying 2007 Enterprise then the msi is called: EnterpriseWW.msi.  If you are going to deploy Office 2010 ProPlus then the msi is called: ProPlusWW.msi.  If you’re not sure what it’s called just do a search for *WW.msi in your source directory to obtain the name and location.

In this example, I’m deploying  Office 2007 Enterprise.  Selecting the correct msi at this stage is the only difference between deploying 2007 or 2010 – all other deployment stages are the same.

– Follow the wizard though to the Summary then click next:

– Leave the default settings here and click next:

– Click next at the Summary screen:

Modify Stage:

– Now that the application has been created we need to make a couple of adjustments.  Right-click the deployment type and select Properties from the shortcut menu:

– On the Programs tab, change the Installation Program to ‘setup.exe

(Feel free to add windows source management info or any other properties like System requirements etc as you see fit) :

– For the final step, on the Content tab we need to modify the location to your Office 2007 or 2010 root media:

Deployment Stage:

– Now the application is ready for deployment.  Right-Click Microsoft Office Enterprise 2007 (Or the name of your application) and select the Deploy option in order to start the deployment wizard:

– Select which collection you would like to deploy to (In this example I choose a test collection containing one computer) :

– Select your Distribution Point:

– Select your installation type.  In this case I’ve made the application available so that the end user is able to install it at their lesiure:

– Select the schedule.  This example shows no schedule set so that the application is immediately available:

– …and the Summary screen:

On the Client:

– Here is the installation process as shown in the Software Center on the client computer:


– And finally it’s installed:











  1. I follow the steps, however, the installation on the client stuck at “installing” process. Any suggestion, does the license key havs impact on the process?

  2. Hi Leo,

    You will need to ensure that your msp file is configured first. I have updated the blog entry to reflect the essential changes that will need to be made in order for the deployment to succeed. Don’t forget to update your distribution point once you have created the msp.

  3. Thanks, I figure out that my installation source has some problem, i downloaded it from MSDN. Once i changes to another installation source from an Outlook 2007 installation disk, it works as charm.

Leave a Reply

Your email address will not be published.