Tom_P Posted March 8, 2024 Posted March 8, 2024 (edited) Hey! So i know there are a few post already on this, but i cannot get MDT to set the keyboard layout to GB. Keeps setting US layout. This is only on the MDT setup screen, once the image is deployed the OS is set to GB. I have mounted the WIM file to check and the bootstrap.ini is correct. Cannot find the customsettings.ini file to check whats applied. But it must be set somewhere, as the settings inside the file are applying to the rest of the setup. Below are my bootstrap and custom settings file. Hopefully somebody can see where I've gone wrong. Bootstrap.ini [settings]Priority=Default [Default] DeployRoot=[DeploymentSharePath] SkipBDDWelcome=YES KeyboardLocale=0809:00000809 KeyboardLocale=en-GB UserLocale=en-GB InputLocale=0809:00000809 SystemLocale=en-GB UILanguage=en-GB UserID=[username] UserPassword=[Password] UserDomain=[Domain] CustomSettings.ini [settings]Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipCapture=YES SkipProductKey=YES SkipComputerBackup=YES SkipBitLocker=YES SkipUserData=YES SkipAdminPassword=YES AdminPassword=[Password] SkipDomainMembership=NO JoinDomain=[Domain] DomainAdminDomain=[Domain] KeyboardLocale=en-GB KeyboardLocale=0809:00000809 UserLocale=en-GB UILanguage=en-GB SkipTimeZone=YES TimeZoneName=GMT Standard TimeTimeZone=085 SkipLocaleSelection=YES true Work 1 true true true true true true SkipSummary=NO SkipFinalSummary=NO SLShareDynamicLogging=[Log] EventService=[Log] Edited March 8, 2024 by Tom_P
Olliedawg Posted March 8, 2024 Posted March 8, 2024 Hey! So i know there are a few post already on this, but i cannot get MDT to set the keyboard layout to GB. Keeps setting US layout. This is only on the MDT setup screen, once the image is deployed the OS is set to GB. I have mounted the WIM file to check and the bootstrap.ini is correct. Cannot find the customsettings.ini file to check whats applied. But it must be set somewhere, as the settings inside the file are applying to the rest of the setup. Below are my bootstrap and custom settings file. Hopefully somebody can see where I've gone wrong. Bootstrap.ini [settings]Priority=Default[Default]DeployRoot=[DeploymentSharePath]SkipBDDWelcome=YESKeyboardLocale=0809:00000809KeyboardLocale=en-GBUserLocale=en-GBInputLocale=0809:00000809SystemLocale=en-GBUILanguage=en-GBUserID=[username]UserPassword=[Password]UserDomain=[Domain] CustomSettings.ini [settings]Priority=DefaultProperties=MyCustomProperty[Default]OSInstall=YSkipCapture=YESSkipProductKey=YESSkipComputerBackup=YESSkipBitLocker=YESSkipUserData=YESSkipAdminPassword=YESAdminPassword=[Password]SkipDomainMembership=NOJoinDomain=[Domain]DomainAdminDomain=[Domain]KeyboardLocale=en-GBKeyboardLocale=0809:00000809UserLocale=en-GBUILanguage=en-GBSkipTimeZone=YESTimeZoneName=GMT Standard TimeTimeZone=085SkipLocaleSelection=YEStrueWork1truetruetruetruetruetrueSkipSummary=NOSkipFinalSummary=NOSLShareDynamicLogging=[Log]EventService=[Log] This is my bootstrap.ini if it is of any help. 1
Tom_P Posted March 8, 2024 Author Posted March 8, 2024 This is my bootstrap.ini if it is of any help. Thank you, unfortunately still US. I just noticed you said thats your bootstrap - Whats in your customsettings?
Olliedawg Posted March 8, 2024 Posted March 8, 2024 Thank you, unfortunately still US. I just noticed you said thats your bootstrap - Whats in your customsettings? Apologies I got them mixed up lol. The screenshot I linked is my customsettings This is all that I have in my bootstrap.ini [settings] Priority=Default [Default] DeployRoot=\\10.25.160.56\Data\MDTProduction 1
snagrat Posted March 8, 2024 Posted March 8, 2024 If you use UK (or British International it used to be called) media this isn’t a problem is it?
gaz350b Posted March 10, 2024 Posted March 10, 2024 If you use the English installer which is actually en_US you may find you have to install en_gb language files during install. Took us ages to realise that we actually should be using the international iso!
Tom_P Posted March 11, 2024 Author Posted March 11, 2024 If you use UK (or British International it used to be called) media this isn’t a problem is it? Its not a problem on the image, just the MDT setup screen. Becomes a problem when typing passwords as symbols are different.
snagrat Posted March 11, 2024 Posted March 11, 2024 Its not a problem on the image, just the MDT setup screen. Becomes a problem when typing passwords as symbols are different. So it is a problem….? Just use the International media and it is no longer a problem
Tom_P Posted March 11, 2024 Author Posted March 11, 2024 So it is a problem…. Just use the International media and it is no longer a problem Im not following you here.. how do i use international media when MDT creates the WIM file?
CHiLL Posted March 11, 2024 Posted March 11, 2024 Im not following you here.. how do i use international media when MDT creates the WIM file? You need to download the International version of the ISO from Microsoft and use that in MDT instead. That has the en-GB language packs included, whereas the English one only has en-US.
Tom_P Posted March 11, 2024 Author Posted March 11, 2024 You need to download the International version of the ISO from Microsoft and use that in MDT instead. That has the en-GB language packs included, whereas the English one only has en-US. I've just checked my OS files in the deployment workbench, and both win 10 & 11 are set as en-GB in properties. Am i looking in the right place? I thought these OS's were only applied after a task sequence was selected, and the wim files that the deployment workbench generates is what loads your MDT setup.
CHiLL Posted March 11, 2024 Posted March 11, 2024 I've just checked my OS files in the deployment workbench, and both win 10 & 11 are set as en-GB in properties. Am i looking in the right place? I thought these OS's were only applied after a task sequence was selected, and the wim files that the deployment workbench generates is what loads your MDT setup. The wim file has to be generated from a source ISO (or extracted from one). It sounds like you're referencing or using the English version as the reference that MDT is using. You will need to replace it with the English International version in order to change the settings that you want. 1
Tom_P Posted March 12, 2024 Author Posted March 12, 2024 (edited) For anyone having similar issues, I was missing the 'PE' after 'KeyboardLocale'. This is my working locale settings: KeyboardLocale=0809:00000809 KeyboardLocalePE=0809:00000809 UserLocale=en-GB InputLocale=0809:00000809 SystemLocale=en-GB UILanguage=en-GB I think its just required in bootstrap, but i applied it to customsettings too, as i didnt want to regenerate the image twice if it was required in both. Edited March 12, 2024 by Tom_P
Planehazza Posted April 4, 2024 Posted April 4, 2024 Something's rattling around in my brain about this issue a few years ago. I haven't touched MDT in a good while as it's SCCM at my current place. I do confidently recall having to set the system language to en-US but set input and region to en-gb Also, check Office. I have a very strong hunch that Office 2019 was installing as en-US and setting it to default. Very annoying, but I have fixed it on my current image setup
jthompson Posted April 4, 2024 Posted April 4, 2024 Not using the intl eng Windows ISO is usually the mistake I make.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now