Group Policy Deployment of Office 2007 Enterprise

Posted on 2009-07-08
Last Modified: 2012-05-07

I am trying to deploy Office 2007 Enterprise and I believe I have just about everything working correctly but I am running into some trouble with the Setup Customizations and the automatic integration of SP2.  When Office is installed on a machine it does not install the product key, company name or the service pack.  It appears to me that the installation is not running the .MSP files that are in the Updates folder.  Can anyone give me some hints as to what I might need to change?

I have a software installation policy assigned in a group policy object and the group policy object assigned to an OU containing my computers.  I have the security permissions on the Policy filtered to a group and all of the test workstations are members of that group.  I have run Office 2007 Enterprise setup with the /admin switch and created a customization file.  I have saved the customization file in the \\DeployShare\Office2007\Updates folder.  I have extracted Office 2007 SP2 files into the Updates folder as well. I have a total of 9 .MSP files in the Updates folder.

I am running Vista clients with SP2 and have an environment with one Windows Server 2003 Domain Controller and one Windows Server 2008 Domain Controller.

Any help on what I may not have configured correctly would be greatly appreciated,

Question by:brownmattc
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 40

Expert Comment

ID: 24802968
Did you configure your .ini file with the MSP? When I deployed 2K3, I ran the setup.exe file, which then 'called' the setup.ini file which in turn references all updates, patches, and MST's (MST for 2K3; I guess the customization is MSP for 2K7?).


Author Comment

ID: 24803156
I am not sure about a .ini file.  Do you happen to know of any documentation about how to create it?
LVL 40

Assisted Solution

coolsport00 earned 500 total points
ID: 24803199
It's part of the installation media. I understand there are several PRO11.MSI files (or I believe they're PRO12.MSI for 2K7) to install from. But, you also have a setup.exe file in the same location as those other install files. There should be a folder called "FILES", and in that folder is a SETUP.INI file. Double-click this file and it will open in a notepad window. There are 'Headings' for files you can add to the install.

Hope that helps...


Accepted Solution

brownmattc earned 0 total points
ID: 24816389
While the Office Customization Tool documentation says you only need to put the .MSP file in the Updates folder I found that I needed to modify the Config.xml file located in the Enterprise.MM folder in order to get the customization file to run correctly.

In particular you need to do most of your customizations from the Config.xml file and add in the following section in order to run the customization file:
      <Command Path="%WINDIR%\system32\msiexec.exe" Args="/p \\Share_Path\Office2007Enterprise\Updates\1_OfficeCustomization.MSP" QuietArg="/q" ChainPosition="after" Execute="install" />

The Updates folder is not processed when you deploy Office 2007 through group policy.  The Updates folder is only processed when you deploy through Setup.exe.

Documentation below

Applying customizations to the Office installation
Because of the way Setup runs when Office is installed, there are some limitations on the number of installation options that you can customize when you deploy the 2007 Office system with Group Policy-based Software Installation. The following limitations apply:

All customizations must be made in the Config.xml file. Setup does not apply Setup customization files that you create using the OCT. For more information about using the Config.xml file, see Config.xml file in the 2007 Office system.

The customized Config.xml file must be located in the main product folder of the product you are installing. Because you cannot specify command-line options for Setup when you assign Office, you cannot specify an alternate location for the Config.xml file. For example, if you are installing Office Enterprise 2007, you customize the Enterprise.WW\config.xml file.

You can customize only the Config.xml elements shown in the following table. These options are set when Office is assigned, and they cannot be modified later when Office is fully installed. All other elements in the Config.xml file are ignored.

Config.xml file in the 2007 Office system
LVL 40

Expert Comment

ID: 24894580
Great info...thanks for updating "brownmattc". Sorry I hadn't responded...was on vacation and just now getting back. :)


Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will guide you to convert a grid from a picture into Excel format using Microsoft OneNote and no other 3rd party application.
Outlook Free & Paid Tools
The viewer will learn how to make their project stand out over others by learning how to change colors and shapes, add spaces, change directions, and add bullets to their charts.
The viewer will learn how to simulate a series of sales calls dependent on a single skill level and learn how to simulate a series of sales calls dependent on two skill levels. Simulating Independent Sales Calls: Enter .75 into cell C2 – “skill leve…

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question