Win7 Pro. 64 Bit Input Language Issue

[RemoteAdmin]

I have done a lot of searching without any luck

I am using WDS and MDT 2010 to deploy Windows 7 Prof. 64 Bit. The issue I am having is the input language default to English United Kingdom instead of English United State. I have checked the unattended file and everything (InputLocale, SystemLocale, UILanguage, UserLocale, UILanguageFallback) referenced to en-US or 0409:00000409. I don’t see anything reference to en-GB or 0809:00000809. I am hoping someone on here can assist me on resolving this issue. Thanks

[MrJinje]

In WDS, have you both enabled unattended installations and associated the XML file with WDS for that (x64) architecture

Open WDS, Right Click on your Server, select properties, go to "Client" tab.

[RemoteAdmin]

Yes, but no luck

[MrJinje]

Did you do any language modifications using DISM.

What does you lang.ini say ?

DVD\sources\lang.ini

[RemoteAdmin]

I did not do any language modify. Here is what in the lang.ini

[Available UI Languages]

en-US = 3

[Fallback Languages]

en-US = en-us

[MrJinje]

Can you export your OS to a WIM and create an ISO, and see how that ISO installs in a VM. Then we can narrow down if it is the WIM itself or a WDS/MDT settings issue.

If that doesn't help, maybe we need more details, is this a vanilla RTM image, or a customized sysprep job, or some kind a vlite special. What exactly are we working with ?

[cluberti]

I've actually had that happen to me a few times with MDT - if you look in WSIM or notepad at the task sequence's unattend.xml in the control folder, it'll show en-us (0409), but when you load the image from MDT, it'll be GB instead of US. In those situations, I've had to completely demo the *entire* MDT install, shares, folders, files and all (short of my app package source files and OS WIM files) and reinstall. Once it starts, it will continue. You literally have to rip MDT out - recreating just the task sequences or bootstrap/custom.ini files won't fix it, for some reason.

It sucks completely, but I've run into it at least twice and once it's broken, that install of MDT is *always* broken (and it's always only en-us to en-GB - other languages continue to work just fine).

[RemoteAdmin]

Thanks all for your inputs, I would hate to reinstall MDT since I have mulitple sites and they are doing the same thing. I will do more searching on this, hopefully I don't need to reinstall MDT on all servers.

[MrJinje]

Let's not re-install everything and start wasting man-hours just yet. This is a simple problem and deserves a simple solution, just create a task sequence that switches the language back to American. Be warned, editing the registry may cause system instability and blah blah blah, I think if you follow this manual from Strider it will work out just fine.

http://www.techtalkz.com/tips-n-tricks/517...indows-7-a.html

It is not ideal, but if it's good enough for you, it's good enough for me. Report back.

On a side note, (pertinent to many other threads as well) I opened the LiteTouch.wsf and noticed this. It looks like they delete any existing unattend.xml files so integrating them into the WIM will not work. Not sure what other things they are doing under the hood, but I suspect some of these bugs are by design (or over-sight).

If oFSO.FileExists(oEnv("SystemDrive") & "\Windows\Panther\unattend\unattend.xml") then

oLogging.CreateEntry "Removing old " & oEnv("SystemDrive") & "\Windows\Panther\unattend\unattend.xml", LogTypeInfo

oFSO.DeleteFile oEnv("SystemDrive") & "\Windows\Panther\unattend\unattend.xml", true

TestAndLog SUCCESS, "Removed " & oEnv("SystemDrive") & "\Windows\Panther\unattend\unattend.xml"

End if

[cluberti]

It's because they're injecting the one created via the task sequence from the \Control folder in the distribution share. Seems more like a sanity check (so that you actually use the unattend you expect to use, even if you've managed to use a source with one integrated already) than anything else.

[RemoteAdmin]

Mr Jinje,

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\MUI\UILanguages\xx-YY is pointing to en-US so can not do anything there.

Here is my solution for now. In task sequence, I have a batch file to import an registry file which update two registry keys to 00000409 from 00000809. Here is my reg file:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Keyboard Layout\Preload]

"2"="00000409"

"1"="00000409"

[HKEY_USERS\.DEFAULT\Keyboard Layout\Preload]

"2"="00000409"

"1"="00000409"