Jump to content


We use cookies to let you log in, for ads and for analytics. OK

Photo

Surface Pro4 - Start PXE over IPv6 on MDT 2013 U2




  • Please log in to reply
5 replies to this topic

#1 bickyz

bickyz

    Member

  • Established Members
  • PipPip
  • 16 posts

Posted 20 September 2016 - 11:25 AM

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.

 

 

 

 

 

Attached Images

  • surface-20sep16-02.jpg




#2 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,212 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 20 September 2016 - 06:58 PM

did you remove the dhcp scope options ?


Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#3 bickyz

bickyz

    Member

  • Established Members
  • PipPip
  • 16 posts

Posted 21 September 2016 - 07:01 AM

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



#4 bickyz

bickyz

    Member

  • Established Members
  • PipPip
  • 16 posts

Posted 21 September 2016 - 11:20 AM

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.

 

Attached Images

  • mdt-21sep16-03.JPG
  • mdt-21sep16-02.JPG
  • mdt-21sep16-01.JPG


#5 bickyz

bickyz

    Member

  • Established Members
  • PipPip
  • 16 posts

Posted 21 September 2016 - 01:06 PM

adding WDS ip to the IP Helper has resolved this.



#6 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,212 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 23 September 2016 - 11:14 AM

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 ?


Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users