For many this is basics, but for some reason I seem to forget this from time to time. Therefore I have chosen to create a blog post to remember the steps.
Create the Office 2010 package as you normally would. Copy the Office CD to a share and add it as a New Package.
Remember to create the MSP file using the setup.exe /admin switch. These are the settings I use normally: 
Microsoft Outlook 2010 – Account Settings – Exchange – Automatically Configure profile
based on Active Directory Primary SMTP Address = Enabled
Microsoft Outlook 2010 – Account Settings – Rss Feeds – Turn of RSS Feature =
Enabled
Add Property HIDEUPDATEUI = TRUE
Set Outlook Profile to Modify Profile
I normally use a KMS server for key management. But this depends on the environment. Then you save these changes to office2k10Silent.msp and save it in the root of the office folder where setup.exe is located. In order to integrate the language pack as part of the setup I then copy the needed folders from the language pack cd: 
Every folder that is needed ends with the name of the language. (in my case .nb-no)
I then copy the config.xml file from the enterprise.ww or the proplus.ww folder to the same location as setup.exe is located. This name of this folder varies from the version you are deploying. Then I edit it like this:
<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" SuppressModal="Yes" AcceptEula="Yes" />
<AddLanguage Id="match" ShellTransform="yes"/>
<AddLanguage Id="en-us" />
<AddLanguage Id="nb-no" />
<OptionState Id="OfficeMUI" State="Local" Children="force" />
</Configuration>
Notice the match switch. When that is set the installation will find out if the OS is English or Norwegian and install the Office GUI with that language.
We then need to specify how to run the installation. I create a program inside the office 2010 package that runs the following command:
setup.exe /adminfile office2k10Silent.msp
That’s it. The config.xml file will be read because it is in the root of the directory. Microsoft documentations states that MSP files and updates can be put in the updates folder of the installation. This works great. The only thing I have noticed is that office
completely installs the entire office suite and then runs the .MSP file and "peels" of the options that you have chosen to exclude.
Happy deployment!
6 comments
2 pings
Skip to comment form ↓
Fredrik
October 1, 2010 at 11:51 am (UTC 2) Link to this comment
Is the part of the config.xml you posted above everyting you have in the config.xml?
I get an error sying that my config file is invald when I use the same code you have. Exept sv-se insted of nb-no
Oddvar
October 4, 2010 at 8:07 am (UTC 2) Link to this comment
Have you done everything else? copied folders over to the installation directory?
Fredrik
October 4, 2010 at 12:48 pm (UTC 2) Link to this comment
I do not know what I did wrong. But i solved it by using Microsoft Deployment Toolkit, and had it incorporate the extra language-pack.
1-klick install will make the users happy
My working config file ended up like this:
chandler
July 22, 2011 at 10:32 am (UTC 2) Link to this comment
I had the same Problem,
”- comes from Website
“- is required.
I changed these Signs an the xml worked.
LMS
September 11, 2011 at 3:51 pm (UTC 2) Link to this comment
Hi
We tried the installation with config.xml with just one line as below,
, then from command prompt we tried setup.exe /adminfile createdOCT.msp and the installation completed without installing the language pack. Please help us to relove the issue
Regards
Lal
Tom Josefsen
April 23, 2012 at 11:33 am (UTC 2) Link to this comment
Thank YOU! Works great!
Mvh Tom J.
Deploy Office 2010 with Different languages | Oddvar Haaland Moe's Blog
March 31, 2011 at 11:22 pm (UTC 2) Link to this comment
[...] seen on my previous post http://www.moe.am/index.php/2010/08/deploy-office-2010-with-integrated-language-packs/ I showed how to integrate language packs into one set of installation files for office. In that [...]
Deploy Office 2010 with Different languages | MSitPros Blog
January 17, 2012 at 10:41 pm (UTC 2) Link to this comment
[...] Oddvar Tweet As seen on my previous post http://msitpros.com/?p=271 I showed how to integrate language packs into one set of installation files for office. In that [...]