The WinOps Blog

PXE support software is installed on your core server as part of the normal OSD installation. However, to enable PXE support, you must first configure PXE settings, then deploy a PXE representative on each subnet of your network where you want PXE support available. PXE representatives provide scalability on your network by deploying OS images to devices in their respective subnets.

Devices on each subnet use normal PXE query and file transfer methods to communicate with their resident PXE representative, which communicates with the core server using Web services (HTTP).

NOTE: Disable other PXE servers
If there is any other PXE server currently running on your network, you must first disable it in order to use LANDesk PXE support.

Deploying PXE representatives

You need to deploy one PXE representative on each subnet where you want to provide PXE boot support. You set up a PXE representative by running the PXE Representative Deployment script on the selected device. This predefined script is available in the Manage scripts tool (click Tools > Distribution > OS deployment > OSD scripts, then click the All other scripts folder).

You can have multiple PXE representatives on a subnet to help with load-balancing. When this is the case, the first PXE representative to respond to a device's request is the one that will be used to communicate with the core server.

NOTE: We recommend that you do not deploy a PXE representative on your core server.

There are no special hardware requirements for the device you select to be a PXE representative, but it must meet the following software requirements:

• Operating system: Windows 2000 Professional SP4, Windows XP SP3, Windows Vista SP2, Windows 7, Windows Server 2000 SP4, Windows Server 2003 SP2, or Windows Server 2008.
  For Windows 2000, ensure that the Microsoft MSI service is running (XP includes MSI by default). If you have installed the latest service pack, the MSI service should be running. Otherwise, you can deploy it to the target PXE representative from the console by following these steps: Click Tools > Distribution > Manage scripts, select the MSI service deployment task under All scripts, and click the Schedule button. In the Scheduled tasks windows, drag the target devices into the window, right-click the MSI service deployment task and select Properties, click Schedule task and specify a start time to schedule the MSI service deployment.
• Installed LANDesk agents: Enhanced Software Distribution agent and Inventory Scanner agent. For more information, see Configuring device agents.

Updating PXE representatives

If you modify the PXE boot option settings (on the Configure > Services > OS deployment tab), you need to update all of your PXE representatives by re-running the PXE Representative Deployment script to propagate those changes to PXE representatives on each subnet. However, re-running the script is not necessary if you simply move PXE proxies from the Available proxies list to the Holding queue proxies list.

Updating Windows PE images

When you modify a Windows PE image in any way, the changes you make must be transferred to all PXE representatives. Normally this is done by re-deploying the PXE representatives, which can take up bandwidth and time. For information about scripts you can use that simply copy the updated Windows PE image to all PXE representatives, see the following document at the LANDesk User Community:

http://community.landesk.com/support/docs/DOC-7619

source : http://help.landesk.com/