I just did this (2011-04-01), and this question consistently ranked high in my googling, so I'll throw down a way-after-the-fact answer with the notes about what I learned. Hopefully this will fill in some blanks.
Source OS was Win7 x64.
Source machine:
This machine must have a static IPv4 address. This example will use 192.168.0.1
.
This machine must have a Windows installation in a shared folder somewhere. This example will use .\win7
This example will log in to the source machine with user TEST
and password test
.
Use tftpboot to fire up a DHCP server (gives an IP to a computer when requested).
This will also start a TFTP server for all of the file transfers.
There should be a folder called boot\
in the tftpboot directory which contains an installation of Windows PE.
Start tftpd64.exe (or tftpd32.exe), open the settings, use default settings, and change:
- IP pool starting addresss: Whatever, the pool of IPs to draw from
- Size of pool: Must be > 2
- Boot File:
boot\pxeboot.com
(will dump into Windows PE environment)
- Mask: 255.255.255.0 works fine.
- Uncheck "Ping address before assignation"
- Check "Bind DHCP to this address"
Restart the program to ensure changes are in effect.
Receiver machine:
Run a network boot from the receiver machine. (The DHCP server will assign an IP).
The boot file will be transferred and run. Press F12 to tell Windows PE to do something.
Wait a while (30-60 seconds). A command prompt will appear and load. Wait until a cursor is available.
A drive must be assigned to the root folder on the Source machine. To do this:
X:\Windows\system32>net use z: \\192.168.0.1\win7
A username of a user on the source machine, and password, must be entered.
Enter the user name for '192.168.0.1': 192.168.0.1\TEST
Enter the password for 192.169.0.1: test
The command completed successfully.
Navigate over to the new directory (z:\
) and fire away. Commands will have a long delay but should work eventually.
Links:
http://tftpd32.jounin.net/tftpd32_download.html (DHCP server x86 or x64, no boot\
dir)
WinPE link removed <-- You'll have to get a legal copy of WinPE. Search on Microsoft's website for the Windows AIK (Automated Installation Kit). It will have WinPE in it, and you can use that as the boot image (winpe.wim).
http://www.geeksonhigh.com/hardware/cannot-boot-from-windows-7-cd-try-pxe
http://certcollection.org/forum/topic/28167-installing-windows-7-over-the-network-using-pxe-booting-and-tftp/
Troubleshooting:
If you run into an error "autorun.dll" could not be loaded or is corrupt setup can not continue error code (0xC1)
. This means your version of WinPE is mismatched with your Windows ISO. Type ver
at the WinPE prompt. You'll get something like 6.*.****
.
Here's a rough table of ver
to WinPE version to Windows ISO:
| ver | Win PE Version | Matching Windows ISO | Background Colors |
------------------------------------------------------------------------
| 6.0.6*** | 2.* | Windows Vista | Blue and Green |
| 6.1.7600 | 3.0 | Windows 7 | Gray |
| 6.1.7601 | 3.1 | Windows 7 SP1 | ??? |
| 6.2.9200 | 4.0 | Windows 8 | ??? |
| 6.3.9600 | 5.0 | Windows 8.1 | ??? |
Windows AIK links:
1@various people asking about wifi: PXE booting does not work over WiFi for many reasons (security, configuration required, ...). You'll need an ethernet cable. – Mark K Cowan – 2015-02-09T13:36:03.740
can we did the same steps for installing Windows 8 through out network, just like you did? @Ben – gumuruh – 2016-08-09T22:53:37.007
@gumuruh - don't know, sorry, haven't tried this recently! Interested if you have any success with it though - good luck :) – Ben – 2016-08-09T22:57:46.667
despite this answer is old, I need to know how to install windows from PXE linux server in UEFI mode. I have prepared winPE iso image and able to perform the same in Legacy mode using pxelinux.cfg/default file. Follow this link. Windows 7 Installation in Legacy I need the same cfg entries for grub menu. so that I can use windows iso for installation. I tried trial and error method but failed! :(
– Ac3_DeXt3R – 2018-08-20T12:36:26.943Very close to the way i did it. Thanks for providing full guide. You earn my vote and tick :) – George – 2011-04-01T10:30:18.440
I get error 53 on "net use" command and 1231 when I ping the server any idea what might be causing this? – Nikhil Bhandari – 2011-09-17T01:36:59.227
3I don't get it. Is
pxeboot.com
part of Windows installation disk or tftp ? Because I don't have it anywhere. Therefore client machine fails to boot. – expert – 2012-01-30T07:53:53.723How do you connect the machines physically? I already have a router that assigns DHCP. Do I connect them to the router or what? – moleculezz – 2012-07-13T06:19:10.293
1Link to megaupload = fail. Also that included a WinPE image, and that is not freeware to be passing around. – Tim – 2012-07-25T15:59:03.190
If you already have a DHCP in place you need a proxyDHCP startegy read here http://www.vercot.com/~serva/howto/WindowsPXE1.html
– Pat – 2012-08-19T08:35:00.600@Tim - noted and removed. – Ben – 2012-12-09T03:45:14.880
so? do the machines have to be physically connected? I have a wifi provider – Ayyash – 2013-08-04T10:41:07.803