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
Next revision Both sides next revision
winpe [2009/10/01 04:25]
tal.aloni Note regarding running the WinPE creation script in a batch file
winpe [2010/04/20 13:58]
jrc3
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 61: 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.  ​
  
-    filename "​\\Boot\\pxeboot.n12";+**For ISC DHCPD**, you can do this by adding the following to ///​etc/​dhcpd.conf//​.
  
-to ///​etc/​dhcpd.conf//​.+    filename "​\\Boot\\pxeboot.n12";
  
 {{ :​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.+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 
 +    067                 ​Bootfile Name         ​boot\pxeboot.n12
  
 ===== Booting WinPE ===== ===== Booting WinPE =====
Line 80: Line 84:
  
 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)