Windows 10: Win10 enterprise deployment, unattend.xml, secondary keyboard issue

Hi all!

I've encountered a little problem. I have multiple sites in several country where needed to deploy win10 with different language and keyboard settings.

Everything else is fine, all other countries are OK but czech and poland.. I need to apply keyboard setting so that cs-CZ (pl-pl) is default, en-US secondary.

I've configured unattend.xml file so that inputlocale is cs-CZ; en-US (pl-Pl; en-US).. it should work.. ? Well it doesn't. I've tried also with: 0405:0001045; 0409:00000409.. .Still same.. In OS there is only czech keyboard.. Of course I can add en-US keyboard manually but I need to have it automatically.. Why en-US won't be there seen automatically in list? Also when adding manually en-us then UI lang will change after re-login to cz-CS (I haven't applied any other ui lang than eng in unattended.xml)

I have input locale configured in 4 Specialize and 7 oobeSystem in xml file.

I'm using Win10 1511 ent x64, SCCM is CB..


Any ideas?

Thanks,

:)

 

Enterprise deployment

Unfortunately the answer to about all the "when" questions that haven't already been addressed by Microsoft is "There's no way to know." We'd have to wait for Microsoft to announce news on such a thing before we know. They tend to make announcements at
certain yearly events. The next event is MIX11 this month. So watch for announcements from that event.

 

Choose time zone during OOBE in Creator's Update?

Hello all,

I'm working on an image for an enterprise environment that we sysprep and then capture to apply to other machines. With the Anniversary Update, it asked the user to choose their time zone during OOBE. However, with the Creator's Update it has not been. It
only asks for Region and Keyboard and connects to network before logging in and going to the desktop.

Is there an unattend.xml setting or something that will enable choosing your time zone during OOBE with the Creator's Update?

 

Moi Radoter, tervetuloa Kymppi Foorumille *Smile

You could try adding locale input methods component in Pass 1 WinPE instead, I've had better results with it when passes 4 and 7 do not what I am expecting:



TechNet article about this: InputLocale

 

Terve Kari, kiitos *Smile

Ok, I'll give it a try. a customer did accept the fact, that en should be default.. But have to try your tip for future use *Smile. Thanks!

-