A non-Acronis application blocks Port 69
PXE
Client machines cannot boot Acronis PXE Server if it is running on the same machine with Broadcom ASF IP Monitor (AsfIpMon.exe)
Change hard drive mode to SATA to resolve the issue
One can put the bootable data of Acronis Rescue Media only on a RIS server or a WDS server running in Legacy mode
How to investigate issues with Acronis PXE Server
This has been fixed
Configuring the product to let users deploy and redeploy their machines with one click on the boot menu
Make sure Acronis PXE Server is installed. Then upload the components to it via Acronis Management Console
Acronis Standalone Utility cannot be uploaded to PXE
How to make Acronis PXE Server boot with PXELinux loader
Acronis PXE Server support for UEFI machines is planned for future
This article applies to:
- Acronis Backup & Recovery 11
- Acronis Backup & Recovery 10
- Acronis Snap Deploy 3
Symptoms
- You install Acronis PXE Server and configure machines to boot from it;
- Machines fail to boot from Acronis PXE Server with the following error:
Acronis Loader fatal error: At least 512 Kb of conventional memory required to start Acronis Loader
Cause
Incorrect work of Intel RAID in BIOS.
Use the Cleanup Utility to remove the PXE Server
32-bit UEFI devices support limitation
To let Acronis products operate properly in the network, you need to open specific ports in Firewall settings.
DHCP server and PXE server are on different machines