We all use a minimum of one operating system language on our computers. It may be likely that a company that has many employees may end up with several nationalities.
This means, more is required in your operating system deployment. When a MUI Pack is installed, the user interface language can be change to one of 33 supported languages. In this post, we will extend hardware inventory in SCCM 2012 to inventory multilingual user interface pack information. Here’s the steps in order to achieve this goal:. Custom WMI Class. Package Creation. Package Deployment.
Hardware Inventory. Verification Pre-requisites Download from TechNet Gallery.
Unzip the file. Copy ps1 in your package source directory.
File Troubleshooting › MUI Files › Microsoft Windows Server 2016 Language Pack. Browse MUI Files in Alphabetical Order.
Copy Operating System Multilingual User Interface Pack.zip where you can reach using UNC path Let’s get started! Custom WMI Class MUI languages information is in WMI class. We will create a new custom WMI Win32OperatingSystemMUILanguages class by using a PowerShell script. Open a command prompt or PowerShell with higher privilege (run as administrator). Navigate to the place you copy the PowerShell script in the pre-requisites section. Execute this command: PowerShell.
Exe –executionpolicy bypass –file Win32OperatingSystemMUILanguages.ps1 You should see something like that in your WMI repository. Now that we have test the PowerShell script on one computer, let’s scale to all devices in your environment. Package Creation We will create a package to successfully run the PowerShell script on multiple machines. Open the SCCM console. Navigate to Software Library / Application Management / Packages.
Click on Import button in the upper ribbon. From Import Package Wizard in General windows, select the UNC path where you copy the package ZIP file and click Next. In File Content, click Next. Click Close The package will be created in the package root folder. Move the package to your package source folder. Right click on the package and click Properties. Select Data Source tab.
Check the box The package contains source files and select your source path of PowerShell script. Click Ok Package Deployment You’ve finish to import the package. The goal is to run the script silently and repeatedly to ensure that the data is updated after any change to the user.
We don’t want the user to be aware each time it is running.
Featured Articles This document describes the characteristics of the different language packs that Microsoft provides for Windows 7. It provides information on the parts of the product that are localized, the licensing considerations that apply, and the availability depending on the language pack type.
Also covered are the localization differences between a localized version of Windows and one after a language pack has been installed. This section of the WAIK (Windows Automated Installation Kit) describes the language packs available in Windows 7 and the multilingual deployments scenarios supported in Windows 7. This white paper, targeted at IT professionals working on Windows image deployments, describes the step-by-step process to create a multilingual Windows 7 image for international deployment scenarios. Learn how to use registry string redirection with MUI, to use the registry in a language-neutral fashion.
Multilingual design considerations for publishing event descriptions to the Event Log. Multilingual design considerations for managing group policy files. Learn techniques for localizing WMI class information, by separating language-neutral and language-specific versions of the class definition.