boot\BCD not found to pxe client

[pankajtakawale]

Im trying n/w booting windows PE 2.0 using PXE.

I followed all steps mentioned in WAIK "Deploy Image by using PXE"

I configured DHCP server and tftp server on same server (no need of 3rd party pxe server in this case)

I copied all windows PE files to \\PXEServer\TFTPRoot\Boot\ .

On PXEServer I configured TFTPD servers Directory registry entry [directory to search for Boot File] to C:\pt\TFTPRoot\Boot

dir \\PXEServer\TFTPRoot\ :-

tftpd.exe

Boot Directory

dir \\PXEServer\TFTPRoot\Boot :-

12/02/2006 06:19p <DIR> .

12/02/2006 06:19p <DIR> ..

07/27/2006 03:16a 79 abortpxe.com

12/02/2006 04:28p 262,144 BCD

07/27/2006 04:16a 3,170,304 boot.sdi

08/30/2006 03:01p 414,776 bootmgr.exe

07/28/2006 12:04a 25,356 hdlscom1.com

07/28/2006 12:04a 25,340 hdlscom1.n12

07/28/2006 12:04a 25,356 hdlscom2.com

07/28/2006 12:05a 25,340 hdlscom2.n12

07/28/2006 12:05a 25,052 pxeboot.com

07/28/2006 12:05a 25,052 pxeboot.n12

07/28/2006 12:26a 333 WdsConfig.inf

07/28/2006 12:26a 27,612 wdsnbp.com

08/30/2006 05:21p 160,874,081 winpe.wim

13 File(s) 164,900,825 bytes

2 Dir(s) 6,644,346,880 bytes free

I configured Boot File in DHCP server as pxeboot.com.

While n/w booting, client machine can not locate \boot\BCD.

PXE client is searching for "boot" folder in \\PXEServer\TFTPRoot\Boot , so I created "boot" folder under it and copied all files in this folder. It worked, but i dont want to keep redudant copies in 2 folders.

So I tried following configuration:

- tftpd's Directory registry entry [boot file directory] to C:\pt\TFTPRoot\

- only pxeboot.com in \\PXEServer\TFTPRoot\ and all other pxe files in \\PXEServer\TFTPRoot\Boot\.

It doesnt work, Client displays error "Tftp Download failed"

I think changing BCD configurations would solve the problem. Can any one please point me to appropriate link or suggest any solution?

Pankaj.

[Jazkal]

We had the same problem. I don't remember off hand how we fixed it, but come Monday I will ask our Linux Dev that found the fix, about it. I'll let you know on Monday what he says.

[Jazkal]

ok, make sure the Boot folder has a capital "B". And that the BCD file is all capitals.

Also check your /var/log/messages. You may have to lookup how to do the "TFTP slash hack", it's where "\" are converted to "/" or something like that. Sorry I don't have more info, but I'm not a linux guy.

[pankajtakawale]

ok, make sure the Boot folder has a capital "B". And that the BCD file is all capitals.

Also check your /var/log/messages. You may have to lookup how to do the "TFTP slash hack", it's where "\" are converted to "/" or something like that. Sorry I don't have more info, but I'm not a linux guy.

Thanks for your reply.

My tftp server is running on windows. I have already capital B, & capital BCD.

Regarding logging - i searched in logs in Tftp current directory & event logs - but no luck. Im using microsofts tftpd.exe (C:\windows\system32\dllcache\) to run TFTP server.

I will try using any other open-source TFTP server which supports logging. If you know logging mechanism of above mentioned tftpd would be helpful.

[Jazkal]

can you post your BCD config?

bcdedit -store %FULLPATH%\BCD

EDIT:

You can run bcdedit from Vista or PE2.

Edited December 5, 2006 by Jazkal

[pankajtakawale]

can you post your BCD config?

bcdedit -store %FULLPATH%\BCD

EDIT:

You can run bcdedit from Vista or PE2.

C:\winpe_x86\mount\Windows\System32>bcdedit.exe /store C:\BCD

Windows Boot Manager

--------------------

identifier {bootmgr}

description Windows VISTA BootManager

displayorder {cf06fe6c-820a-11db-bf00-000c29ab100f}

timeout 30

Windows Boot Loader

-------------------

identifier {cf06fe6c-820a-11db-bf00-000c29ab100f}

device ramdisk=[boot]\Boot\WinPE.wim,{ramdiskoptions}

description MyWinPE Boot Image

osdevice ramdisk=[boot]\Boot\WinPE.wim,{ramdiskoptions}

systemroot \Windows

detecthal Yes

winpe Yes

[Jazkal]

The only thing I see that "may" be a problem, is the name of your wim file. Try naming it exactly like what the BCD config file shows.