This post was contributed by Patrick Zovistoski, a fellow community member. Thanks!
The following steps show how to configure your Task Sequence to automatically install an Office 2013 Language Pack that matches the language selected during the Deployment Wizard. Since it is deployed dynamically, it eliminates the need to include the Office Language packs in your image.
Update August 9, 2014: Added info about the source folder structure.
Import into MDT the Windows 8 Language Packs that you require.
Create a new application for each Office 2013 Language Pack that you require, using the following command line for setup: "setup.exe /Config .osmui.xx-xxconfig.xml" where "xx-xx" is the language you are adding.
Add a group to your Task Sequence with conditionals set for the "UILanguage" TS variable. For example, it will process the group only if "UILanguage" is not equal to English. Then, it will apply the appropriate sub-task depending on the value of "UILanguage":
Make sure to modify your rules/"CustomSettings.ini" to prompt for language selection in the Deployment Wizard:
Now when you select a non-English language in the wizard, it will automatically deploy the associated Office 2013 Language Pack:
Additional configuration notes
Each language has its own source folder, for example:
Each Language Pack is an independent application (note each language has its own app folder):
Make sure that you have the following entries in the "config.xml" file for each language (French example shown):
<Configuration Product="OMUI.fr-fr"> <Display Level="Basic" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <Setting Id="SETUP_REBOOT" Value="Never" /> </Configuration>
Thanks again Patrick, great contribution,
I don't remember if this configuration sets the default language or not.
Lets say you have an English version of Office 2013 included in the image and then select Swedish during the installation.
How do you get the Swedish language set as default displaylanguage instead of English during the installation of the language pack ?
I mean, otherwise the user have to choose this by himself afterwards, which is not nice 🙂
The blog post is now updated with info about the source folder structure, and the app configuration.
Are you creating seperate folders for each language and creating MDT applications or are you dumping all language packs into one single folder and creating MDT instances for each language?
While testing manually, I dumped all of languages into one single folder and using a specific language config.xml for executing with setup.exe.
I am getting "Choose a language" prompt even when i provided all the unattended values.
Backgroud: English Office is baked into the WIM. I am installing just language packs based on user selection in the deploy TS.
Setup.exe /config .omui.fr-frconfig.xml
First, please don't post unrelated questions to the blog post. This post is about language packs in MDT, hardly related to drivers.
Second, MDT does not support Post OS driver installations. You will have to install the drivers as applications if you want to have them installed Post OS.
I have selected " post OS installation task sequence template" because I need to install driver post os installation.
Hi, I am working on MDT 2013 for deployment of win8.1.Currently I am having issue with driver injection using out of box. Till now I had followed below steps: Downloaded driver from dell site. Imported drivers into Out of box drivers. Created selection profile. Created a task sequence(by selecting post OS installation task sequence template) for driver injection and selected above created profile. Under option tab I have created query.(if statement based on task sequence variable Model) When I deployed task sequence on machine none of the driver installed. Please guide me resolve this issue. Thanks in advance, Regards,Suresh.M.M. Regards,… Read more »
Again thanks for your prompt reply!
I'm going to get that book 🙂
Thanks for showing a little tip of the iceberg
Buy the "Deployment Fundamentals – Volume 4" book and you will see the structure I use 🙂
Shorthand: For applications I have one folder for each vendor, and then within the folder a descriptive name of the app, what type of deployment it is, and for what architecture. For example:
Install – Microsoft Silverlight 5.0 – x64
Install – Microsoft Visual C++ 2005 SP1 – x86-x64
Install – Microsoft Visual C++ 2008 SP1 – x86-x64
Configure – Microsoft IE 11 for Windows 8.1 – x64
Install – Adobe Acrobat Reader 11.0 – x86
Install – Adobe AIR 3.4 – x86
Again a great post and contribution.
I wonder, Johan, could you share some more information about the folder structure within MDT. I'm still looking for a logical approach on how to name folders and in what order I should name them.
Perhaps you can share some insight in your strategy!