| COMPLETE summary information for MOSS and WSS Language packs |
| Written by Administrator | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Friday, 04 December 2009 08:40 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
As there are many articles about LanguagePacks for WSS and MOSS, but none answered my questions at once, I had to start with this article with complete summary that is needed for language pack installation for WSS 3.0 and MOSS 2007 For each language. Following topics will be discussed:
Installation order of language packs + links When language pack should be installed / related issues What version of language pack are you running ? Languages and their codes (ID) Slipstreaming Language pack with SP1 /SP2 Automatization of language pack installation
Installation order of language packs: first of all, you need to download the language packs + related SP (recommended is SP2 of course) so you download WSS and MOSS LP from microsoft.com NOTE: there is only this link for all Languages, - you just need to Use the change language drop down to choose different language’s language pack download. This applies also for SP1/SP2 dowloads for language packs !!.
PS: when you do clean installation and you are on SP2 level on farm, you dont need to install SP1 first for language packs, it is included in SP2. So just install Language and then SP2. When language pack should be installed / related issues You should install language pack after you install WSS/MOSS + SP, but of course it is ideal situation, I had the case when I had to install additional language packs after SP2 and June cumulative update was installed. In this case you can install language pack without any problem (well I had problem that correct rights were not set properly on the STYLES folder in the 12 hive folder -read NOTE bellow.) If you install MOSS > then SP2 > then language packs > their SPs > then Cumulative udpate > you run Configuration wizard and you realise you need to install more languages, you can do that without a problem, just > Install WSS Language pack > its SP2 > MOSS language pack (if you are on MOSS) > its SP2 run the config wizard and you are ready to go. NOTE: I had to set read permissions for role - USERS in the "web server extensions\12\TEMPLATE\LAYOUTS\<LANGUAGE CODE>\STYLES" folders for all languages. What version of language pack are you running ? Answer to this question was found on : Patrick Heyde's blog Check registry WSS: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\InstalledLanguages\<LCID> MOSS: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\InstalledLanguages\<LCID> here you will see something like this: LCID - Reg_SZ - {language pack build level} 1033 - Reg_SZ - 12.0.4518.1000 1031 - Reg_SZ - 12.0.4518.1000 ... or LCID - Reg_SZ - {language pack build level} 1033 - Reg_SZ - 12.0.6219.1000 1031 - Reg_SZ - 12.0.6219.1000 WSS: REG.EXE QUERY HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\InstalledLanguages\ MOSS: REG.EXE QUERY HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\InstalledLanguages\ Languages and their codes (ID) When you want to check which pack is on lower level, or which folder you should check in case of need The following table lists the language packs that are available:
Slipstreaming Language pack with SP1 /SP2 This is very easy and very very handy, not that it just saves you one installation per language but it saves you time. Unfortunately ic cannot be automated completely. You cave to start installation of each WSS and MOSS lang pack manualy (there is annoying EULA and Config wizard starts after each install. But anyway, it is very handy as I wrote. Provided on: Joe Rodger's blog In case you didn’t know, you can slipstream server pack 1 (or the latest SP) of a language pack into the RTM service pack installation point, creating a single install point for each language pack include includes SP2. You may think, big deal, I’m saving one installation. That’s true, but if you have a a medium or large farm, it cuts the number of items you need to install by half, which can add up over time, especially if you have a dev and QA/staging environment you keep in sync. Unfortunately, you can only do this per language, so you still need to do one install per language, but every little bit helps. For WSS Language Packs (example here is for the Spanish language pack):
For MOSS Language Packs (example is for the Spanish language pack):
Automatization of language pack installation unfortunately as I wrote above, it is not very possible. You can slipstream your installation and create script to start each pack for you, but you will be asked for imput anyway. What you can do if you really want is to: Create costom Config.xml for the installation. it should have something like:
setup.exe /config config.xml - complete inforamtion about this is on : http://technet.microsoft.com/en-us/library/cc287749.aspx It should install you language pack and open Configuration wizard, you can cancel that one out using pskill and put into script following: timeout 15 "%~dp0\pskill.exe" psconfigui.exe /accepteula >nul And run installation of another language with same parameters and using same steps as above. I have tried to do this but without success, but you might be more skilled and achieve that. If it is the case feel free to inform me how to automate that ;) So this is it, these are pretty much all information you should need to spend 1-2 days playing around with the MOSS. Cheers KbNk;
Powered by !JoomlaComment 4.0alpha3
!joomlacomment 4.0 Copyright (C) 2009 Compojoom.com . All rights reserved." |
