MDT 2013 | 3rd party PXE booting LiteTouchPE_x64.wim
Posted on 2013-12-06
I've got a scenario where the MDT & WDS server is Disallowed from being local to each building location. Plus, the WAN links are not strong at the separate offices, so I'm having to be creative with workarounds to minimize WAN traffic.
Already have a solution in hand to replicate the DeploymentShare folders to each site, outside of DFS-R (Syncrify)
I've discovered that the appliance handling DHCP for all the network segments has PXE functionality, via its BOOTP options. I've already got my testing segment reaching out to my local TFTP service and downloading the file specified in BOOTP.
However, the loader complains about BCD folders, so something with the folder structure or prepared files I"ve put on the TFTP server (tftpd32) is out of whack.
I've noticed most of the files required sitting in the c:\DeploymentShare\Boot\x64 location, and sub directories. I'd like to have PXE automatically load up into the DeploymentShare\Boot\LiteTouchPE_x64.wim file.
Are these files able to be used just as they are, in place, for 3rd party PXE? Which should be specified as the first file loaded/transferred from the TFTP server? (pxeboot.n12, wdsnbp.com, boot.sdi, bootmgr, etc.)
Will I have to perhaps create a special BCD file to repurpose these existing files?
Would changes to the DeploymentShare necessitate an update to the BCD?
Thanks in advance for all the wonderful tips and assistance!