How to Configure the PXE Service Point
Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2
You can use the PXE protocol to initiate operating system deployments to Configuration Manager 2007 client computers. Configuration Manager 2007 uses the PXE service point site role to initiate the operating system deployment process. The PXE service point must be configured to respond to PXE boot requests made by Configuration Manager 2007 clients on the network and then interact with Configuration Manager 2007 infrastructure to determine the appropriate deployment actions to take.
You must assign the PXE service point site role to a server supported by Configuration Manager 2007 operating system deployment. The service site can be a primary or secondary site server.
If you are using Windows Server 2003 you must install the Remote Installation Services (RIS) and the Windows Automated Installation Kit (Windows AIK). If you are using Windows Server 2003, Service Pack 2 you must install the Windows Deployment Services using Add or Remove Programs. Configuration Manager 2007 SP1 and Configuration Manager 2007 R2 require the Vista SP1 version of Windows AIK.
The PXE protocol is not secure. Both the PXE server and the PXE client should be located on a physically secure network, such as in a datacenter to prevent unauthorized access to your site.
Use the following procedure to create the PXE service point site role.
To create the PXE service point
In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Site Systems.
To start the New Site Role Wizard, click Action on the Configuration Manager console, and then click NewRoles. Alternatively, in the Actions pane, or right-click Site System Roles, and then click New Roles.
You can deploy and configure multiple PXE service point servers depending on your network topology.
On the General page of the wizard, optionally provide the fully qualified host name (FQDN) for the server, and then specify which account credentials should be used to install the site system role.
On the System Role Selection page, select PXE Service Point.
On the PXE-General page, specify whether the PXE service point is enabled to respond to incoming PXE requests.
This option will temporarily disable this PXE server and should be selected only if there are conflicting PXE servers on the network.
You can specify a password for computers that boot to PXE.
For unattended deployments, do not specify a password. If a password is specified, a user must be present at the client computer to enter the password or the deployment will fail.
Specify whether this server will respond to PXE service requests on all network interface adapters or a specific network interface adapter in the Interfaces section by entering the MAC address for all applicable interfaces.
If multiple PXE service points are used, enter the number of seconds the PXE service point should wait before responding to PXE requests in the Delay box. Use this option only when there are multiple PXE servers on the same subnet.
On the PXE-Database page, specify the account the PXE service point should use to connect with the Configuration Manager 2007 database. The account specified must have the necessary permissions on the client computers running Microsoft SQL Server and Configuration Manager 2007 client permissions. For more information, see About the PXE Service Point Database Connection Account. You will also need to specify whether the PXE service point will create a self-signed certificate or whether a certificate should be imported by the user. If you import a certificate it must be issued by a certification authority (CA) trusted by the site.
For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.