We have the following: 2008 Server w/ WDS, Printer Server Roles 2000 Server w/ DHCP Role WDS Setup: Default Folder location C:\RemoteInstall WDS is setup with Vista SP2 Image file straight from the disk (default install.wim) and Boot file (default boot.wim) these files were put in the following default directories all this was put in a default location by WDS. Image File = C:\RemoteInstall\Images\ImageGroup1 Boot File = C:\RemoteInstal\boot\x86\images\boot.wim DHCP Setup: DHCP is not listed on any scope in DHCP it's statically assigned The scope of the computer I'm trying to PXE boot has the following Scope settings for WDS Scope Option 66: "Boot Server Name" Scope Option 67: "boot\x86\images\boot.wim PXE Boot Client Results: I get a IP address I then get the following error PXE-T01: File boot\x86\images\boot.wim is not found at tftp PXE-T01: TFTP Error - File Not Found PXE-T01: Exiting Intel Boot Agent Question Can someone please explain to me why I'm getting this error and what I can do to fix this problem I've tried to change the file path to the ones that I see online ie (boot\x86\pxeboot.com or wdsnbp.com) and I get the same error. I'm at my wits end and not sure what to do please advise. Thank You.

Hi, Please run Wdsutil /Verbose /Progress /Uninitialize-Server on the WDS server first. If the issue persists, please verify whether your WDS is still in the legacy mode. If so, WDS should be configured to use startrom.n12. In addition, I would like to know whether you are using SCCM/SMS in your environment. Tim Quan

Ok I uninitialized the server and started over it still did not work (I even loaded a new image). The WDS server is running in Native mode. If you could go into more detail about the startrom.n12 is that something that is required only in Legacy mode or something I should try period? Also yes we do have SCCM in our environment, I'm not familiar with it's workings is there something that needs to be done there?

Hi, Thank you for the reply. Since you have SCCM installed, this could influence the PXE booting. I suggest discussing this issue in our Configuration Manager Operating System Deployment forum. They should be the best resource to troubleshoot this issue. http://social.technet.microsoft.com/Forums/en-US/configmgrosd/threads Tim Quan