Solved

MDT 2013 | 3rd party PXE booting LiteTouchPE_x64.wim

Posted on 2013-12-06
4
1,407 Views
Last Modified: 2013-12-13
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!
0
Comment
Question by:murraybd
  • 2
4 Comments
 

Accepted Solution

by:
murraybd earned 0 total points
ID: 39717989
I'd come across several posts on Griffon's IT Library (c-nergy.be/blog) related to MDT and PXE Network booting.

I was also able to find an earlier post that focused on the building of BCD files with BCDedit.

http://c-nergy.be/blog/?p=458

This allowed me to reconstruct the BCD files needed to allow my appliance PXE support to load the right WIM file as desired, on network booting.
The major restriction I was running into was being disallowed from using MS Server flavoured OS as the baseline for these distributed MDT installations.
Now I can host the Linked deployment shares on a Win7 workstation, with a TFTP daemon hosting the PXE and WIM files for network booting.
0
 

Author Closing Comment

by:murraybd
ID: 39717993
Further comments are welcome, but the major issue addressed in this thread has been resolved for now.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
While working, an annoying popup showing below will come and we cannot cancel or close it form the screen. The error message will come again and again.
This Micro Tutorial will give you a basic overview of Windows Live Photo Gallery and show you various editing filters and touches to photos you can apply. This will be demonstrated using Windows Live Photo Gallery on Windows 7 operating system.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question