Why won't my client computers PXE boot? What do I need to do to get it to work?
There are several configuration items that need to be done before the PXE server will respond to clients and allow them to PXE boot.
1. Be sure the PXE services are running.
In Computer Management, PXE services are now known as Symantec Netboot Services. Specifically, these services are:
By default, these services are set to Manual run. This is to allow a degree of control over PXE servers and avoid conflicts, and these services need to be started for the PXE boot process to function in the environment. They should be started in the following order:
After starting the services, it will be several minutes before they will be active for PXE use. For more information on what each of these do, please see KB 51889.
**NOTE: On some installs, an additional service - '_Symantec_netBoot_Helper' - may be installed. This service is a relic from before HF1 for DS 7.1 and should not be present (see KB 51895). If this service is present, please follow the steps documented in KB 51895.
**NOTE: These services will be set to Manual by default on installation. To set these to automatically start/run certain dependencies should be set up to preserve the above-mentioned start order. This can be accomplished by following KB 52235.
2. Be sure that the automation environments are configured.
An "Automation Environment" is a separate preboot environment that the computer loads into a RAM disk in order to run processes (image capture, etc.) against the production hard drive without files being open and running, thus allowing for an accurate capture of an image. These automation environments need to be built before a machine can be booted via PXE. By default, only templates for these environments are built (otherwise known as Automation Folders).
To configure the automation environment, do the following:
3. Be sure PXE policies are on.
**NOTE: There should be at least one (1) computer listed at the bottom of this page. If not, then something above has not been done correctly, such as starting the PXE services. No computers can be manually added here; they will show up automatically when functioning correctly. If all the above steps have been completed and the services are running, it may take a little time for it to come up initially; sending a basic inventory from the server as well as running the 'NS.Delta Resource Membership Update' on the NS will accelerate this. If this list still remains blank, see KB 52886.
4. Be sure the Deployment Site Server Components Policies are on.
**NOTE: These components are automatically installed on the Notification Server, so these apply primarily to Site Servers. Further information can be found in KB 51896.