deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 05:17:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update Language-pack-management-csp.md

Browse Source
This commit is contained in:
Daniel Simpson 2021-06-23 13:28:04 -07:00 committed by GitHub
parent c8d156c735
commit 769114b749
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 27 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
windows/client-management/mdm/Language-pack-management-csp.md
View File

@ -14,43 +14,55 @@ ms.date: 06/22/2021
# Language Pack Management CSP
Language Pack Management CSP allows a direct way to provision language packs remotely in Windows 10. A separate CSP exists to allow provisioning of optional Features On Demand (FOD) which include handwriting recognition, text-to-speech, etc. associated with a language. device management tools like Intune can use management commands remotely to devices to configure language related settings.
The Language Pack Management CSP allows a direct way to provision language packs remotely in Windows 10. A separate CSP exists to provision optional Features On Demand (FOD) which include handwriting recognition, text-to-speech, etc. associated with a language. Device management tools such as Intune can use management commands remotely to devices to configure language related settings.
Device context
1. Enumerate installed languages with GET command on the "InstalledLanguges" node:
1. List the installed languages with GET command on the "InstalledLanguges" node. For example:
Sample command
**GET./Device/Vendor/MSFT/LanguagePackManagement/InstalledLanguages**
**GET./Device/Vendor/MSFT/LanguagePackManagement/InstalledLanguages /zh-CN/Providers**
**GET./Device/Vendor/MSFT/LanguagePackManagement/InstalledLanguages /ja-JP/Providers**
```
GET./Device/Vendor/MSFT/LanguagePackManagement/InstalledLanguages
GET./Device/Vendor/MSFT/LanguagePackManagement/InstalledLanguages /zh-CN/Providers
GET./Device/Vendor/MSFT/LanguagePackManagement/InstalledLanguages /ja-JP/Providers
```
The nodes under “InstalledLanguages” are the language tags of the installed languages. The “providers” node under language tag is the bit map representation of either "language pack (features)" or "LXPs". 1 indicates the language pack installed is a System Language Pack (non-LXP), “2” stands for LXPs installed. “3” stands for both installed.
The nodes under **InstalledLanguages** are the language tags of the installed languages. The **providers** node under language tag is the bit map representation of either **language pack (features)** or **LXPs**. The value of **1** indicates the language pack installed is a System Language Pack (non-LXP), **2** indidcates that the LXP is installed. **3** indicates that both are installed.
2. Install language pack features with EXECUTE command on the "StartInstall" node of the language
Sample command
2. Install language pack features with the EXECUTE command on the **StartInstall** node of the language. For example,
```
**ADD./Device/Vendor/MSFT/LanguagePackManagement/Install/fr-FR/**
**EXECUTE./Device/Vendor/MSFT/LanguagePackManagement/Install/fr-FR/StartInstallation**
```
The installation is an asynchronous operation. IT admin can query the ‘Status’ node by using the following commands:
The installation is an asynchronous operation. You can query the **Status** node by using the following commands:
```
**GET./Device/Vendor/MSFT/LanguagePackManagement/Install/fr-FR/Status**
**GET./Device/Vendor/MSFT/LanguagePackManagement/Install/fr-FR/ErrorCode**
```
Return value definitions are:
- 0 – Not started
- 1 – In process
- 2 – Succeeded
- 3 – Failed. ErrorCode is a HRESULT that could help you diagnose the issue and why installation failed
Status: 0 – not started; 1 – in process; 2 – succeeded; 3 – failed. ErrorCode is a HRESULT that could help diagnosis if the installation failed
> [!NOTE]
> If the IT administration has not set the policy of blocking cleanup of unused language packs, then this command will fail.
> If the IT administrator has not set the policy of blocking cleanup of unused language packs, then this command will fail.
3. Delete installed Language with the DELETE command on the installed language tag. The delete command is a fire and forget operation. The deletion will run in background. IT admin can query the installed language later and resend the command if needed.
3. Delete installed Language with the DELETE command on the installed language tag. The deletion will run in background, and admins can query the installed language later and resend the command if needed.
Sample command
```
**DELETE ./Device/Vendor/MSFT/LanguagePackManagement/InstalledLanguages /zh-CN (Delete command)**
```
4. Get/Set System Preferred UI Language with GET or REPLACE command on the "SystemPreferredUILanguages" Node
Sample command
```
**./Device/Vendor/MSFT/LanguagePackManagement/LanguageSettings/SystemPreferredUILanguages**
```