UEFI PXE x86 Deployment on Acer Aspire Switch 10 E

In Case you would like to Use UEFI Network Boot to install a fresh Windows 10 to a Tablet, then you Need something Special. In my case the Environment Looks like this:

Have a Installed Configuration Manager 2012 R2 SP1 CU1 Installation
PXE enabled on my Primarysite Servers DP
Have a Acer Aspire Switch 10e Tablet (Aspire SW3-013)
and for this Tablet, you Need a Special Network to USB Adapter that PXE/Network boot is Possible, it Needs a ASIX AX88772B Chipset on it, or just use the acer Adapter (it’s just a 10MB, but it works) http://store.acer.com/store/aceremea/en_GB/pd/ThemeID.26339800/productID.284496300

Netzwerk to USB device



Next is this, Switch 10 E Tablet has a Atom Processor on Board, that Shows you a x64 Architecture, but in real it’s supports only x86 OS.
What we have done, we controlled to be shure that the x86 WinPE Boot Image is ready to start over PXE Boot, you see the Image ID on the Bottom of the Tablet when the download Begins.

Next step is that we make a Tasksequence ready, here are some Spezial things to do:
1. Create a TS with the Wizard “Create Task Sequence” select “Install an existing Image package” and click trogh. Important select the boot Image x86 WinPE. The next flagg is importatnt too, “Partition and Format the target Computer before installing the operating System” the other stuff are choises by your selfe.

2. In the End you got a TS with the Steps for UEFI Partitioning and BIOS Partitioning, what i have is when is start the Tablte the first time i got all UEFI Patitions in double, so in this case i create a “run commandline step” and create a Diskpart answer file to clean the full Disk first:
(Here are my WMI query to be shure just this Model do this: select * from Win32_computersystemproduct where name like ‘%Aspire SW3-013%’)

Command line: diskpart.exe /s .\Clear.txt
in the File:
select Disk 0
save this as Clear.txt and create a Package without a Program.
In the BIOS and UEFI Partition go to the Windows (Recovery) Partition and set the 1% “Use a percentage of remaining free space” to 100%, it should use the rest of the free space not only 1% of it 😉

3. Next step is Apply Operating System, here you can use the classic unattended.XML file as we know from older Deployment’s, but make the File open with the new ADK 10 “Windows System Image Manager” to be shure it’s Win10 ready.

4. In the Step “Apply Windows Settings” here i wrote a Blog post about the Lizense Key Problem: http://blog.colemberg.ch/2015/07/license-key-during-win10-deployment-tasksequence/

5. In the Domain Join Part we have now a joice, the Tablet is Used like a Own Device, so we don’t Need a Domain Joined Device, we set the Device to a Workgroup and when the Setup are finish we manualy join the Device to AAD (Azure-AD), by desigen is it not Possible to join a Device direct during OS-Deployment to AAD (if you have a Script or an idea let me know) the AAD Team told me this is a User interaction to Join a Device to AAD in case of a BYOD Szenarios.

6. Then we give the Tablet the Boot-critical Drivers and followed by step “Setup Windows and Configuration Manager”

Here is the First Reboot of the Device, if it commes Up with a failure it’s a Problem with the following:
Here the Massage you get on the Device after the Boot: ” Default boot device missing or boot failed. Insert Recovery Media and hit any Key then select ‘boot manager’to choose a new bootdevice or to boot recovery media”

I was looking a Long time to find the Problem in this case: In the smsts.log i can’t see anything, but then i found a Post about a Problem in the MSR Partition. The MSR Partition is for the Boot config in a UEFI Szenario and mapped automaticly to Drive S:, i was looking in this and saw that in the Folder S:\EFI\Boot it’s a File calling bootx64.efi, but we have installed a x86 OS, then i was changing the Apply “Operating System Step” to use a “Apply operating System from an orginal Installation source” and implement the Win 10 ISO sources. After that i controlled during the TS and now the Setup creates  the right file bootia32.efi in the Folder S:\EFI\Boot.
This Blog helps me to figure it out: http://blogs.msdn.com/b/steverac/archive/2013/09/13/osd-pre-stage-and-uefi-systems.aspx

This is a simple Workarround, hope it helps, and it’s only when you deploy x86 UEFI OS!

7. Next step i Implement two run command line steps to create a local User and them to the Local Admin Group:
NET USER <Username> “Pa$$w0rd” /ADD
NET LOCALGROUP “administrators” “<Username>” /add

8. In the end of the TS i got other challanges:
1. Remove the CM12 Client Agent and Install the Intune Agent
2. Make the Intune Agent ready in Registrie
3. Reset the Network Adapter MAC Adress

  1. I found a great articel from Peter van der Woude thank you Peter for sharing: http://www.petervanderwoude.nl/post/installing-the-microsoft-intune-client-directly-after-a-task-sequence/

  2. Set the following Regkey: %windir%\system32\reg.exe add HKEY_LOCAL_MACHINE\Software\Microsoft\Onlinemanagement\Deployment /v WindowsIntuneEnrollPending /t REG_DWORD /d 1

  3. I found a script on Gallery TechNet that helps to reache this Goal: http://blogs.technet.com/b/askpfeplat/archive/2014/07/28/how-to-use-the-same-external-ethernet-adapter-for-multiple-sccm-osd.aspx

Hope this helps, this Infos are “as is” please test it first



Leave a Reply


Get every new post delivered to your Inbox

Join other followers:

%d bloggers like this: