This content has been marked as final. Show 9 replies
Yes. That's the simplest way.
Would I need to create special new file set to inlude them all, or create multiple file sets (grouping the same language and sometimes multiple keyboard maps in each) and assign them all to each machine object?
Any preference to each method?
Use the file sets the way we distribute them, just include all that you need.
So it seems that we would need to assign 15 filesets to each machine (to support all languages and keyboard maps).
Would then users need to manually select them in pre-boot, before typing anything (user name and password)? Is there any way to avoid this manual process and set those (language and keyboard) during Client Upgrade?
Do you know anyone, in the real world, that is using 15 or more language file sets for each of 20K+ machines?
It will pick one based on the windows settings. Yes lots of people deploy all the languages. It doesn't matter how many, 1, 10, 20 etc. No difference. See my blog for info on how it works.
I have just made a fresh Client install and it didn't pick keyboard type to match Windows one (Irish). I have applied most of language file sets to this machine object, including one for UK, which contains Irish KB.
Does this autodetection work on each synch?
Read my blog. It explains it all. Probably your keyboard Id in windows does not match the code we use. It's easy to link them though if it is indeed the same map.
Ok. I've read it. Autodetection is designed to work only once - during boot record replacement. So language file sets must be present at that time.
But it failed to do so in Irish KB case. Windows reports 00001809 code, ther was no ID Map Entry listed as "1809.Keyboard" and no match was made.
I wonder why this was excluded from LanguageIDMap section in Locale.ini in "EEPC51 LANG: English United Kingdom/USA..." file set.
Interesting - there is a 1809.Keyboard in my English locale.ini file, (0009.DELanguage directory), and a Keyboard.1809 section etc, but as you say, no automatic mapping entry.
you can add this yourself simply by editing the locale.ini file in the 0009.declient directory, then updating the same file in the database with this new copy.
Recreate the install set and it should detect fine. I would log a ticket with McAfee about this bug you have discovered wink