Annoying edition upgrade bug

[localzuk]

I have a dozen Linx 10v64 tablets here, that come with Windows 10 Home on them by default. Reimaging them is a bit annoying, as it appears so far that I can't PXE boot. So, I have gone down the route of creating an ICD package file to upgrade the edition to Education.

 

That works fine. However, after then joining the machines to the wireless and then the domain, they won't log in. All usernames/passwords are "incorrect password". AD disagrees.

 

Looks like a bug - https://community.spiceworks.com/topic/1812057-incorrect-username-password-after-joining-a-domain-windows-10

 

Anyone got a quicker fix for this? Running the Windows Media Tool in "Upgrade" mode is a slower process than I'd hoped!

[sted]

have you tried running mdt from within windows as long as it has a nic it should be doable (or creating a bootable mdt usb pen)

[Oaktech]

You need a bootable USB stick my friend. I've written some instructions somewhere - I'll look them out.

 

Startech USB 3 PXE network adapter.

 

Or a non pxe network adapter and a USB stick.

 

This was done for the Linx pro tablets and the Acer w510, but I've followed an almost identical procedure for w10.

 

Things you need:

a working WDS server

the AIK for your version of windows

1x usb stick for initial build media

1x usb hub

1x usb keyboard

1x usb mouse

1x USB NIC card with drivers (I've got a startech one)

2x 4gb or bigger usb sticks

 

What I did was to place the windows media on a usb drive, use the usb host cable to connect a usb hub, connect the boot usb and a keyboard and mouse to the hub and boot the tablet off the stick. Install whatever flavour of windows you want - we used 8.1 enterprise and all of your software. Sysprep the machine as you would normally

 

Use the WDS server to create a capture image using the process in this article: http://social.technet.microsoft.com/...ge-in-wds.aspx when the image is created, mount it in the WDS console and inject the drivers for your usb nic, dismount it and copy it to one of the 2gb or bigger USB sticks. This is your capture stick. It is architecture dependent.

 

Use the capture stick to run through the process of sysprepping the machine onto your WDS server

 

Follow the instructions here to use the AIK to create a discover image https://technet.microsoft.com/en-us/...(v=ws.10).aspx mount the discover image in WDS and inject the USB drivers again.

 

Use this to boot and build the machine from your WDS server using the image you created before.

 

Simples!

 

Hopefully this will help you. It's PITA, but it is doable.

Edited June 29, 2017 by Oaktech

[localzuk]

Eugh. I was hoping to avoid doing a full reimage of them!

[Oaktech]

Eugh. I was hoping to avoid doing a full reimage of them!

 

It sucks, but once you've done it once you have it and it'll work for ages!