{"id":659,"date":"2011-06-28T21:46:54","date_gmt":"2011-06-28T20:46:54","guid":{"rendered":"http:\/\/www.autoitconsulting.com\/site\/?p=659"},"modified":"2025-07-26T12:54:11","modified_gmt":"2025-07-26T11:54:11","slug":"setting-a-uk-keyboard-in-configmgr-2007-osd","status":"publish","type":"post","link":"https:\/\/www.autoitconsulting.com\/site\/deployment\/setting-a-uk-keyboard-in-configmgr-2007-osd\/","title":{"rendered":"Setting a UK Keyboard in ConfigMgr 2007 OSD"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Overview<\/h2>\n\n\n\n<p>In the UK, we actually get the US version of Windows 7 and Office 2010, so whenever I do any build engineering in either MDT or ConfigMgr one of the first things I need to customize are the regional settings. In particular the keyboard layout and location. There are many ways to achieve this ranging from manually making the change in a reference image or creating an unattend.xml file. In this post I will show how you can set regional settings for Windows 7 at deploy-time using ConfigMgr 2007 OSD and collection variables. This will allow you to automatically have different settings depending on which ConfigMgr collection a machine belongs to. The process shown in this post is for UK settings, but the method will work equally well for any other regional requirements.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Collection Settings<\/h2>\n\n\n\n<p>First, on a collection used for OSD deployment select<strong> Modify Collection Setttings<\/strong> and goto the <strong>Collection Variables<\/strong> tab. Enter the following variables:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OSDSystemLocale:<\/strong> en-GB<\/li>\n\n\n\n<li><strong>OSDInputLocale:<\/strong> en-GB<\/li>\n\n\n\n<li><strong>OSDUserLocale:<\/strong> en-GB<\/li>\n\n\n\n<li><strong>OSDUILanguage:<\/strong> en-US<\/li>\n\n\n\n<li><strong>OSDUILanguageFallback:<\/strong> en-US<\/li>\n<\/ul>\n\n\n\n<p>Note: A common error is trying to use a value of <strong>en-GB<\/strong> for the <strong>UILanguage <\/strong>&#8211; there is no such UI setting, Brits have to make do with American spellings in our Microsoft products&#8230; The collection variables should now look like this:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter\"><img loading=\"lazy\" decoding=\"async\" width=\"400\" height=\"447\" src=\"\/site\/wp-content\/uploads\/2011\/06\/collection_variables.png\" alt=\"\" class=\"wp-image-667\" title=\"Collection Variables\" srcset=\"https:\/\/www.autoitconsulting.com\/site\/wp-content\/uploads\/2011\/06\/collection_variables.png 400w, https:\/\/www.autoitconsulting.com\/site\/wp-content\/uploads\/2011\/06\/collection_variables-268x300.png 268w\" sizes=\"auto, (max-width: 400px) 100vw, 400px\" \/><\/figure>\n\n\n\n<p class=\"has-text-align-center\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Unattend File<\/h2>\n\n\n\n<p>Now create a simple unattend.xml file using the <a title=\"Windows Automated Installation Kit\" href=\"http:\/\/www.microsoft.com\/download\/en\/details.aspx?displaylang=en&amp;id=5753\" target=\"_blank\" rel=\"noopener\">Windows Automated Installation Kit<\/a> and the <strong>Windows System Image Manager<\/strong> tool. You need to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Add the component <strong>amd64_Microsoft-Windows-International-Core_neutral<\/strong> to the <strong>specialize<\/strong> section. (use the x86 component if you are using a 32 bit version of Windows 7)<\/li>\n\n\n\n<li>Enter the &#8216;OSD&#8230;&#8217; variables we created above in the relevant sections wrapping them with % signs, for example <strong>%OSDSystemLocale%<\/strong> for the <strong>SystemLocale <\/strong>entry.<\/li>\n<\/ul>\n\n\n\n<p>When finished it should look something like this:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter\"><img loading=\"lazy\" decoding=\"async\" width=\"698\" height=\"204\" src=\"\/site\/wp-content\/uploads\/2011\/06\/edit_unattend.png\" alt=\"\" class=\"wp-image-671\" title=\"Edit Unattend File\" srcset=\"https:\/\/www.autoitconsulting.com\/site\/wp-content\/uploads\/2011\/06\/edit_unattend.png 698w, https:\/\/www.autoitconsulting.com\/site\/wp-content\/uploads\/2011\/06\/edit_unattend-300x88.png 300w\" sizes=\"auto, (max-width: 698px) 100vw, 698px\" \/><\/figure>\n\n\n\n<p class=\"has-text-align-center\"><\/p>\n\n\n\n<p>Save the unattend file in a suitable folder (I&#8217;m saving it in \\\\server\\ConfigMgr_SWStore$\\OSD\\Unattend\\<strong>Win7SP1x64_Unattend.xml<\/strong> &#8211; using the folder structure suggested in <a title=\"ConfigMgr 2007 OSD Folder Structure\" href=\"\/site\/deployment\/configmgr-2007-osd-folder-structure\/\" target=\"_blank\" rel=\"noopener\">this post<\/a>). I tend to put various unattend.xml files for different uses in the same folder then I create a single package for them all for simplified use &#8211; in this example I&#8217;ll call it <strong>OSD Unattend Files<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter\"><img loading=\"lazy\" decoding=\"async\" width=\"582\" height=\"186\" src=\"\/site\/wp-content\/uploads\/2011\/06\/unattend_folder.png\" alt=\"\" class=\"wp-image-674\" title=\"Unattend Folder\" srcset=\"https:\/\/www.autoitconsulting.com\/site\/wp-content\/uploads\/2011\/06\/unattend_folder.png 582w, https:\/\/www.autoitconsulting.com\/site\/wp-content\/uploads\/2011\/06\/unattend_folder-300x96.png 300w\" sizes=\"auto, (max-width: 582px) 100vw, 582px\" \/><\/figure>\n\n\n\n<p class=\"has-text-align-center\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Task Sequence<\/h2>\n\n\n\n<p>The final step is to attach this unattend.xml file to your OSD Task Sequence. Select the <strong>Apply Operating System<\/strong> task and enter the package and unattend file name in the <strong>Use an unattended or sysprep answer file&#8230;<\/strong> boxes:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter\"><img loading=\"lazy\" decoding=\"async\" width=\"528\" height=\"394\" src=\"\/site\/wp-content\/uploads\/2011\/06\/unattend_tasksequence.png\" alt=\"\" class=\"wp-image-676\" title=\"OSD Task Sequence\" srcset=\"https:\/\/www.autoitconsulting.com\/site\/wp-content\/uploads\/2011\/06\/unattend_tasksequence.png 528w, https:\/\/www.autoitconsulting.com\/site\/wp-content\/uploads\/2011\/06\/unattend_tasksequence-300x224.png 300w, https:\/\/www.autoitconsulting.com\/site\/wp-content\/uploads\/2011\/06\/unattend_tasksequence-510x382.png 510w\" sizes=\"auto, (max-width: 528px) 100vw, 528px\" \/><\/figure>\n\n\n\n<p class=\"has-text-align-center\"><\/p>\n\n\n\n<p>Now when you use this task sequence the collection variables will be expanded inside the unattend file and voila &#8211; per collection regional settings! You can also set these same variables directly on computer objects if you need to specialise for an individual computer.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview In the UK, we actually get the US version of Windows 7 and Office 2010, so whenever I do any build engineering in either MDT or ConfigMgr one of the first things I need to customize are the regional settings. In particular the keyboard layout and location. There are many ways to achieve this [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":662,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[59,62,91,27,68,21,6],"class_list":["post-659","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-deployment","tag-configmgr","tag-deployment","tag-mecm","tag-osd","tag-sccm","tag-unattend-xml","tag-windows-7"],"_links":{"self":[{"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/posts\/659","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/comments?post=659"}],"version-history":[{"count":6,"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/posts\/659\/revisions"}],"predecessor-version":[{"id":100127,"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/posts\/659\/revisions\/100127"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/media\/662"}],"wp:attachment":[{"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/media?parent=659"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/categories?post=659"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.autoitconsulting.com\/site\/wp-json\/wp\/v2\/tags?post=659"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}