MDT boot from network failure, is it UEFI related

[Davit2005]

We get as far as selecting network boot but then a message quickly pops up Downloading NBP file which succeeds but then straight after get network boot fail error.

 

The device is a Acer ICONIA W5 tablet and we specifically found the USB to Ethernet adapter. I'm sure if it was a boot image driver issue it would get further in than this.

 

Stumped :-(

[DavetheITguy]

it will be because the boot image hasn't got the drivers for the tablet or cannot boot onto the network correctly via usb to rj45. We had the same issue with the Linx tablets. We ended up building them using Clonzilla. If you are using Windows 8 you can perform an export of drivers using powershell.

[Davit2005]

it will be because the boot image hasn't got the drivers for the tablet or cannot boot onto the network correctly via usb to rj45. We had the same issue with the Linx tablets. We ended up building them using Clonzilla. If you are using Windows 8 you can perform an export of drivers using powershell.

 

I have a feeling that it is also due to the fact that I cannot get the Laptop into legacy mode. The drivers have been a right PITA to find also Acer support say my boot environment needs to support UEFI.

[sted]

iirc as long as you have server2012r2 as your wds server booting up a uefi system itself shouldn't be an issue. When we rebuilt 2 schools over summer we turned uefi back on on anything that supported it and have had no issues as a result. Might be easier if its only a few to boot them from a penstick to connect to mdt

[Davit2005]

iirc as long as you have server2012r2 as your wds server booting up a uefi system itself shouldn't be an issue. When we rebuilt 2 schools over summer we turned uefi back on on anything that supported it and have had no issues as a result. Might be easier if its only a few to boot them from a penstick to connect to mdt

 

Yep, seems to be what you are saying about better support in 2012 R2. Unfortunately our WDS/MDT was built a few years ago on 2008R2, I wonder if I can do an implace upgrade, we backup the server which is a VM with Veeam so shouldn't be too hard to go back.

 

Anyone done an implace upgrade of a server running WDS/MDT??

 

Have you got any steps for creating a USB which I can boot from??

Edited December 9, 2015 by Davit2005

[sted]

Yep, seems to be what you are saying about better support in 2012 R2. Unfortunately our WDS/MDT was built a few years ago on 2008R2, I wonder if I can do an implace upgrade, we backup the server which is a VM with Veeam so shouldn't be too hard to go back.

 

Anyone done an implace upgrade of a server running WDS/MDT??

 

Have you got any steps for creating a USB which I can boot from??

 

if its just wds/mdt it m ight be simpler if you have another 2012r2 server somewhere to just install wds on that and disable it on your existing server as a test but I don't see why it shouldn't upgrade ok

 

from usb not tried but mdt can create an iso I assume that's basically a win7/8/10 disk so in theory the win7 pen drive tool should be able to write that to a usb drive but ive not tried

[Davit2005]

if its just wds/mdt it m ight be simpler if you have another 2012r2 server somewhere to just install wds on that and disable it on your existing server as a test but I don't see why it shouldn't upgrade ok

 

from usb not tried but mdt can create an iso I assume that's basically a win7/8/10 disk so in theory the win7 pen drive tool should be able to write that to a usb drive but ive not tried

 

We have put a lot of time and effort into MDT and currently have it to the point where the build process is totally automated (once we get the switches for all the software correct). Not saying it impossible to get back to the same setup but it will be a task and not sure if we won't be without a MDT server till it's done.

 

I suppose I might try doing implace upgrade to 2012 R2.

Edited December 9, 2015 by Davit2005

[sted]

We have put a lot of time and effort into MDT and currently have it to the point where the build process is totally automated (once we get the switches for all the software correct). Not saying it impossible to get back to the same setup but it will be a task and not sure if we won't be without a MDT server till it's done.

 

I suppose I might try doing implace upgrade to 2012 R2.

you don't need to move mdt just wds they are separate wds just boots the pc from the network you can use the boot image mdt creates on a wds server that's not the same machine and once booted it does it all from the mdt server your config/task sequences wouldn't be affected

[Davit2005]

you don't need to move mdt just wds they are separate wds just boots the pc from the network you can use the boot image mdt creates on a wds server that's not the same machine and once booted it does it all from the mdt server your config/task sequences wouldn't be affected

 

Thanks @sted

 

I suppose then we just have to configure all the vLANS with the new WDS server as the IP helper address and away we go :-)

[sted]

Thanks @sted

 

I suppose then we just have to configure all the vLANS with the new WDS server as the an IP helper address and away we go :-)

 

my knowledge of vlans is very limited (i know what they are and that's about it its always been on my list of things to learn but I never have the equipment) but as far as I know yes