Added a hotfix 968718 to SCCM to increase the block size. WinPE boot time has been decreased significantly. After you apply this hotfix, you can customize the ramdisk TFTP block size by using the following RamDiskTFTPBlockSize registry subkey: Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\PXEName: RamDiskTFTPBlockSizeTYPE: REG_DWORDValue: <the expected block size> WDS doc chapter 7: "We recommend that you go up in multiples (4096, 8192, 16384) and you should not set a value higher than 16384"The consequence of increasing the number past 16384:Corrupt packages... 64 kb might work on a newer computer but fail on an older due to BIOS support...I had to try 65536 and it was smoking fast but common sense ruled and I lowered it back to 16384.Has anyone else experimented with this and ran into any issues?I have to admit this is much easier to update nowwith areg key than using bcdedit...Thanks Quote of the day: "We're gonna wait for Windows 7"

This one can be kind of shady, it normally works fine in a lab environment but I have experienced some issues, when trying to use it in a live environment. Example 1. Network infrastructure, sometimes diffrent switches / routers make this setting brake, meaning in some areas / sites it will not work after you have cranked up the speed. Example 2. Diffrent models, diffrent NIC:s handles this setting better or worse, so more then often you will have a couple of models in your environment that will not work after you have changed this setting. It is really nice go increase the speed but test it thourally on all models / sites before you turn it on in a live environment. Thanks !

I have been running at 32768 at my current company for almost two years. We currently use Dell Latitude E series now but still have some leftover D series and they all work well. We also have a few Optiplex models and do not have issues with those either. I really can't vouche for any other vendors. Mike

Quick note here, YMMV and is dependant on the NIC in the system being booted and heavily dependant on your network infrastructure.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys