Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revision Both sides next revision | ||
|
appnote:chainload_wds [2014/12/22 15:06] svenx Article created. |
appnote:chainload_wds [2014/12/23 09:36] svenx Minor changes and formatting. |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| ''HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/WDSServer/Providers/WDSTFTP/ReadFilter'' | ''HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/WDSServer/Providers/WDSTFTP/ReadFilter'' | ||
| that controls which TFTP paths are mapped to the directory containing | that controls which TFTP paths are mapped to the directory containing | ||
| - | the various installation files. Depending on the existing | + | the various installation files defined by the ''RootFolder'' registry key in the same location. |
| + | |||
| + | {{ :appnote:regedit-wdstftp.png?400|RegEdit WDSTFTP}} | ||
| + | Depending on the existing | ||
| configuration, it is likely that additional patterns must be added to | configuration, it is likely that additional patterns must be added to | ||
| make iPXE and the WDS boot programs work correctly. | make iPXE and the WDS boot programs work correctly. | ||
| Line 41: | Line 44: | ||
| Loading the initial WDS network boot program ''wdsnbp.com'' can be | Loading the initial WDS network boot program ''wdsnbp.com'' can be | ||
| done either directly from the iPXE shell or via a menu entry. The only | done either directly from the iPXE shell or via a menu entry. The only | ||
| - | thing that needs to be modified is the DHCP ''next-server'' setting, | + | thing that needs to be modified is the DHCP ''next-server'' parameter, |
| which will let ''wdsnbp.com'' know which server to communicate with. | which will let ''wdsnbp.com'' know which server to communicate with. | ||
| Due to how iPXE handles [[:settings#scopes|configuration setting | Due to how iPXE handles [[:settings#scopes|configuration setting | ||
| Line 90: | Line 93: | ||
| * filename: ''boot\x64\pxeboot.n12''. | * filename: ''boot\x64\pxeboot.n12''. | ||
| * option 250: ''0b0101100400000001ff'' | * option 250: ''0b0101100400000001ff'' | ||
| - | * option 252: \Tmp\x86x64{GUID}.bcd | + | * option 252: ''\Tmp\x86x64{GUID}.bcd'' |
| - Client: ''wdsnbp.com'' requests TFTP ''/boot\x64\pxeboot.n12''. | - Client: ''wdsnbp.com'' requests TFTP ''/boot\x64\pxeboot.n12''. | ||
| - Client: ''pxeboot'' requests TFTP ''/boot\x64\bootmgr.exe''. | - Client: ''pxeboot'' requests TFTP ''/boot\x64\bootmgr.exe''. | ||
| Line 97: | Line 100: | ||
| ===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
| + | {{ :appnote:wireshark-wds.png?400|WDS in Wireshark}} | ||
| Due to the poor error reporting in the WDS boot programs, the go-to | Due to the poor error reporting in the WDS boot programs, the go-to | ||
| troubleshooting tool should be a network packet analyzer like | troubleshooting tool should be a network packet analyzer like | ||
| Line 114: | Line 118: | ||
| * TFTP error codes from the WDS server. | * TFTP error codes from the WDS server. | ||
| * DHCP options in the client requests and server responses. | * DHCP options in the client requests and server responses. | ||
| + | * The WDS event log in Windows. | ||
| ==== TFTP download errors ==== | ==== TFTP download errors ==== | ||
| Line 129: | Line 134: | ||
| If either ''wdsnbp.com'' or ''pxeboot.n12'' gets stuck in a request | If either ''wdsnbp.com'' or ''pxeboot.n12'' gets stuck in a request | ||
| loop, it is likely that the initial TFTP download worked, but | loop, it is likely that the initial TFTP download worked, but | ||
| - | subsequent ones are failing. This happens because iPXE uses forward | + | subsequent ones are failing. This can happen because iPXE uses forward |
| slashes in the TFTP file path, while the WDS boot programs are prone | slashes in the TFTP file path, while the WDS boot programs are prone | ||
| to using a mix of forward and backward slashes. | to using a mix of forward and backward slashes. | ||
| Line 152: | Line 157: | ||
| that can take ages to download the files. | that can take ages to download the files. | ||
| - | The iPXE author has developed [[:wimboot]], a boot loader that takes | + | A good alternative to the PXE mechanism of WDS is [[:wimboot]], a boot loader that takes |
| over the roles of ''wdsnbp.com'' and ''pxeboot.n12''. It lets you | over the roles of ''wdsnbp.com'' and ''pxeboot.n12''. It lets you | ||
| fetch all the relevant files over HTTP and hand over execution to | fetch all the relevant files over HTTP and hand over execution to | ||
| Line 164: | Line 169: | ||
| * How the Boot Configuration Data Store Works: http://technet.microsoft.com/en-us/library/cc770770 | * How the Boot Configuration Data Store Works: http://technet.microsoft.com/en-us/library/cc770770 | ||
| * iPXE [[:howto:winpe|WinPE howto]] | * iPXE [[:howto:winpe|WinPE howto]] | ||
| - | |||
