PXE Options in DHCP Configuration for Red Hat 4 DHCP Servers that talk to SCCM R2?
Posted on 2010-08-24
I am in process of building an SCCM R2 server that will eventually replace a WDS server in our production environment. We currently do not have a fully functional lab environment that would facilitate testing SCCM in isolation away from our WDS server.
I have PGP coming onsite in a week to build a Universal Server that will provide While Disk Encryption and will need to talk to our new SCCM server.
Our current WDS Server configuration
WDS Server IP: 10.17.1.106
New SCCM Server IP: 10.17.1.122
DHCP Servers IP: 10.17.1.44 (both of these servers are Red Hat 4)
The DHCP servers currently have the following the following DHCP config:
failover peer "DHCP";
allow known clients;
deny unknown clients;
deny dynamic bootp clients;
option routers 10.17.0.1;
option subnet-mask 255.255.0.0;
option broadcast-address 10.17.255.255;
option domain-name "mud.com";
option domain-name-servers 10.17.1.225, 10.61.1.225;
option ntp-servers 10.17.1.44;
range 10.17.21.1 10.17.21.254;
range 10.17.22.1 10.17.22.254;
range 10.17.23.1 10.17.23.254;
range 10.17.24.1 10.17.24.254;
As you can see, the current DHCP configuration has no PXE options defined....we discovered this yesterday.
It is our intent to setup a new DHCP scope on these same DHCP servers with reservations for a handful of IP/MAC addresses of test laptops and then set an IP boundary for the new SCCM server using this new scope (10.17.200.1-10.17.200.3 as an example) with PXE options defined, and then set up the Distribution point and PXE point on the new SCCM server.
One of my Linux Admins sent me the following:
Does the SCCM Documentation provide any guidance on how to set up the DHCP Server for Option 60? It looks like it is necessary to provide several pieces of information, including the following:
option space PXEClient;
option PXEClient.vendor-specific-info code 43 = string;
option PXEClient.class-identifier code 60 = string;
option PXEClient.pxe-server-name code 66 = string;
option PXEClient.pxe-ip-address code 150 = string;
option PXEClient.filename code 67 = string;
When fully configured, it will look something like this example:
option PXEClient.class-identifier "PXEClient";
option PXEClient.pxe-server-name "10.23.0.1";
option PXEClient.pxe-ip-address "10.23.0.1";
option PXEClient.vendor-specific-info 06:01:0B:08:07:AA:AA:01:0A:17:00:01:00;
option PXEClient.filename "Bstrap\x86pc\BStrap.0";
While, I realize I am asking TechNet/Microsoft folks to look at Linux configs, I want to make sure we do not miss a step and end up troubleshootin for days, I was wondering if anyone had any experience with getting SCCM to respond to PXE boot requests coming from a RHEL 4 DHCP server?
I appreciate your time and help!