Archive for May, 2017

Introduction

There is presently a potential issue in setting language settings using unattend.xml when deploying Windows 10 1703 Enterprise x64. The language values may not be set during the OOBE / specialize phase. Errors may be logged in setupact.log. The blog I have written will go through how I have approached the issue.

In addition to this Paul Winstanley, who I have been exchanging information with on this matter, was unable to produce a working solution with the settings that have worked for me. He has ended up implementing different values in his unattend.xml after comparing my settings and logs. He was also seeing:

  • Win 10 hanging on the the ‘Just a moment’ screen indefinitely after a build
  • An error message ‘Oops something went wrong’ after the build had completed, which I was then allowed to skip past

Where I haven’t seen these problems.

His great write up on how he has approached the issue should be read and can be found here:

https://sccmentor.com/2017/05/20/windows-10-1703-language-pack-fun-and-games/

The Problem

Windows 10 1703 Enterprise has now been available in VLSC since early May. Eager for deployment testing I’ve updated my production environment with a new deployment and in-place upgrade task sequence and upgraded a few IT staff PC’s which is going well.

This process though wasn’t as straight forward as you would think. For starters I was getting problems with the OOBE processing step with my existing Windows 10 1607 unattend.xml settings. I wasn’t expecting this as you don’t normally have to change any language settings in an unattend file. Specifically I was seeing:

  • A prompt asking if I wanted to join my work network in the form of mydomain.com.au
  • A prompt asking what sort of display language I wanted to choose
  • Display language not being set correctly – AGAIN!
My Solution

I downloaded the following ISO’s:

  • SW_DVD5_WIN_ENT_10_1703_64BIT_English_MLF_X21-36478
  • SW_DVD5_NTRL_Win_10_1703_32-BIT_X64_MultiLang_LangPackAll_LIP_X21-35517
  • SW_DVD9_NTRL_Win_10_1703_64Bit_MultiLang_FOD_1_X21-35556

Extracted the Windows 10 1703 ISO and added to my MDT environment.

Created a new Build and Capture Task Sequence and added a step to:

  • Add the .NET 3.5 Framework Role
  • Remove unwanted modern applications
  • Enable the Windows Update steps

Using my existing build and capture environment I performed a build and capture to create an updated wim file with the latest updates. My build environment is as follows. Please don’t use ADK 1703 presently it has a nasty secure boot bug.

Server 1

  • Windows Server 2012 R2 x64
  • MDT 8443
  • ADK 1607

Server 2

  • Windows Server 2012 R2 x64
  • WSUS

Custom Settings.ini

[Settings]
Priority=Default

[Default]
_SMSTSORGNAME=%ORGNAME%
UserDataLocation=NONE
DoCapture=YES
OSInstall=Y
JoinWorkgroup=WORKGROUP
HideShell=NO
FinishAction=SHUTDOWN
DoNotCreateExtraPartitions=YES
ApplyGPOPack=NO
WSUSServer=http://%SERVERNAME%:8530

SkipAppsOnUpgrade=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipComputerBackup=YES
SkipBitLocker=YES
SkipSummary=YES
SkipRoles=YES
SkipCapture=NO
SkipFinalSummary=YES
SkipTimeZone=YES
SkipApplication=YES

EventService=http://%SERVERNAME%:9800

I’m then importing the captured wim into my Configuration Manager 1610 instance running ADK 1607 and MDT 8443.

The Task Sequence I’m using is using MDT integration.

Windows 10 1703 appears to have made some significant changes in how Language is used. For my language pack to correctly be set as the display language and to avoid OOBE display language prompts my Unattend.xml file has the following settings.

For English (Australia).

specialize pass
<InputLocale>0c09:00000409</InputLocale>
<SystemLocale>en-AU</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-AU</UserLocale>

oobeSystem pass

<InputLocale>0c09:00000409</InputLocale>
<SystemLocale>en-AU</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-AU</UserLocale>

<OOBE>
<ProtectYourPC>3</ProtectYourPC>
<NetworkLocation>Work</NetworkLocation>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
</OOBE>

For Dutch.

specialize pass

<InputLocale>0413:00020409</InputLocale>
<SystemLocale>nl-NL</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>nl-NL</UserLocale>

oobeSystem pass

<InputLocale>0413:00020409</InputLocale>
<SystemLocale>nl-NL</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>nl-NL</UserLocale>

<OOBE>
<ProtectYourPC>3</ProtectYourPC>
<NetworkLocation>Work</NetworkLocation>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
</OOBE>

The main difference is that UILanguage needed to be changed to en-US. When I initially had this set to en-AU or en-GB it would fail to change it during the specialize / OOBE phase with 1703.

Updates to Task Sequence

To facilitate deploying Windows 10 1703, I’ve created two new packages.

  • Windows 10 1703 MDT Deploy Settings Package – This contains my unattend.xml and customsettings.ini (note no changes to customsettings.ini was required)

  • Windows 10 1703 Language Pack Package – This contains my language pack and additional feature on demand components to add text to speech etc support. This is not needed if you just wish to add multi-lingual display support. For English (Australia) as per below.

  • For Dutch as per below.

If your modifying/copying an existing Task Sequence don’t forget to also update the package setting in the Apply Operating System Image step so that your updated Unattend.xml is used along with any Gather steps.

To import the language pack I have done much the same as for 1607, just with referencing the new package.

Results

The results are as follows with English (Australia). I have confirmed that Office uses English (Australia) and that browser spelling support both en-AU and en-US.

The results are as follows with Dutch:

 

For troubleshooting problems with language settings look at the UnattendGC.log that is located at c:\Windows\Panther\UnattendGC. As an example where I have applied the Dutch nl-NL language pack you can see that the settings have been processed successfully and logged.

Oh and by the way indexing is now definitely fixed in 1703 when searching from the taskbar. I applied this months May 2017 CU for 1703 and indexing continued to work 🙂

Cheers

Damon