Remote Installation of Windows XP through PXE

Remote Installation of Windows XP through PXE
Abstract:
PXE and preboot execution environment (Remote Boot Technology) can be implemented in the following ways:
1. Use the network installation service provided by Windows server to deploy XP or 2003 network installation. This method must be performed in domain mode.
2. Install the client system by installing the software for the network service.
This article introduces the second method. This method is convenient and requires no additional servers.
Online has a very detailed installation steps and implementation principle, can refer to Netease blog author liaowake article "Windows environment PXE install Win2k, WINXP, win2k3", address http://liaowake.blog.163.com/blog/static/250751020091161920817/

System deployment structure:
Lan
==========================================
=-> =
= PXE Server Client PC =
= <-=
==========================================

PXE Server: a PC installed with Windows XP installation files in the LAN, used to provide PXE services
DNS and DHCP services are installed on the PXE Server.
Client PC: The PC where the operating system is to be installed

Requirements:
Hardware
1. The client PC motherboard supports PXE Remote Boot
2. PXE Server can access its resources through LAN
Software:
1. the DHCP server is responsible for allocating IP addresses.
2. the TFTP server is responsible for transferring files to the client.
3. binl is the key to network installation in Working Group mode. This service is used to load the NIC Driver of the client from the network, mainly through ncq, NCR, rqu, and RSU packets.
4. Win2k, WINXP, win2k3, or image files

Installation steps:
On the PXE Server, execute the following Configuration:
1. Download tftpd32 software, Home Page http://tftpd32.jounin.net/index.html, (I use version 3.34), this software provides DNS and FTP Server Functions
2. Open the tftpd32.exe program and switch to the DHCP Server Tab:
The server interfaces address is the IP address of the PXE Server. Note that the following IP settings must be in the same CIDR block as the IP address and cannot conflict with the IP address of an existing device on the network.
IP pool starting address 192.168.0.200 IP Address
Size of pool 5 (this can be used as needed)
Boot file pxelinux.0
Wins/DNS server local IP address, others can also
The default router local IP address. Others can also be used. It must be the same as the previous line.
Mask limit 255.0
(Leave other blank)
3. Create a shared folder TFTP
Create a folder WINXP in the TFTP directory
Copy the i386 folder from the Windows XP installation disk to the WINXP directory
4. Boot local boot from the chain. c menu
Pxelinux.0 boot Client
Vesamenu. c32 start the menu Program
5. Move the modified "setupldr.exe" to the TFTP directory and rename it "ntldr"
6. copy the NIC Driver of the client PC where the system is installed to the PXE Server TFTP \ WINXP \ i386, because after boot, the client PC needs to use the NIC to access the shared directory of the PXE Server, instead of getting files directly using the TFTP protocol during boot
Generally, the NIC driver is in the i386 \ driver. Cab package of the Windows installation disk. extract it.
7. Start binlsrv for the client to find the NIC Driver

Troubleshooting:
1. If the xxxfile is incorrectly scanned or cannot be found during installation, you can view the log on the log viewer Tab Of The tftpd32.exe program, find the missing file, and copy it to the corresponding directory.
2. the PXE Server Firewall should be closed or open to prevent client requests from being blocked.
3. If you use PXE to install the system on a VM,
1) enable the network startup of the simulator. For example, virtual box is not enabled by default.
2) Note that Nic settings in Virtual Machine options include not connected, local only, local LAN Nic, shared networking (NAT), unlimited wireless Nic, and bridge adapter, you need to set "as local LAN nic" or "bridge"
3) The Boot mechanism of each virtual machine is different, and some will not respond at startup (such as Microsoft Virtual PC), but there is no error prompt, and sometimes it is not a PXE Server configuration error, in this way, only other methods can be considered for incorrect search.
4. Due to the WINNT. Sif bug, if the tftpd32 log prompts that the file pxelinux.0xxxxx starting with pxelinux.0 cannot be read, you need to rename these XXXX files with the prefix pxelinux.0
5. Windows Security Policy Modification
6. If the following error occurs:
Trying to load: pxelinux. cfg/01-00-0c-29-ca-7a-ce
Trying to load: pxelinux. cfg/0a000014
Etc ..
Trying to load: pxelinux. cfg/Default
Unable to locate configuration file
It is because the DHCP server configuration of TFTP is incorrect, or the firewall cannot connect to the TFTP server.
7. Error: Invalid or invalid upt kernel Image
This error occurs when startrom. n12 is renamed to winxp.0. The startrom. n12 file must be renamed and must be changed to the file name ending with the extension 0 (Linux special file ID). Otherwise, the above error occurs.
8. Incorrect file name garbled during file retrieval: INF file j8j9j: J; j <j = j> J? Is upt or missing, status 21. Setup cannot continue. Press any key to exit.
It may be a problem with the syslunux version. The author tests that 3.73 in liaowake can be started normally and the above error will occur when the latest 3.82 version is used.
9. The NIC Driver required by the virtual box virtual machine is extracted from the WINXP installation disk i386 \ driver. Cab and copied to the i386 directory.