{"id":2149,"date":"2016-02-08T17:25:27","date_gmt":"2016-02-08T15:25:27","guid":{"rendered":"http:\/\/blog.hosebei.ch\/?p=2149"},"modified":"2016-02-08T17:25:27","modified_gmt":"2016-02-08T15:25:27","slug":"windows-10-language-packs-localization-for-built-in-groups","status":"publish","type":"post","link":"https:\/\/blog.hosebei.ch\/?p=2149","title":{"rendered":"Windows 10 &#8211; Language Packs localization for Built-In Groups"},"content":{"rendered":"<p>Since the deployments of Windows 10 take more and more steam on, new adventures are rising up. The last one I&#8217;ve seen, was the fact, that a deployed Windows 10 Enterprise 1511 en-US with included language packs is ending up with localized named Built-In Groups, when selected another User Interface, than en-US.<!--more--><\/p>\n<p>You might say, no problem with that, but in my opinion in some circumstances it is quite more easy, to be able to use the same group named &#8220;Administrators&#8221; on all Machines, instead of using an SID. Anyway, I could not find any explanation about this topic, and may someone comment what I&#8217;m doing wrong, or respond me on twitter (<a href=\"https:\/\/twitter.com\/hosebei\/status\/696701264055369728\" target=\"_blank\">Tweet<\/a>).<br \/>\nI&#8217;m using a very simple unattended file:<br \/>\n<a href=\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/02\/windows10language01.png\" rel=\"attachment wp-att-2150\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/02\/windows10language01.png?w=300\" alt=\"UnattendFile windows 10\" width=\"300\" height=\"111\" class=\"aligncenter size-medium wp-image-2150\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/02\/windows10language01.png 638w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/02\/windows10language01-300x111.png 300w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><br \/>\nI used the same structure within System Center Configuration Manager and variables for years now, and never faced this issue on a Windows 7 or 8 deployment.<br \/>\nI also checked the setupact.log and can determine, that the values from the unattend.xml gets applied:<br \/>\n<a href=\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/02\/windows10language021.png\" rel=\"attachment wp-att-2154\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/02\/windows10language021.png?w=300\" alt=\"unattendgc.log\" width=\"300\" height=\"132\" class=\"aligncenter size-medium wp-image-2154\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/02\/windows10language021.png 1426w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/02\/windows10language021-300x132.png 300w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/02\/windows10language021-1024x450.png 1024w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/02\/windows10language021-768x338.png 768w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>But all the Built-In Groups are localized in German, so I&#8217;m ending up with a group named &#8220;Administratoren&#8221; instead of &#8220;Administrators&#8221;.<br \/>\nIs something wrong with my configuration, or is this a new behavior with Windows 10? Might someone can help me out on this, or can clarify that it happens to them aswell.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Since the deployments of Windows 10 take more and more steam on, new adventures are rising up. The last one I&#8217;ve seen, was the fact, that a deployed Windows 10 Enterprise 1511 en-US with included language packs is ending up with localized named Built-In Groups, when selected another User Interface, than en-US.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15,27,33,43],"tags":[],"class_list":["post-2149","post","type-post","status-publish","format-standard","hentry","category-configmgr","category-operating-system-deployment","category-sccm","category-windows-10"],"_links":{"self":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/2149","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2149"}],"version-history":[{"count":0,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/2149\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2149"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2149"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2149"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}