Jump to content











Photo
- - - - -

SCCM PXE/TFTP


  • Please log in to reply
3 replies to this topic

#1 sebus

sebus

    Frequent Member

  • Advanced user
  • 305 posts

Posted 12 November 2015 - 09:12 PM

Anybody has any idea if there is a better way to deliver bootable .wim to client from SCCM, but WITHOUT using the c***py TFTP that is build in to WDS?

wimboot from http would be perfect (maybe one day in distant future Microsoft does manage to catch up with rest of the world...)

 

sebus



#2 sebus

sebus

    Frequent Member

  • Advanced user
  • 305 posts

Posted 13 November 2015 - 04:14 PM

Well, after doing the dll hack as per this the speed is OK, apart from the fact that now I can not PXE boot any Vmware based VM



#3 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1986 posts
  • Location:Nantes - France
  •  
    France

Posted 13 November 2015 - 06:20 PM

have you considered tweaking your BCD to adapt tftp (client) settings?



#4 sebus

sebus

    Frequent Member

  • Advanced user
  • 305 posts

Posted 13 November 2015 - 07:04 PM

Sure, done that together with the dll adjustment, works OK (minus the VMware VM boot)

 

RamdiskTFTPBlockSize = 16 with hacked dll and corresponding setting in bcd, makes 450 Mb .wim download in Optiplex 3020 in 10 seconds.

Same wim booting Hyper-V 2012 R2 VM with legacy network (only one that can do PXE boot) takes under 1 min

 

sebus






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users