Note: PXE Lite 1.5 and 1.6, while similar, have different components. This post talks about the 1.6 components.

Broadly speaking, PXE Lite can be separated into 3 groups of components.

Local (or Branch) Components

There are the “local” components. These are installed on a machine at the branch.

The most important of these is the PXE Lite Server (PXELiteServer.exe). It’s installed as a Windows Service, and is responsible for responding to PXE-flavoured DHCP requests and TFTP file transfer requests.

Also installed on the machine at the branch are CopyFromCache, which copies OS boot images from the Nomad (or CCM) cache to the PXE Lite TFTP root.

Central Components

These are installed on the ConfigMgr server.

There’s a web service which is used by PXE Lite Server to interface with the ConfigMgr database; there’s a stored procedure which is installed into the ConfigMgr database (for the use of the web service, unsurprisingly).

There’s also a utility called UpdateBootImage, which is used to prepare ConfigMgr boot images for use with PXE Lite; I’ll discuss in a later post.

OS Image Components

The PXE Lite Central installer copies these to your ConfigMgr server, and then they’re “injected” into the OS image. The list of files to be injected into the OS image is controlled by the OSDInjection.xml file (in C:\Program Files\Microsoft Configuration Manager\bin\i386 by default).

There are:

• NomadPackageLocator: This should be run as a task sequence step; it looks at the TS environment for any required packages, finds out if they’re available in nearby Nomad caches and updates the TS environment accordingly.
• (Optional) NomadInstallSoftware: This is a replacement for the MDT “Install Software” step. You use it if you’re using Nomad to precache packages to the local machine. Unfortunately, the “Install Software” step doesn’t use Nomad to download the packages, so it doesn’t work with precaching. Use this instead.
• (Optional) GetPxeServerAddress: This is useful when you’re running scripts (in Windows PE) that require the location of the TFTP server which you booted from. This information is stored in the registry at boot time, but it’s not in a particularly convenient format for scripting.
• (Optional) TSEnv2: A useful utility for viewing and editing the TS environment. Also includes the ability to edit “read-only” TS variables.

By default, only the NomadPackageLocator is injected. To add the others, you’ll need to edit the osdinjection.xml file.

Read the complete post at http://www.1e.com/1EBlogs/post/2009/07/02/PXE-Lite-v16-Components.aspx