SP2 RIS to WDS conversion gives PXE-T01: File not found errors

Yesterday, I upgraded the server 2003 running RIS to SP2. I have run through
all the steps I can find to finish the conversion to WDS.

Now when I boot a PXE client, it gives these error messages:
PXE-T01: File not found
PXE-E3B: TFTP Error - File not Found

I went to the WDS console and then the properties of the Windows Deployment
Services boot properties page. Under x86 architecture, it was defaulted to
boot\x86\pxeboot.com. I searched the drive and there is no file named
pxeboot.com. I changed it to Boot\x86\wdsnbp.com. This allowed the PXE
client to at least give another message. It then starts trying to hit the
info for the x64 client.

Any ideas on where to go from here? I just want it to be able to let a
remote client boot like it did before I applied SP2.

Thanks!

Arch

I upgraded an x64 RIS server on our test lan to SP2 and had no problem with
RIS/WDS not working afterwards. I tested both x86 and x64 builds.

Does your have a pxeboot.com anywhere on the disk?

From the Vista CD, you can get the .WIM file and allow you to create the
pxeboot.com file.

If you don't have a Vista DVD, you're not going to be able to work outside
of Legacy mode. To return to Legacy mode, run WDSUTIL /Uninitialize-server at
a command prompt.

I downloaded the kit and installed it on my workstation. It ends up
installing a file called "C:\Program Files\Windows
AIK\Tools\PETools\x86\winpe.wim"....is this the .WIM file I need? What do I
do with it?

I know these questions sound stupid but I have scoured ever article I could
find and I have yet to figure out the answer.

["Greg"]

So Arch did you find a solution?

Change the boot program for x86 to OSChooser\i386\startrom.com

Worked for me.

[willm952]

Hi,

I was flustered for 2 days. 1st I figured out that isa server was denying all traffic after a fresh install. so undid that.

next I did set dhcp options under Scope Options to:
060 PXE Client
066 Boot server host name (name or IP)
067 Bootfile name > pointed to remoteinstall\oschooser\i386\startrom.com

my laptop still gives PXE-T01 error > file not found TFTP

finally figured out the problem

on Windows Deployment Services (has to be running in mixed mode)
..if it says native mode you'll need to uninstall/reinstall and select mixed mode
dhcp tab needs to have checked do listen port 67 +
Configure dhcp option 60 to "PXECLIENT"

Next click BOOT Tab > x86 architecture
> should read OSChooser\i386\startrom.com

if it shows pxebootrom.com > there's your rat.

Changed that 1 setting > laptop picks up RIS server > prompts for login
> logged in with admin login > setups like a champ.


the whole reason i got into this was that my laptop doesn't have a cdrom built in and won't boot off of usb connected cd rom.

Hope this works for you.

[eworkman]

Same results here but also have a new issue now. It seems that both broadcom and intel teamed nics are having a problem with spanning-tree. We are running spanning-tree on Cisco 3750 switches with no problems until SP2 was installed. I'm not sure what could have changed that would have an effect on spanning-tree but we turned it off and the problem goes away. The issue is the build never starts as it stops with a tftp timeout. Any ideas?