I got some good advice to remove all DHCP options and just use an IP helper on the router’s VLAN config. I put that in place, and everything is working. Thanks, all.
================ Kenneth Merenda From: [email protected] [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: Friday, October 7, 2016 7:54 PM To: [email protected] Subject: [mssms] RE: IP Helpers for PXE I wouldn’t recommend using IP Helpers and DHCP scope options. The PXE specs are a little dubious on that so depending on HW vendor you get different results. //A From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: den 7 oktober 2016 11:44 To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: IP Helpers for PXE Also look on the server and see if the PC is actually getting to the PSP by reviewing the smspxe log From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Friday, October 7, 2016 10:16 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: IP Helpers for PXE You don’t need 66 either. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Merenda, Kenneth Sent: Friday, October 7, 2016 9:24 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: IP Helpers for PXE Thanks, all, for the feedback. We do have multiple PXE-enabled DP’s across different subnets. Here at my office, our network team confirmed the IP helper is configured on the router, then removed option 67 from the DHCP scope, leaving only 66. Now, BIOS systems get “PXE-E53 no boot filename received” error, and UEFI get “PXE-E18 server response timeout” =============== Kenneth Merenda From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Friday, October 7, 2016 8:38 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: IP Helpers for PXE “As for PXE and UEFI, I followed Andreas Hammarskjöld’s white paper on configuring MS DHCP to boot either BIOS or UEFI depending on how the client is set to boot. http://2pintsoftware.com/whitepaper-using-dhcp-uefi-bios-pxe-booting/<https://urldefense.proofpoint.com/v2/url?u=http-3A__2pintsoftware.com_whitepaper-2Dusing-2Ddhcp-2Duefi-2Dbios-2Dpxe-2Dbooting_&d=DQMGaQ&c=r_B2dqKkHczsuXPCSs5DOw&r=krYjy-Xm1tps1F_nkG9sNKQIT3ZPFrUh3rvr18goJ2E&m=DJkIazG4WvQ2MuWPp74vJSSjCWO_g66xnMMqcL5rZZA&s=aRjZzt7HUcS8fVfbTse5KId_OjbKjkMWUYPqWkizDvs&e=> It wasn’t too bad to set up and it works.” +1 We are in the process of implementing this here. We are in the same boat as you, Todd. The Server group PXE boots their servers to their own infrastructure and we PXE boot ours to SCCM. All we can do it submit tickets to the Networking group to make changes. They did balk when we asked to make the switch to IP Helpers (they have several hundred routers to configure). Instead they’re reconfiguring each DHCP scope using Andreas’ guide. Mike From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Friday, October 07, 2016 9:23 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: IP Helpers for PXE IP helpers assume, however, that you have a homogeneous client base and that EVERYTHING wants to PXE to the same deployment server. Here, I have no control over any of the hundreds of networks but through submitting a ticket to the Networking group, so when WDS first came out we opted to submit just the one ticket to Networking to change the IP helper on specific networks to point to the MS DHCP server we had, and then control options 66 and 67 in each scope and sometimes each IP with reservations. Admittedly, most of what I PXE are servers for deployment, Linux and Windows, some to Cobbler, some to SCCM and some to WDS. Having it this way provides the most flexibility for that. A Windows BIOS client can occupy the IP next to a Windows UEFI client, next to a Linux client. As for PXE and UEFI, I followed Andreas Hammarskjöld’s white paper on configuring MS DHCP to boot either BIOS or UEFI depending on how the client is set to boot. http://2pintsoftware.com/whitepaper-using-dhcp-uefi-bios-pxe-booting/<https://urldefense.proofpoint.com/v2/url?u=http-3A__2pintsoftware.com_whitepaper-2Dusing-2Ddhcp-2Duefi-2Dbios-2Dpxe-2Dbooting_&d=DQMGaQ&c=r_B2dqKkHczsuXPCSs5DOw&r=krYjy-Xm1tps1F_nkG9sNKQIT3ZPFrUh3rvr18goJ2E&m=DJkIazG4WvQ2MuWPp74vJSSjCWO_g66xnMMqcL5rZZA&s=aRjZzt7HUcS8fVfbTse5KId_OjbKjkMWUYPqWkizDvs&e=> It wasn’t too bad to set up and it works. Todd From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Friday, October 7, 2016 7:51 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: IP Helpers for PXE Don’t use DHCP options, set the helpers on the routers. I didn’t have to do anything different to make UEFI work. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Merenda, Kenneth Sent: Friday, October 7, 2016 7:43 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] IP Helpers for PXE [External Email] I have a large environment where the DHCP server and WDS server are not always on the same subnet as the clients. In this case, what IP helpers are needed for PXE of both UEFI and BIOS devices? Currently, we’re using option 66 pointing to the WDS server (SCCM DP), and 67 pointing to SMSBoot\x86\wdsnbp.com. It seems to me that 67 would cause a problem for UEFI, but I’m hesitant to change. Right now, PXE works for BIOS but not UEFI, and I don’t want to break BIOS support just to get UEFI working. SCCM is environment 2012 R2 SP1 CU1 on Server 2008 R2. Thanks, in advance. ----------------------------- Kenneth Merenda ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
