This case is very common: As a good practice, you’ve installed Office in your reference image. When came time to deliver to your international users, you’ve probably used something similar to what Patrick Zovistoski offered to the community on Yohan’s blog.
While this solution is a really wonderful peace of MDT Art, it simply won’t feet in the multi-language area as it is only able to install one Office language pack per deployment.
If you’ve already stumbled upon part 1& 2 of my Multi-Language series, you now known that MDT needs enhancement to properly support more than one language.
Today we will bring Office 2013 (Not tested, but should works on 2010 too) to the mix and tweak the installation in order to install every Office language pack that matches the UI languages you selected in the wizard.
How it works
I’ve created an all in one script that can install language packs and OCT.
The language pack part works like this :
- The script search if MDT has records of Windows language packs to install or if the OS as languages already installed
- It will then verify that an Office LP counterpart exit.
- If it found a match, it will dynamically create the required setup.xml file to install Office in your preferred flavor
This method works from one to any number of Language packs but, don’t require to create an application per language like in the Patrick Zovistoski method.
How to install
Note: this script assume that Office 2013 has been previously deployed ( whether with a sysprep reference image or earlier in the same task sequence).
Download the script InstallOfficeLP.wsf
Create an application, and configure it to execute the command cscript.exe InstallOfficeLP.wsf
In the application folder, the following files should be present
- The script InstallOfficeLP.wsf
- Any Office LP you wish to install embedded in a sub folder named accordingly (de-de, fr-fr etc..)
- if you have one ; your OCT file (.MSP)
Finally, your application need to be launched during a task sequence.
End of holydays transmission !!
Diagg