PXE Representative has an outdated Ivanti EPM Agent.

BIOS has bad network boot agent code

BIOS with Intel Boot Agent(IBA) versions 1.3.36 through 1.3.50 do not allocate enough memory space for the PXE menu to be loaded on the client computer.

This is the most common cause of this PXE-E74 issue.

Computers that customers reported experiencing this issue:

Symptoms: Only specific models of computer are unable to PXE boot.

Resolution:  Upgrade or downgrade BIOS.  Contact device vendor for further information.

BIOS with IBA prior to 1.3.36 or a BIOS with IBA after 1.3.51 should address this issue.

Some vendors have not provided an updated BIOS to fix the issue, while other vendors have. 
If a vendor has not provided a BIOS that fixes the issue if possible the BIOS should be downgraded. 
If an update is provided that may fix the issue, a BIOS upgrade may be necessary.

PXE Representative installation is incomplete or corrupted

The PXE representative installation may have been incomplete causing missing directories or folders, or those files may have become corrupt.  The following graphic illustrates the folder and files that should exist under \Program Files (x86)\LANDESK\PXE:

(Run "tree /f" from this folder to compare results)

     
Click graphic to view full size.

Symptoms:  All computers on the same subnet will not PXE boot.  Or if using more than one PXE rep on a subnet, all computers going to specific (bad) PE Representative will fail.

Resolution: Reinstall the PXE Representative.

1. Verify which PXE representative clients are attempting to boot from by looking for the PXE representative IP Address on the BIOS boot screen on the client.
2. Delete existing PXE Representative Deployment task.
3. Schedule new PXE Representative Deployment task.

• Instructions for LDMS 9.6 and later
• Instructions for LDMS 9.5 and earlier
  

Ports blocked to the PXE  Representative

During the network boot process, all file transfer requests are initiated to port 69 which services the TFTP (Trivial File Transfer Protocol).

If this port is blocked, requests to the TFTP Service on the PXE representative will fail.

Symptoms: All computers on the same subnet will not PXE boot. Or if using more than one PXE rep on a subnet, all computers going to specific (bad) PE Representative will fail.

Resolution: Check network environment to ensure that proper ports are available.

• UDP Port 67 (DHCP)
  Port used by the DHCP Server to receive requests.
• UDP Port 68 (PXE Client)
  Port used by the client for DHCPDiscover to DHCP Server
• UDP Port 69 (TFTP)
  Port that PXE Rep receives TFTP requests from.
• UDP Port 4011 (PXE / ProxyDHCP)
  Like port 67 on the DHCP server, but for PXE rep to respond to DHCPDiscover with further DHCP  information for the network booting process.

Incorrect DHCP options are  configured

Symptoms: Typically in this scenario, all computers will not be able to PXE boot that get their IP address from that DHCP server.

Resolution: Remove options 43 and 60 from the DHCP Server.

The DHCP server is typically configured in one of the following ways.

• Option 60 not set.  Option 43 not set.
• Option 60 set to 'PXEClient'.  Option 43 not set.
• Option 60 set to 'PXEClient'.  Option 43 set.

When neither option 60 nor option 43 is set, PXE clients do not have information where the PXE server is, and will wait until a PXE server contacts them.  The PXE Representative listens to DHCP discovery packets sent by PXE clients and offers a DHCPOFFER response in tandem with the DHCP Server.

When option 60 is set to 'PXEClient', the DHCP server contains information about where the PXE representative is.  If option 43 is not set, the PXE server and the DHCP server are at the same IP Address.
If option 43 is set PXE clients must decode option 43 to know how to reach the PXE server.

In most situations, option 43 does not need to be set up, because the PXE server will either listen to DHCP discovery packets (DHCPProxy), or be on the same computer as the DHCP server. However, if the PXE server is on a separate subnet (it cannot listen to DHCP discovery packets), or if there are several PXE servers on the same subnet, option 43 is the only viable solution in order to instruct PXE clients on what to do.

Multiple PXE Representatives on the subnet or other 3rd party PXE solution on subnet

Symptoms: Clients will intermittently fail PXE booting or will always fail to PXE boot.

Resolution: The following query can be created to find the IP address of all PXE Representatives (or the query can be modified to return other criteria if so desired)

How to: Create an Ivanti EPM Query to find all PXE Representatives

• A Wireshark network capture can be performed to ensure all BOOTP (Network boot) traffic is coming from the expected sources.

Incorrect Permissions in IIS for folder

Symptoms: All clients receive the PXE-E74 error.

Resolution: Ensure that the local IUSR account on the Core Server has rights to the  \LANDESK\ManagementSuite\LANDESK\Files directory.  In addition, ensure that Group Policy has not restricted the rights for IUSR as a whole.