Summary

Lists of the current known issues with implementing, configuring, using and upgrading PXE Everywhere.

If you need further help, please refer to the Troubleshooting page for how to contact 1E Support and the technical support process.

On this page:

Issues using PXE Everywhere

IssueDescriptionWorkaround
UEFI PXE Boot Fails with error in the boot loader when a machine has more than one NIC

When machine has more than one Network Interface Card (NIC) and on performing PXE Boot from the secondary NIC card the PXE Boot will fail.

This issue occurs only when you try boot from a NIC which is NOT the first NIC in the boot order.

If you boot from the first NIC the boot will complete without problem.
When Tftp session begins errors are noticed for file for which system cannot find the path specified

During PXE Boot UEFI firmwares requests few files however when not found boot still succeed. 

These files are optional for the boot and not essential.
When a 1E PXE Everywhere boot image is created with blocksize values higher than 1471 bytes, TFTP transfers fail during PXE Boot

On Cisco and TPLink switches with DHCP Snooping enabled and block size value is higher than 1471 bytes PXE boot may fail. This is due a bug in the switch hardware itself. 

This issue does not occur when DHCP Snooping is off.

For details of how to change the block size used by TFTP, please refer to Preparing and deploying 1E PXE Everywhere boot images: TFTP Block Size.
CreateBCD.exe does not remove the .prompt.bcd files when it is re-runThe boot.image_ID.prompt.bcd and boot.image_ID.prompt.bcd.LOG files are not purged from the boot images under TFTPROOT when upgraded from previous versions.Manually delete the log files.
Secure Boot won’t work on Hyper-V (Gen-2) virtual machines.PXE Booting Hyper-V (Gen-2) virtual machines with the Secure Boot option is not supported in PXE Everywhere.None.
Command prompt crashes when arguments are passed to UpdateBootImage.exeIf you run a command prompt and pass arguments to UpdateBootImage.exe, it crashes the session. Run the command prompt with elevated rights.
Create media fails when using UpdateBootImageGUI tool.UpdateBootImageGUI does not throw an error when a site server is specified in the SMSProvider field which does not have a local SMS Provider. The command is generated successfully with the entered value of the site server name, however the create media fails.
Temporary image file is left in the %temp% folder after UpdateBootImage.exe has executed successfullyDuring UpdateBootImage a temporary .WIM file is updated in %temp% folder. This image file is not deleted after a successful execution of UpdateBootImage.exe and can be removed manually.Manually delete the image file.

Issues installing PXE Everywhere Central

IssueDescriptionWorkaround
PXE Everywhere Central unattended installation succeeds even when prerequisites are not met.PXE Central unattended installation creates an entry in Windows Program and Feature however, program files are not installed and the Web service is not created.Ensure prerequisites are met when installing unattended.
While upgrading PXE Central to 3.2 or above from an older version where TLS 1.0 has been disabled, you get an exception - "Could not connect to Database"

While upgrading PXE Central to 3.2 or above from an older version TLS v1.0 has been disabled, you get an exception - "Could not connect to Database". You can ignore the error and click on ‘Next’ button, then installation would go through fine.

That error occurs as a part of uninstallation of older version, when it tries to remove the stored procedures from DB. Since we don’t have TLS 1.2 support in old version, it fails to connect to DB.

Ignore the error and click on ‘Next’ button, then installation would go through fine.
After upgrading PXE Everywhere Central there are log files left in c:\programdata\1e\pxelite

From PXE Everywhere Central v4.0 onwards, the new default logpath is c:\programdata\1e\pxeeverywhere.  The legacy logapth is c:\programdata\1e\pxelite.

During upgrade the legacy log files are deliberately not deleted. This is partly to avoid contention with other legacy PXE Everywhere products installed on the computer, but also to avoid mixing old and new logs.

Manually delete the log files after all PXE Everywhere products have been upgraded.

Issues installing PXE Everywhere Responder

IssueDescriptionWorkaround

PXE Everywhere is not responding as expected. Log file shows messages similar to:

Error: failure to bind to 192.168.18228:69. 
The specified address is already in use
TFTP: retry in 1000ms
Error: failure to bind to 192.168.18228:4011. 
The specified address is already in use
DHCP: retry in 1000ms

PXE Everywhere Agent and PXE Everywhere Responder cannot co-exist on the same computer and are not supported together. Whilst it is possible to install them together, they will not work and will have issues such as failure to bind to ports.

Either uninstall PXE Everywhere Responder, or disable PXE Everywhere module in 1E Client. Then restart the computer, or restart the relevant service (PXE Everywhere or 1E Client). 
Responder does not respond to Agents on port 67. 

PXEEverywhereResponder.msi will upgrade legacy (3.2 or before) Responder and Agent if they exist, keeping the old registry settings. Upgrading a Responder will cause it to continue functioning as a Responder on port 67. Upgrading an Agent to a Responder will also allow it to function as a Responder, but if the Agent was previously configured to support DHCP Snooping then it will not be using port 67 and the Responder must be re-configured to use port 67. 

Post-install fix is to reconfigure DhcpPort=67 on the Responder.

Include DHCPPORT=67 as an installer property if you are upgrading legacy Agents to act as Responders. 

After upgrading PXE Everywhere Responder there are log files left in c:\programdata\1e\pxelite

From PXE Everywhere Responder v4.0 onwards, the new default logpath is c:\programdata\1e\pxeeverywhere. The legacy logpath is c:\programdata\1e\pxelite.

During upgrade the legacy log files are deliberately not deleted. This is partly to avoid contention with other legacy PXE Everywhere products installed on the computer, but also to avoid mixing old and new logs.

Manually delete the log files after all PXE Everywhere products have been upgraded.

Issues installing PXE Everywhere Agent in 1E Client

IssueDescriptionWorkaround

PXE Everywhere is not responding as expected. Log file shows messages similar to:

Error: failure to bind to 192.168.18228:69. 
The specified address is already in use
TFTP: retry in 1000ms
Error: failure to bind to 192.168.18228:4011. 
The specified address is already in use
DHCP: retry in 1000ms
PXE Everywhere Agent and PXE Everywhere Responder cannot co-exist on the same computer and are not supported together. Whilst it is possible to install them together, they will not work and will have issues such as failure to bind to ports.Either uninstall PXE Everywhere Responder, or disable PXE Everywhere module in 1E Client. Then restart the computer, or restart the relevant service (PXE Everywhere or 1E Client). 
PXE Everywhere Agent fails to connect to PXE Everywhere Central.An incorrect URL has been specified during installation of PXE Everywhere Agent. The installer wizard does not validate the PXE Lite Central URL is provided during the PXE Lite Local GUI installation.Ensure you specify the correct URL when installing PXE Everywhere Agent.
PXE Everywhere does not support RISC based architecture.PXE Everywhere does not support RISC based architecture and therefore not able to PXE boot clients using RISC. For instance, architecture being used by Microsoft Surface Pro 10 LTE Models is ARM 64-BIT UEFI (11)  which is a RISC architecture and not recognized by PXE Everywhere.None.
PXE Everywhere Agent installation fails when an unprivileged user installs it after providing administrator credentials (UAC prompted) for installation.PXE Everywhere Agent installation fails with error when an unprivileged user initiates PXE Everywhere Agent installation even after validating credentials after UAC prompt. When installing the agent interactively, run the installer from a command prompt with elevated permissions.