{"id":128,"date":"2021-01-27T22:08:45","date_gmt":"2021-01-27T21:08:45","guid":{"rendered":"http:\/\/m365-blog.de\/?p=128"},"modified":"2021-01-27T22:27:56","modified_gmt":"2021-01-27T21:27:56","slug":"windows-10-2004-20h2-use-lxp-in-task-sequence","status":"publish","type":"post","link":"https:\/\/m365-blog.de\/?p=128","title":{"rendered":"Windows 10 2004\/20H2 – Use LXP in Task Sequence"},"content":{"rendered":"\n

Last year I wrote a Blog Post<\/a> about Language Experience Packs (LXP\u2019s) within a 1909 OSD Task Sequence.  <\/p>\n\n\n\n

But I think no one of us still want to deploy this \u201cold\u201d OS and is looking forward to Windows 10 20H2. Fortunately, my colleague Markus just texted me last week with some optimization for the implementation of LXP\u2019s. <\/p>\n\n\n\n

I really liked it so here it is.<\/p>\n\n\n\n

Package: <\/h2>\n\n\n\n

You still need to apply the LXP Files you want in the Task Sequence. Alternatively, you can prepare your Image with the LXP files, if you want to\u2026 have a look at Michael Niehaus Blog Post for more Information about that: https:\/\/oofhours.com\/2020\/08\/11\/windows-10-2004-every-local-experience-pack-a-planet-wide-os-image\/<\/a> <\/p>\n\n\n\n

Download the LXP ISO for 2004 and extract the language you need to your Package Share destination (No new LXP\u2019s for 20h2 are released. You can use the LXP\u2019s for 2004). <\/p>\n\n\n\n

In my example I used the de-DE LXP\u2019s. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Create a SCCM Package for every extracted Language and distribute the content to you DP\u2019s. (If you need help how to create a Package, maybe this<\/a> Blog post can help you. Short note \u2013 we don\u2019t need a program). <\/p>\n\n\n\n

So now there is the cool Part. We just need three Task Sequence Steps to implement the LXP\u2019s for a Language.  <\/p>\n\n\n\n

Set Dynamic Variables: <\/h2>\n\n\n\n

First create a Set Dynamic Variables Task Sequence Step with the following Configuration to set the Language Settings which will be used in the Apply Windows Settings step.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Make sure to define the Location Variable (for example as a Variable Property on the Computer Object, Collectionvariable, additional Set Task Sequence Variable Step based on Computername,\u2026) in the Language Tag Format used by Windows \u2013 in my case for Germany \u201cde-DE\u201d.  <\/p>\n\n\n\n

Here you can look up the Language Tags: https:\/\/docs.microsoft.com\/en-us\/windows-hardware\/manufacture\/desktop\/available-language-packs-for-windows#language-packs<\/a> <\/p>\n\n\n\n

Install DEDE: <\/h2>\n\n\n\n

Use the Add-AppxProvisionedPackage command to Install the LXP. Link the Package with the described files above. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
powershell.exe\u00a0-executionpolicy bypass -command\u00a0\"Add-AppxProvisionedPackage -Path C:\\ -PackagePath .\\LanguageExperiencePack.de-DE.Neutral.appx -LicensePath .\\License.xml\"<\/pre>\n\n\n\n
You can create this Step for each language you want to install based on Variables. Double check the linked Package \u2013 you need to change this for each Language. <\/p>\n\n\n\n
Add FOD: <\/p>\n\n\n\n
The next and last step will install some German Features on Demand. Just a short reminder\u2026 Have a look at your execution policy for PowerShell Scripts ;). <\/p>\n\n\n\n
This Script can be used for any Language you want to install. So, no duplicated Steps for different Languages are necessary. <\/p>\n\n\n\n
\n
# Create an object to access the task sequence environment\n$tsenv = New-Object -ComObject Microsoft.SMS.TSEnvironment\n\n# Query the environment to get an existing variable\n# Set a variable for the language to use\n$lng = $tsenv.Value(\"Location\")\n\n# Get all available language capabilities\n# and install them from the Internet using DO if available\nGet-WindowsCapability -Online | where { $_.Name -like \"Language*$lng*\"} | Add-WindowsCapability -Online\n<\/pre>\n\n\n\n
<\/p>\n<\/div><\/div>\n\n\n\n
\"\"<\/figure>\n\n\n\n
So far so good \u2013 that was everything you need to know for the Win10 20h2 OSD TS. <\/p>\n\n\n\n
Make sure to check out my colleague Markus on Twitter: @MarkusBux <\/a><\/p>\n\n\n\n
Again, a few additional notes here which might help you…<\/p>\n\n\n\n