How to speed up PXE boot in WDS (MDT)

 

During a PXE boot, when the boot image file is being loaded in the client, it should not take any longer than a few minutes time depending on the size of the boot.wim and your network. If it seems that your PXE boot times are extremely slow, you may be able to speed up the process by increasing the TFTP block size. This article will show you how to speed up PXE boot in WDS and SCCM.

Trivial File Transfer Protocol (TFTP) is the network protocol used for downloading all files during network boots. TFTP is an inherently slow protocol because it requires one ACK (acknowledgment) packet for each block of data that is sent. The server will not send the next block in the sequence until the ACK packet for the previous block is received. As a result, on a slow network, the round-trip time can be very long.

Change the Maximum Block Size to 16784 on your WDS server Winking smile

image

PXE booting fails with "PXE-T04: Access Violation" and "PXE-E36: Error Received from TFTP Server

I had a very strange issue. After updating to MDT 2013 and ADK 8.1 wen a client response getting error PXE-T04: Access Violation” and “PXE-E36: Error Received.

Solution:

Uninstalling WDS role
Reboot
Installing WDS role

Configuring WDS

Add MDT boot Images.

It works again.

WDS was corrupted Great Sad smile

WAIK Add Drivers to a Wim File

Some handy Windows 7 Waik commands to add drivers to a wim file.
Before you start copy the wim file to your harddisk

1. Some information about the Wim:
Dism /Get-WimInfo /WimFile:d:\boot.wim

2. Mount the wim file to a folder:
Dism /Mount-Wim /index:1 /WimFile:d:\boot.wim /MountDir:d:\mountpe

3. Add the Driver:
Dism /Image:d:\mountpe /Add-Driver /Driver:d:\nic\b57nd60x.inf

4. Close the wim file and saving the file:

Dism /Unmount-Wim /MountDir:d:\mountpe /Commit

De gemaakte Deployment Point Image “LiteTouchPE_x86.wim” Toevoegen aan Windows Deployment Services (WDS)

Onder E:DistributionBoot vind je 2 bestanden LiteTouchPE_x86.wim en LiteTouchPE_x86.iso

De WIM kun je aan WDS aan hangen onder Boot Images en de ISO kun je branden als je toevallig een netwerkkaart kaart hebt die geen PXE ondersteund.

clip_image001
clip_image002
clip_image003
clip_image004
clip_image005
clip_image006
image

64 bit Windows PE niet te zien in Windows Deployment Services

Zie je het volgende artikel voor het gemiste x64 in PXE.

http://technet2.microsoft.com/WindowsVista/en/library/9e197135-6711-4c20-bfad-fc80fc2151301033.mspx?mfr=true

Je moet x64 aanzetten als je 64bits OS wilt uitrollen via WDS zie het volgende stukje tekst:

• x64-based client computers do not receive an x64 Windows PE boot image. This can occur if the PXE basic input/output system (BIOS) implementation of the network booting computer does not correctly identify itself as being capable of working with x64-based computers. To work around this issue, enable architecture detection in the boot programs. To do this, run this command on your WDS server:

Commando: WDSUTIL /set-server /architecturediscovery:yes

Windows Deployment Feature op Windows 2008

1. Installeer WAIK op de Server die WDS moet gaan verzorgen.

2. Als eerste heb ik Windows Deployment feature geïnstalleerd.

3. Daarna heb ik WDS Server geconfigureerd. Zorg dat je de remoteinstall map op een harde schijf zet met genoeg ruimte.  

4. Daarna heb ik onder Install Image groep aangemaakt genaamd Ward waar alle gemaakte Images bewaard kunnen worden.

clip_image001

5. Ik heb ook een paar opties geconfigureerd. Zie de volgende scherm afbeeldingen

clip_image002clip_image005

clip_image003clip_image004

Vergeet niet op de DHCP Server optie 60 te configureren.