AI2 has uploaded a patch.
Description:
Hello to all,
As I saw, there were several attempts to put language-support to AutoSPInstaller. This is a different approach. Instead of coding every language itself in the PowerShell scripts, the modifications use a “translation table”, so everyone can add his own language keys. The language is detected from the
OS-LCID (and, in some cases, on the locale ID in the $xmliput....LCID). I know, there is a little bit redundant code, but I don’t know, where to place best, so I put it in every modified function.
There is also another modification: If you install on SSDs you sometimes get a timing problem on the “CreateCentralAdmin” function. Adding a little “Sleep” will help.
A third region is, if you want to install SharePoint foundation, there is no PID necessary.
The last modification is, if you are running AutoSPInstaller remotely, but not with psexec, you’ll get a problem with “CreateUPSAsAdmin”. The approach of starting a new-PSSession won’t work on my mashine, but as I run the whole AutoSPInstaller with the execution policy Bypass, there is no need to give extra credentials to the start-process command.
These modifications are tested on AutoSPInstaller 3.96 (w SP2013 SP1 Support) from Mar 10. Just copy the AutoSPInstallerFunctionsCustom.ps1 and the SPTranslations.csv into the AutosPInstaller directory.
It would be great, if anyone can give me feedback on this topics. If it is widely tested, it could get the chance to get into the main source and we can use autospinstaller with ervery language we want.
It works fine with my automatic infrastructure installer scripts www.raucamp-consulting.de/ai2
Related to Paches Nr. 13871 and 10417
See you
Thorsten Raucamp