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

Updated

Browse Source
This commit is contained in:
nimishasatapathy 2021-06-27 17:01:16 +05:30
parent f3a48169fa
commit 305560033d
2 changed files with 29 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -14,64 +14,40 @@ ms.date: 06/22/2021
# Language Pack Management CSP
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.
The Language Pack Management CSP allows a direct way to provision language packs remotely in Windows 10 and Windows 10 X. A separate CSP exists to allow provisioning of [optional FODs](/windows-hardware/manufacture/desktop/features-on-demand-language-fod) (Handwriting recognition, Text-to-speech etc.) associated with a language. MDMs like Intune can use management commands remotely to devices to configure language related settings.
1. List the installed languages with GET command on the "InstalledLanguges" node. For example:
1. Enumerate installed languages with GET command on the "InstalledLanguages" node
```
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**. The value of **1** indicates the language pack installed is a System Language Pack (non-LXP), **2** indicates that the LXP is installed. **3** indicates that both are 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)](/windows-hardware/manufacture/desktop/available-language-packs-for-windows) or [LXPs](https://www.microsoft.com/en-us/store/collections/localexperiencepacks?cat0=devices&rtc=1). The value of **1** indicates the language pack installed is a System Language Pack (non-LXP), **2** indicates that the LXP is installed. **3** indicates that both are installed.
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**
```
***ADD./Device/Vendor/MSFT/LanguagePackManagement/Install/fr-FR/**
**EXECUTE./Device/Vendor/MSFT/LanguagePackManagement/Install/fr-FR/StartInstallation***
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**
```
*****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 administrator has not set the policy of blocking cleanup of unused language packs, then this command will fail.
> If IT admin has NOT set the policy of blocking cleanup of unused language packs, this command will fail.
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.
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.
Sample command
```
**DELETE ./Device/Vendor/MSFT/LanguagePackManagement/InstalledLanguages /zh-CN (Delete 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**
```
**.*/Device/Vendor/MSFT/LanguagePackManagement/LanguageSettings/SystemPreferredUILanguages***

9
windows/client-management/mdm/policy-configuration-service-provider.md
View File

@ -1371,6 +1371,7 @@ The following diagram shows the Policy configuration service provider in tree fo
</dd>
</dl>
## ADMX_ICM policies
<dl>
@ -6781,6 +6782,14 @@ The following diagram shows the Policy configuration service provider in tree fo
</dd>
</dl>
### Language Pack Management CSP policies
<dl>
<dd>
<a href="./policy-csp-lanmanworkstation.md#lanmanworkstation-enableinsecureguestlogons" id="lanmanworkstation-enableinsecureguestlogons">LanmanWorkstation/EnableInsecureGuestLogons</a>
</dd>
</dl>
### Licensing policies
<dl>