Group Policy Deployment of Office 2007 Enterprise

Hello,

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,

Matt
LVL 4
brownmattcAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

coolsport00Commented:
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?).

Regards,
~coolsport00
0
brownmattcAuthor Commented:
Hello,
I am not sure about a .ini file.  Do you happen to know of any documentation about how to create it?
0
coolsport00Commented:
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...

~coolsport00
0
brownmattcAuthor Commented:
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
http://technet.microsoft.com/en-us/library/cc179214.aspx
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
http://technet.microsoft.com/en-us/library/cc179195.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
coolsport00Commented:
Great info...thanks for updating "brownmattc". Sorry I hadn't responded...was on vacation and just now getting back. :)

Regards,
~coolsport00
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Office

From novice to tech pro — start learning today.