Windows 11 SCCM Languages Pack Gestion

Question

Hello to all ;)

Thank you for taking the time to read this post.

Indeed, it’s all in the title.

I would like to find a way to efficiently deploy language packs in SCCM for W11.

I tried this method: https://learn.microsoft.com/en-us/azure/virtual-desktop/language-packs

or the usual methods with DISM, but since there are several packs in FOD, it is more complex.

Thank you for your suggestions

Answer 1

Hello Lacroix Pierre-Jean,

Deploying language packs for Windows 11 using SCCM (System Center Configuration Manager) can be a bit more involved due to the changes in the architecture compared to previous Windows versions. However, it is certainly possible. Below is a general outline of the steps you can follow:

-Download Language Packs:

-Import Language Packs into SCCM through the Software Library

-Create a Language Pack Deployment Package using the wizard

-Create a task sequence in SCCM to deploy the language packs. You can use the "Install Package" step to install the language packs.

-Deploy the task sequence to the target devices or device collections where you want to install the language packs.

-Test the deployement on some target computers before spread to the network.

For a step by step guide, you can consult the next Microsoft article, which includes detailed explanation of the steps and also screenshots of the process:https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/app-management/deploy-language-pack

--If the reply is helpful, please Upvote and Accept as answer--

Answer 2

Good morning.

Thank you for your reply.

My problem is that my powershell scripts are not signed and therefore do not install my language packs with the Task Sequence.

Do you have a tutorial to create a configuration element in the compliance settings, to modify the SCCM client policy on the execution of Powershell scripts?

"PowerShell execution policy

Configure how Configuration Manager clients can run Windows PowerShell scripts. You can use these scripts for detection in compliance settings configuration items. You can also send the scripts into a deployment as a standard script.

Bypass: The Configuration Manager client bypasses the Windows PowerShell configuration on the client computer, so that unsigned scripts can run.

Restricted: The Configuration Manager client uses the current PowerShell configuration on the client computer. This configuration determines whether unsigned scripts can run.

All signed: The Configuration Manager client runs scripts only if a trusted publisher has signed them. This restriction applies regardless of the current PowerShell configuration on the client computer."