I've been reading a lot on these forums the last couple of weeks, mostly regarding SCCM etc, but at the moment I've got an issue I haven't been able to wrap my head around.
We're using a standard win 2k8 r2 domain environment. This environment used to contain a server with MDT 2010 and WDS 2008 (server 2008 r2), used for deploying win7 etc, the environment used to work pretty well.
Then somebody thought it was a good idea to buy some tablet computers, to be specific the HP Elitepad 900. Specs for this tablet computer indicate it is able to do PXE boot (there is an ethernet port on the docking), but due to limitations this only works using UEFI (BIOS not supported). After a lot of reading I found that wds 2008 does not support x86 uefi, so the server was upgraded (no fresh install) to windows server 2012 (with wds 2012) and mdt 2012 update 1.
Legacy computers are still able to PXE boot correctly (and complete installation), but UEFI machines, or machines starting in UEFI mode can't do this at the moment.
What happens is:
- boot the computer over network (or tablet), we mainly want the elitepad to get working (x86 uefi), but I've also tried booting another machine using x64 UEFI with the same result
- the following is shown:
>>Start PXE over IPv4, Press [ESC] to exit...
Station IP address is x.x.x.x
Server IP address is x.x.x.x
NBP filename is boot\x86\wdsmgfw.efi
NBP filesize is xxxxx bytes
Downloading NBP File
Succeed to download NBP file.
[EDIT] Not sure if it's NEP or NBP file, not very clear on the screen
Then the screen changes and I see:
Windows Depoyment Services (server IP: x.x.x.x)
Contacting Server (x.x.x.x): - (this is like turning / - \ - / - \ ...)
After a while (timeout)the computer shows:
Windows Deployment Services encountered an error:
Error Code: 0x102
What I've tried/changed so far:
Changed the NBP filename in DHCP options, it used to be boot\x86\wdsnbp.com (when not using UEFI), before changing this I simply got network error when trying to network boot.
Added NIC (and other) drivers in WDS 2012, regenerated the boot image afterwards etc.
Tried reinstalling WDS on a newly installed windows server 2012 (without mdt) in standalone mode.
Other stuff I can't think of at the moment :-)
PXE booting of our SCCM 2012 update 1 (only used for updates & endpoint protection at the moment), but with the same result
Any thoughts/ideas? I have a feeling I'm overlooking something stupid, but then again it may not be stupid.
Sorry I should have posted this in