Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
winpe [2009/08/17 07:09]
tal.aloni modified the script to allow executing it in a bat file
winpe [2010/06/05 07:34] (current)
sha0 Add info about next-server DHCP option
Line 12: Line 12:
  
 Install the AIK onto a working Windows system (the "​technician computer"​). ​ The installation requires around 1GB of disk space. Install the AIK onto a working Windows system (the "​technician computer"​). ​ The installation requires around 1GB of disk space.
- 
 ===== Setting up WinPE ===== ===== Setting up WinPE =====
  
-Open the Windows PE Tools Command Prompt (//Start// -> //All Programs// -> //Microsoft Windows AIK// -> //Windows PE Tools Command Prompt//) and enter the following commands (some of which are case-sensitive):​+Open the Windows PE Tools Command Prompt (//Start// -> //All Programs// -> //Microsoft Windows AIK// -> //Windows PE Tools Command Prompt//) and enter the following commands (some of which are case-sensitive). Note that if you intending to install a 64 bit version of Windows, the second command below should specify "​amd64"​ instead of "​x86"​ (amd64 is a generic reference to 64 bit support which includes support for both AMD and Intel based 64bit hardware):
  
     mkdir C:\Temp     mkdir C:\Temp
Line 33: Line 32:
     %BCDEDIT% -set {ramdiskoptions} ramdisksdidevice boot     %BCDEDIT% -set {ramdiskoptions} ramdisksdidevice boot
     %BCDEDIT% -set {ramdiskoptions} ramdisksdipath \Boot\boot.sdi     %BCDEDIT% -set {ramdiskoptions} ramdisksdipath \Boot\boot.sdi
-    for /f "​tokens=3" ​%%a in ('​%BCDEDIT% -create -d "​Windows PE" -application osloader'​) do set GUID=%%a+    for /f "​tokens=3"​ %a in ('​%BCDEDIT% -create -d "​Windows PE" -application osloader'​) do set GUID=%a
     %BCDEDIT% -set %GUID% systemroot \Windows     %BCDEDIT% -set %GUID% systemroot \Windows
     %BCDEDIT% -set %GUID% detecthal Yes     %BCDEDIT% -set %GUID% detecthal Yes
Line 43: Line 42:
     %BCDEDIT% -set {bootmgr} displayorder %GUID%     %BCDEDIT% -set {bootmgr} displayorder %GUID%
     del /Q bcdedit.exe     del /Q bcdedit.exe
 +
 +Note: When using inside a batch file, replace %a with %%a  (twice) in the "​for"​ command parameters.
  
 ===== Transferring WinPE to a TFTP server ===== ===== Transferring WinPE to a TFTP server =====
Line 59: Line 60:
 ===== Configuring DHCP and TFTP ===== ===== Configuring DHCP and TFTP =====
  
-Configure your DHCP server to hand out //"​\Boot\pxeboot.n12"//​ as the boot filename.  ​For ISC DHCPD, you can do this by adding+Configure your DHCP server to hand out //"​\Boot\pxeboot.n12"//​ as the boot filename.  ​
  
 +**For ISC DHCPD**, you can do this by adding the following to ///​etc/​dhcpd.conf//​.
 +
 +    next-server XXX.XXX.XXX.XXX;​
     filename "​\\Boot\\pxeboot.n12";​     filename "​\\Boot\\pxeboot.n12";​
  
-to ///​etc/​dhcpd.conf//. +where the **next-server** details either the IP address or DNS hostname of your TFTP server.
 {{ :​warning.png}} {{ :​warning.png}}
  
-Note that you **must** use a backslash (\) as the path separator, rather than the more usual forward slash (/).  If you use a forward slash, //​pxeboot.n12//​ will be unable to locate //​bootmgr.exe//​ and the boot will fail.  Your TFTP server must be configured to support the use of backslashes as path separators; see [[:​tftp_backslash|Supporting broken TFTP clients]] for instructions on configuring your TFTP server to do this.+<sub>Note that you **must** use a backslash (\) as the path separator, rather than the more usual forward slash (/).  If you use a forward slash, //​pxeboot.n12//​ will be unable to locate //​bootmgr.exe//​ and the boot will fail.  Your TFTP server must be configured to support the use of backslashes as path separators; see [[:​tftp_backslash|Supporting broken TFTP clients]] for instructions on configuring your TFTP server to do this. 
 + 
 +Note also that each backslash is doubled within ///​etc/​dhcpd.conf//;​ this is because ISC DHCPD treats a backslash as an escape character.</​sub>​ 
 + 
 +**For Microsoft DHCP Server**, set the following options 
 + 
 +    Option Number ​      ​Option Name           ​Value 
 +    066                 Boot Server ​          ​XXX.XXX.XXX.XXX 
 +    067                 ​Bootfile Name         ​boot\pxeboot.n12
  
-Note also that each backslash is doubled within ///​etc/​dhcpd.conf//;​ this is because ISC DHCPD treats a backslash as an escape character.+where option 66 refers to your TFTP server'​s IP address or DNS hostname.
  
 ===== Booting WinPE ===== ===== Booting WinPE =====
Line 78: Line 89:
  
 Congratulations on a successful boot of Windows PE! Congratulations on a successful boot of Windows PE!
- 

QR Code
QR Code winpe (generated for current page)