MDT 2013 - PC's take ages to load litetouch .wim file

[JonThompson]

Hello,

 

I'm pretty new to MDT, but after updating our deployment share and rebuilding our boot images, PC's now take an age to load the LiteTouchPE_x64 .wim file.

 

The file now has a (2) after it in brackets, so Im assuming MDT is now using the new WIM files.

 

Has anybody come accross this before or know of a fix? I tried adding in a reg key to increase TFTP file size, but that seemed to make things even slower.

 

Thank You.

[caffrey]

What NIC's ? I've always had an issue with nvidia stuff - maybe try a different nic to see if makes a difference ?

[minimoo]

For the bit once the litetouch.wim is loaded, you might find Reducing Windows Deployment time using Power Management - The Deployment Guys - Site Home - TechNet Blogs speeds up the next stage.

 

How big is the litetouch file ?

[JonThompson]

Thanks, that link looks promising.

 

How big is the litetouch file ?

 

If it's the one in the boot folder it's about 350mb.

[minimoo]

also, registry key??

 

my understanding was it was in bcdedit in 2008/R2:

 

https://blog.uvm.edu/jgm/2010/11/04/tuning-microsoft-pxe-tftp/

https://technet.microsoft.com/en-us/library/cc731245(WS.10).aspx#BKMK_41

 

and moved to the GUI in windows 2012:

 

https://technet.microsoft.com/en-us/magazine/dn163597.aspx

 

Only thing to remember with the tfp size, you might find some NIC's don't like it. I remember increasing ours and finding certain machines stopped wanting to install so finding a middle ground. I've noticed sometimes that the litetouch boot feels slow, but given MDT task sequence run time is about 25 minutes (if ssd at least), i'm not sure I care.