DS 8.x : How do I set up PXE services on a Deployment 8.xserver?
search cancel

DS 8.x : How do I set up PXE services on a Deployment 8.xserver?


Article ID: 179647


Updated On:


Deployment Solution


Steps include installing and configuring PXE and Configuring a Preboot Configuration


DS 8.x


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:

  1. Symantec Network Boot Service (PXE)
  2. Symantec Neowrks Boot Service (TFTP)

By default, these services are set to Automatically 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:

  1. PXE Server
  2. TFTP Server

After starting the services, it will be several minutes before they will be active for PXE use.

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:

  1. Open the Preboot Configuration: Settings | Deployment | Manage Preboot Configurations
  2. Configure the Profile Configuration for the Pectagent Communication: PXE Quick Start for Windows using and how to use CEM:  Imaging using Cloud Enabled Management
  3. LInks will be shown on where to download a ADK and to import the ADK ( article:  150348 )
  4. Configure the Preboot Environment Settings for Winpe ( Default setting works in most cases )
  5. There will be two options listed by default: 'LinInstall' and 'PEInstall'.  These are Automation Folders, not PXE bootable environments.  You will need to create a PXE environment to use.  Select 'Add' in the top left to start the creation of an actual Automation Environment.
  6. Fill in the Name field and select the appropriate options.  Note that the name cannot contain special characters.  Note that you can have an environment that will auto-select between x64 and x86, but if you wish to force a particular mode you'll have to remove the architecture you do not want.  Note that you can choose just PXE or just Automation Folders, or both.  If you're unsure, we'd recommend creating both.
  7. After entering the information, click 'OK' then 'Save Changes' on the policy page.
  8. Verify that the configuration has been built and replicated.  This is done on the client for each individual PXE server via policies.  It can be checked / verified by clicking on the Status "button" / link at the upper-right of this policy.  Note that the status will show while it is building, The configuration being build can be seen in the agent under 'NBS Server' tab
    1. If you want to "hurry-up" this process, you can do the following:  a) Run the Delta Update scheduled task.  b) Go to the client on a chosen PXE server (including the NS) and choose the Update button to send a configuration request and get this policy.  c) Launch Task Manager on the PXE server (including the NS) to see and/or watch BootWiz executing.  When it is done, you should see the Status show the policy creation is completed and you should have the appropriate PXE folders in the Agent.

3. Be sure PXE services are on.

  1. Be sure that the 'NBS Global Settings' policy is 'On' : Setting | Deployment | NBS Global Settings' and toggle: Apply NBS settings immediately
  2. For PXE acknowledgment turn long NBS General Settings' policy; Setting | Deployment | NBS General Settings
  3. If you will be imaging unknown computers (i.e. bare-metal), you should select the option to respond to unknown computers.
  4. If you find the process is not performing as you wish, this is also where you can enable logging.  
  5. Select 'Save Changes' at the bottom of the policy page.

**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.  

4. Be sure the Deployment Site Server Components Policies are on.

**NOTE: Apply these plugins onto the Site Server. If imaging is to be done from the NS then the Deployment Task Server Component plugin will only need to be installed on it

  1. On the NS Console, open 'Settings'>>'All Settings'
  2. Expand 'Settings'>>'Agents/Plug-ins'>>'Deployment
  3. Turn on the 'Deployment Package Server Components - Install' Policy
  4. Turn on the 'Deployment Package Server Components- Upgrade' Policy
  5. Expand 'Settings'>>'Agents/Plug-ins'>>'Deployment>>'Windows x64 or x86'
  6. Turn on the 'Deployment Task Server Components (x86/x64) - Install' Policy
  7. Turn on the 'Deployment Task Server Components (x86/x64) - Upgrade' Policy

**NOTE: There will be 2 added plugin in the Symantec Management Agent on the Site Server and only one plugin if install on NS