You deploy a Windows 7 image by using one of the following applications:
Microsoft System Center Configuration Manager 2007 (SCCM 2007)
Microsoft Deployment Toolkit 2010 (MDT 2010)
Microsoft Deployment Toolkit 2012 (MDT 2012)
The default system locale setting is changed.
The locale name (for example, sv-SE) is set correctly. However, the locale code in the registry remains set to 00000409 (en-US).
In this scenario, some applications display incorrect characters or languages. For example, in the example in the last bullet point, the page setup in Microsoft Paint remains set to U.S. (inches) instead changing to Metric (millimeters).
In some RUNAS/Impersonation scenarios, the LocaleName and Locale registry values are not in sync in Windows 7. For example, this may occur with an operating system deployment in System Center Configuration Manager 2007 when the deployment is run as a local system.
To resolve this issue, add a step to either the System Center Configuration Manager or Microsoft Deployment Toolkit task sequence to change the Locale value of the Default User profile (ntuser.dat) by using a batch file that is located in the machine build. This value is located in the following registry key:
For example, follow these steps:
Create a command file in C:\Temp that is called "SetLocale.cmd."
Copy and paste the following text into the new file, and then save the file:
Create a new file in C:\Temp that is called "Locale.reg"
Copy the following text into the new file, and then save the file:
======= Windows Registry Editor Version 5.00 HKEY_USERS\ntuser.dat\Control Panel\International] "Locale"="0000041D"=======
Add "C:\temp\SetLocale.cmd" as a new entry in the task sequence.
Note For MDT you will have to add it to the StateRestore phase.
Method 2 (for System Center Configuration Manager)
In system Center Configuration Manager, create a package. For example, create a package that is named "Unattend XML Scripts."
Create an Unattend.xml file that has the correct international settings in the Specialize and OOBE settings, and then save the file in the Package source folder. An example for Windows 7 x86 (32-bit) is as follows:
In the SCCM OSD task sequence, on the "Apply Operating System" task, set to "Use and unattended or Sysprep answer file for a custom installation," select the package above, and then type the name of the XML. For examply, type Unattend.xml.