|
Menu |
5. TroubleshootingBoot processHere's a simplified overview of the boot process that the PXE clients go thourgh when this method is used.
C->S DHCP request for IP
S->C Acknowledges IP request and gives the client a (free) ip-address
C->S DHCP request for bootserver/file
S->C DHCP Reply for bootserver/file SERVER:/boot/myserver/wdsnbp.0
C->S TFTP Request for bootfile /boot/myserver/wdsnbp.0
S->C TFTP Reply /boot/myserver/wdsnbp.0
C->S BINL request (where can I find the BCD file?)
Server finds in tftpd.log where that client has downloaded its wdsnbp file from and relies with the bcd file in that same directory.
S->C BINL reply /boot/pxeboot.com and
/boot/myserver/bcd
C->S TFTP request /boot/pxeboot.com
S->C TFTP reply /boot/pxeboot.com
C->S TFTP request /boot/mysystem/bcd
S->C TFTP reply /boot/mysystem/bcd
Client reads BCD file and finds out where to download the boot.sdi and winpe.wim from
C->S TFTP request /boot/boot.sdi
S->C TFTP reply /boot/boot.sdi
C->S TFTP request /boot/winpe.wim
S->C TFTP reply /boot/winpe.wim
Then the client boots into Windows PE. When that is done it takes these seps we have prepared:
Log filesObvious locations to look when troubleshooting is in the logs, check out the following logfiles:
More...I'll add more info when I find out.Go back to the start |