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

Discussion in 'Windows Server' started by Arch Willingham, Mar 15, 2007.

  1. 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.


    Arch Willingham, Mar 15, 2007
    1. Advertisements

  2. Arch Willingham

    Nick Payne Guest

    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.

    Nick Payne, Mar 16, 2007
    1. Advertisements

  3. Does your have a pxeboot.com anywhere on the disk?
    Arch Willingham, Mar 16, 2007
  4. Arch Willingham

    John Guest

    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.
    John, Mar 16, 2007
  5. 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.


    Arch Willingham, Mar 16, 2007
  6. Arch Willingham

    gcw009 Guest

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

    Worked for me.

    EggHeadCafe.com - .NET Developer Portal of Choice
    gcw009, Apr 3, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.