Windows 10: In S-Mode image, language which was selected while initiating the deployment is not...

I have created a S-Mode ISO by modifying the unattend.xml using ADK tools (DISM & SIM). While deploying I have selected the language as Spanish (even for some other language as well), But after deployment while at the OOBE screen, the language selected is English by default which is suppose to be Spanish as per earlier selection. Here I have to select the respective language every time at OOBE.


I used Windows 10 RS5 (1809).


Any one please help me in resolving this issue.


Thanks,

Devanathan

:)

 

Customize Windows 10 Image in Audit Mode with Sysprep  

I am sorry but I do not understand that, "select INSTALL...". You should not have that selection when deploying, you simply mount the deployment image and the installation (deployment) will be automatic.

• Configure your image in Audit Mode
• Create the Answer File
• Sysprep
• Capture the image
• Deploy

That's it. The Microsoft TechNet article I linked to in my previous post explains the procedure.

 

Language

Hi Sassy,

To remove the Croatian language in Windows 10, we suggest that you follow these steps:

• Open the Settings app, select Time & Language, and click
  Region & Language.
• Under Add a language, select English, and click
  Set as default.
• Select the Croatian language and click Remove.
  
• Close the Settings app, restart the computer, and check if the issue persists.
  

Let us know if the steps provided worked for you.

 

Customised Windows 10 deployment on multiple desktops and laptops.


OK, after giving this a thought and thinking how I would do it, here's my suggestion. Please notice that, as I said, this is how I would do it. Other geeks might disagree with parts or all of it.

I tested this scenario using one Hyper-V VM as technician machine (the one to build image) and three virtual machines to test simultaneous deployment in two scenarios:

• Capturing install.wim from technician machine and using DISM to apply / deploy image from a network share
• Capturing install.wim from technician machine, making ISO from it, deploying by clean installing from ISO burned to Flash drive

Based on the fact that ISO method is clearly faster and simpler, it is what I suggest to you. I estimate you would need an hour and half to two hours to customize install image, capture it and make an ISO, then assuming you would make 5 Flash drives for install / deployment you would need about half an hour per five machines, in other words you would deploy to those 25 new machines in less than three hours, almost a full working day to deploy those 50 existing ones.

Two working days, day 1 to make the image and deploy to new machines, day 2 to deploy to old ones.

Chronological workflow based on my suggestion:

Phase 1, Image customization tutorial, parts One through Six:

• Install Windows 10 on a technician machine (I recommend Hyper-V VM but any capable PC is OK)
• Boot to Audit Mode
• Update Windows, install software, customize & personalize Windows
• Sysprep

Phase 2:

• Capture the install.wim from technician machine as told in this tutorial, Part Four steps 4.1 through 4.5 (physical PC as technician machine) or Part Four steps 4.6 through 4.13 (Hyper-V VM as technician machine)
• Create ISO as told in same tutorial, Part Five
• Burn / write ISO to as many Flash drives as you want to / need to for simultaneous installs
• Boot production machines from Flash drive, install Windows 10

The above is how I would do this. If you choose the DISM method instead, applying install.wim from a network share, see this Microsoft support article: https://technet.microsoft.com/en-us/.../hh824910.aspx

For more advanced deployment using MDT see this article: https://technet.microsoft.com/en-us/.../dn475741.aspx