Sign in to follow this  
Followers 0
bickyz

Surface Pro4 - Start PXE over IPv6 on MDT 2013 U2



6 posts in this topic

Dear all,

We have MDT 2013 with Update.

We have been deploying Windows 10 to the HP/Dell computers without any issues.

 

We are trying to deploy Windows 10 to few brand new Surface Pro 4, however when pxe booting it displays following, then boot to the default Windows 10 after "Start PXE over IPv6"

We are using Microsoft Surface Ethernet Adapter usb dongle.

---------------------------------------------------------------------

>>Start PXE over IPv4.
Station IP address is x.x.x.x (ip obtained from dhcp server)

 

Server IP address us z.z.z.z (MDT server ip)

NBP filename is boot\x64\wdsnbp.com

NBP filename is 30832 Bytes

Downloading NBP file ...

 

Succeed to download NBP file.

 

>>Start PXE over IPv6.

---------------------------------------------------------------------

 

I have already done following:

 

Any help would be much appreciated, thank you.

 

 

 

 

 

post-24998-0-46115600-1474370761_thumb.jpg

Share this post


Link to post
Share on other sites


did you remove the dhcp scope options ?

Share this post


Link to post
Share on other sites

Hi anyweb,

Do I remove both of these ?

066 Boot Server Host Name = MDT/WDS server IP

067 Bootfile Name: = boot\x64\wdsnbp.com

 

Will removing these affect the pxe boot for the PCs with the legacy bios (non UEFI) ?

 

thank you

Share this post


Link to post
Share on other sites

Hi anyweb,
I have removed both 066 & 067 from the DHCP. None of the computers can now do PXE boot.
Switch config has IP Helper pointing to the DHCP server.

Computers with legacy BIOS tries to obtain the IP from the DHCP server then says PXE-E53: No boot filename received (screenshot attached)

 

 

and on Surface it says PXE-E18: Server response timeout (screenshot attached)

 

 

thank you.

 

post-24998-0-34708000-1474456719.jpg

post-24998-0-64724700-1474456721.jpg

post-24998-0-38938900-1474456724.jpg

Share this post


Link to post
Share on other sites

can you attach your smspxe.log file so we can see what it says, did you distribute both the x86 and x64 boot images to your pxe enabled dp ?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0