it chooses the language on activation from the list in the IDMap based on the country codes reported by Windows.
this is done prior to downloading any patches or updates to the file sets.
so, if you include all the languages in your install set, the choice will be made based on Windows current settings, if however you selected language sets AFTER the fact (and did not include them in the install pack), then the default behavior is to apply that language immediatly.
you can change this by removing the defaultlanguage/keyboard lines from each individual locale.ini file in each language file group. This turns the language from a "apply now" to "add to the list of choices".
What does it mean "the choice will be made based on Windows current settings" ? The settings of Default User on the given computer will be used ?
the settings of the desktop that the activation happens under, so usualy that of the localsystem account.
What do you mean by 'localsystem account'? Is this valid for local user account?
Will this be working when migrating from old to a newer version, and changing the theme?
will what be working?
Again, only the installer checks and sets the language/keyboard settings, and only if the machine is not currently active.
The question is the following: When migrating machine from an old(4.2) to a new version(5.2.2), we always get default English(US) layout.
Is it possible to get the Windows layout on the PBA instead of the default English?
Not during migration.
use the linkuser.vbs script as part of your migration - it will re-evaluate the layouts and pick the most appropriate one.
If one decides to do custom code deployment to assist migration, choices are not limited to "linkuser.vbs", which is not a part of EEM/EEPC product.
We customize Locale.ini in relevant language file sets and push those to appropriate machines (by assigning appropriate file set to machine) during custom, non-silent Client upgrade. We check for many other conditions, fix lots of issues and communicate via GUI to user, what is going on and what user is expected to do (or not to do) during upgrade time.