Installing and Configuring Additional Languages during Windows Autopilot

I was experimenting with different ways to get additional languages installed and configured during Windows Autopilot and it proved to be an interesting challenge. The following is what I settled on in the end and what produced the results that I wanted.

Here were my particular requirements, but you can customize this per your own need:

• The primary language should be English (United Kingdom)
• An additional secondary language of English (United States)
• Display language should be English (United Kingdom)
• Default input override should be English (United Kingdom)
• System locale should be English (United Kingdom)
• The administrative defaults for the Welcome screen and New user accounts must have a display language, input language, format and location matching the primary language (UK / UK English)
• All optional features for the primary language should be installed (handwriting, optical character recognition, etc)

To achieve this, I basically created three elements:

1. Installed the Local Experience Pack for English (United Kingdom)
2. Deployed a powershell script running in administrative context that sets the administrative language defaults and system locale
3. Deployed a powershell script running in user context that sets the correct order in the user preferred languages list

This was deployed during Autopilot to a Windows 10 1909 (United States) base image.

Local Experience Packs

Local Experience Packs (LXPs) are the modern way to go for installing additional languages since Windows 10 1803. These are published to the Microsoft Store and are automatically updated. They also install more quickly that the traditional cab language packs that you would install with DISM.

LXPs are available in the Microsoft Store for Business, so they can be synced with Intune and deployed as apps. However, the problem with using LXPs as apps during Autopilot is the order of things. The LXP needs to be installed before the PowerShell script that configures the language defaults runs, and since PowerShell scripts are not currently tracked in the ESP, and apps are the last thing to install in the device setup phase, the scripts will very likely run before the app is installed.

To get around that, I decided to get the LXP from the Volume Licensing Center instead. Then I uploaded this to a storage account in Azure, where it gets downloaded and installed by the PowerShell script. This way I can control the order and be sure the LXP is installed before making configuration changes.

When downloading from the VLC, be sure to select the Multilanguage option:

Then get the highlighted ISO. The 1903 LXPs work for 1909 also.

Get the applicable appx file and the license file from the ISO, zip them, and upload the zip file into an Azure Storage account.

When uploading the zip file, be sure to choose the Account Key authentication type:

Once uploaded, click on the blob and go to the Generate SAS page. Choose Read permissions, set an appropriate expiry date, then copy the Blob SAS URL. You will need this to download the file with PowerShell.

Administrative PowerShell Script

Now lets create a PowerShell script that will:

• Download and install the Local Experience Pack
• Install any optional features for the language
• Configure language and regional settings and defaults

Here’s the script I’m using for that.

User PowerShell Script

Now we need to create a very simple script that will run in the user context. This script simply makes sure that the list of preferred languages is in the correct order, as by default it will look like this:

This script will run for each user that logs in. It won’t run immediately so the order may be wrong when you first log in, but it doesn’t take long before it runs. Create the script in Intune, remember to run it using the logged on credentials, and deploy it to your Autopilot AAD group.

English united states local experience pack что это за программа

Устранить ERR_CONNECTION_REFUSED ВКонтакте ERR_CONNECTION_REFUSED которая возникает при входе на ВКонтакте? Ответ на этот вопрос мы дадим в этой статье. Также расскажем о других, подобных ошибках… Подробнее » Err failed что за ошибка

Eshell операционка что это такое

• автор: admin
• 14.03.2023

Eshell операционка что это такое Доброго времени суток! непосредственно самой Windows (удобно, можно сразу же работать); Free DOS — бесплатная ОС без графич. интерфейса, совместимая… Подробнее » Eshell операционка что это такое

Error bios legacy boot of uefi only media что делать

• автор: admin
• 14.03.2023

BIOS LEGACY BOOT OF UEFI ONLY MEDIA при запуске Windows с флешки Для того, чтобы исключить возможные проблемы или загрузиться с полными правами администратора, вы… Подробнее » Error bios legacy boot of uefi only media что делать

English united states local experience pack что это

• автор: admin
• 14.03.2023

English local Experience pack — что это за программа и нужна ли она? (LXP) Приветствую друзья. Одно из неприятных явлений в Windows — установка непонятных… Подробнее » English united states local experience pack что это

Ecc registered что это

• автор: admin
• 14.03.2023

Типы оперативной памяти. Небуферизированная память, с ECC, регистровая с ECC. Всё больше людей сталкиваются с проблемой несовместимости оперативной памяти с компьютером. Устанавливают память, а она… Подробнее » Ecc registered что это

How to deploy Windows Local Experience Packs with Intune

One of the biggest issue with Windows servicing on Windows 10 is language packs, from Windows 10 1803 this will be fixed with Microsoft using Microsoft Store to deliverer language packs. The benefit of using store app for language packs is that they are not removed as part of the Windows servicing and will there for be retained when a end user is getting a new Windows build upgrade.

In this blogpost I will describe how you can deploy Language packs with Intune and Microsoft Store for Business (MSfB) based on the preferred language settings on the end user, and how to use Intune Company Portal as self-service for language packs.

• A Azure AD tenant
• Signup for Microsoft Store for Business
• Microsoft Intune (automatic deployment)
• Windows 10 1803

How to get the Language Packs from MSfB:

First you have to go to the Microsoft Store for Business portal: https://aka.ms/MSfB

Search for Local Expirence Pack

Select the Local Experience Pack you need in your organisation

Click “Get the app”

By getting the app it will go in your MSfB and you can use it with a deployment tool like Intune or SCCM – if you what the end user to use the private Store in Windows 10 you also need to get in in the private store.

Click “Get the app” do it for all the Local Experience Pack you need

And now it will get in your management tool like Intune or SCCM at next sync schedule – or you can initiate the sync manually.

How to deploy Local Experience Pack with Intune:

After the sync from MSfB you can see the Local Experience Packs in Intune – seletct one to deploy it.

In my case I selected the Danish Local Experience Packs

1. Click Assignments
2. Click group

In this case I will do it required based on the end user Preferred Language – so I have already created Azure AD dynamic groups based on the attribute. See the blogpost here.

Now we have to assign the Local Experience Packs

1. Select “Required”
2. Select “Include Groups”
3. Select “groups to include”
4. Select the dynamic language group for da-dk

You can also create assignment as available so that the end user can use the Intune Company Portal to install the Local Experience Packs.

Create a collection for Local Experience Packs

The reason for creating a collection in MSfB is so that the apps are grouped in the private Windows Store.

Create a collection:

1. Click your private store
2. Click Add collection

Give the collection a name – Local Experience Pack

Then you can add the Local Experience Packs to the collection

And now for the end user experience – in the blogpost I did 3 different thing – so there will also be 3 different user experience.

1. Local Experience Packs as required – the end user will not notice any thing in the installation
   
2. Available from Intune Company Portal – the end user will see it and can installed it on request
   
3. In the Windows Private Store – the end user will see it and can installed it on request

Share this:

Like this:

Like Loading.

Related

Published by Per Larsen

I’m a Senior ProgramManager at Microsoft in CxP Intune CAT, Technology Evangelist and public speaker. With analytical and business perspective, and constant searching for the best solution for the customers. Co-Organizer @ewugdk «Everything Windows User Group Denmark», and public speaker. Owner of the blog: Osddeployment.dk View all posts by Per Larsen

7 thoughts on “ How to deploy Windows Local Experience Packs with Intune ”

Fred says:

One last step missing – how can I configure the language I just install to be set as default? This does not happen automatically just because the LEP was added. What would be your preferred methoed – a PS script via Intune or something else?

Michael Brunker says:

From 1803 or later, does the local experience pack get installed/update automatically when you update Windows to a new feature release?

Conrad Zimmermann says:

So.. after more than 20 years of MS consulting I am for the first time ready to advice enterprises to switch to another OS.. MS is really doing something crazy with this OS.. Doing a serious corporate image with this @#@# require at least 3x the energy and costs than previous OS. I know MS is continually joking presenting crazyness as “enhancements” all allong the year, but this one is the too much one. : So to deploy this @### I have to implement : Prerequirement: A Azure AD tenant
Signup for Microsoft Store for Business
Microsoft Intune (automatic deployment)
Windows 10 1803 AS if doing a coporate image with SCCM, all the scripts, all the bugs, all the crapware, all the packaging, all the drivers issues, wasn’t enough.. What a #@#@#@# joke..

Matthew White says:

Nice post, the language pack covers the base settings, is there a way to push the additional language features without requiring admin details? I have pushed this out to a new 1809 deployment and all the users have a toast notification to install additional pieces which they cant do as they aren’t admins.

Aviad Raviv-Vash says:

Hello
I am sttopmed, because when I get to the step “After the sync from MSfB you can see the Local Experience Packs in Intune”, I am not able to see these apps at all… have they moved? Thank you.

Per Larsen says:

I have the same in one of my tenants right now – I’m investigating what is wrong. I have other tenants where it is working

Aaron McLaughlin says:

I work in a school environment and we are pushing the language pack to students in Japanese class. We are able to install the language pack using Intune, but afterwards when the student tries to enable Japanese and type in a Word document it will not type in Japanese. They click on the A icon in the task bar and select Hiragana, but it will not change to Japanese or stay on Hirigana. It’s like the keyboard is not installed or some other piece. Are there other packages that need to be installed in order for the students to be able to type in the language? Thanks

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

При подготовке материала использовались источники:

Installing and Configuring Additional Languages during Windows Autopilot

https://gshimki.ru/telefon/35/page/161

How to deploy Windows Local Experience Packs with Intune