Q: How do I configure PXE service in server-side? How to use PXE function to boot in client-side?
- A: Run the program to configure PXE service. You can choose "Boot from AOMEI Windows PE system", "Boot from AOMEI Linux system", or "Boot from custom image file". Then click "Start Service" button. If the current system doesn’t have the required environment to create a bootable image file, the program will prompt you to install Windows AIK or ADK.
- After you have finished configuring server-side, ensure the client-side and server-side both exist in the same LAN and network segment.
- Check whether DHCP server exists in LAN or not. There must be a DHCP server in LAN. If you don't have a DHCP server, you can use some software such as TFTPD32 to build it.
- If the client computer’s motherboard is set to UEFI boot mode, change to legacy BIOS boot mode and enable the PXE boot option in BIOS.
- Restart the client computer to start up the system through the network booting.
- Optional: Temporarily close all firewalls, including Windows firewall and third-party program firewall before running the feature.
- Optional: You may be prompted that some ports are in use by other programs, when starting the PXE service. To check enter the CMD command prompt, and separately type:
netstat -aon|findstr "67", netstat -aon|findstr "69", netstat -aon|findstr "4011" to check if the 67, 69, 4011 ports of server-side are in use by another program.
If so, please type tasklist|findstr "PID" to find out which processes are using these ports, and then manually end the processes using theses ports.
Q: In a few cases when using PXE, why does it fail to create a Windows PE bootable image file?
A: Causes may be:
- The environment required to create a Windows PE bootable image file is not present in the current system. In such case, the program will prompt you to install Windows AIK or ADK, and then restart program to try again.
- The program is installed in the directory which includes non-English characters. In such case, the program will prompt you that it failed to create Windows PE bootable image file. Please use the "Create Bootable Media" function in AOMEI Backupper to create Windows PE bootable ISO image file, and then store it to the program installation directory. Alternatively reinstall the program into English directory, or install the language pack in current system related to the non-English characters included in the installation directory.
- A bug has occurred. Please use "Create Bootable Media" function in AOMEI Backupper to create a Windows PE bootable ISO image file, and then store it to the program installation directory. Alternatively use other software to create bootable ISO image file, such as AOMEI PE Builder, or select a bootable ISO image file you have already created.
- If the "Create Bootable Media" function in server-side program is running, creating Windows PE bootable image file in the PXE function will fail. Please wait until the progress of "Create Bootable Media" in server-side program is completed, and then continue with the operation in the PXE function.
Q: In a few cases, why does the client-side fail to boot from the network even after they have finished configuring PXE service in the server-side?
- A: If the server-side and client-side do not exist in the same network segment, the server-side neither receives the request from client-side nor sends data to the client-side. The inability to communicate results in the client-side failing to use the PXE function to boot from server-side. In such a case, configure the server-side and client-side with the same network segment.
- If the LAN on which the server-side and client-side exist does not have DHCP server, the client-side cannot obtain the IP address when booting from the network. To solve this problem, add a router with DHCP service to the LAN, or use third-party software such as TFTPD32 to configure DHCP service on another computer.
- The client-side using PXE function to boot from the network may be affected if the firewall of server-side is enabled. In such case, close the firewall of server-side.
- Boot failure will occur if the client-side uses UEFI boot mode to start up from the network. Currently the PXE function in the program does not support UEFI boot mode. To correct this, enter into motherboard settings to change the UEFI boot mode into legacy BIOS boot mode.
- It may be that the logged-in user in server-side is not an Administrator account. In such a case, the configured PXE service fails to start automatically after logging in. Please run AOMEI PXE Tool with administrator privileges, and then click "Start Service" button. Restart from the client-side to try again.
- The client-side using PXE function to boot from the network must connect to the server-side through a wired network. The PXE function does not support communication through the wireless network card.
Q: In a few cases, why does system startup fail when using PXE function to boot from the network?
- A: The selected bootable image file might have a problem. Please re-create a bootable image file, or use "Create Bootable Media" function in AOMEI Backupper, or use AOMEI PE Builder.
- If the selected bootable image file is too large, or the computer’s memory too small, boot failure may occur because of insufficient memory. Please select a smaller bootable image file.