John
Thank you for correcting me on the support level of DHCP options.
I suspect John that as an MVP you will have access to the documentation which
states "Furthermore
the use of DHCP Options to control PXE requests in Configuration Manager 2012
is not supported by Microsoft. Therefore the recommended and supported method
of PXE booting client PCs that are on a different subnet than the DHCP or
WDS/PXE Service Point servers is the use of IP Helpers."
I happened to be reviewing the document yesterday and the words "not supported
by Microsoft" struck me I suppose that you could argue that were you to have an
environment running WDS on Server 2008 where you never had any UEFI involvement
then yes, Microsoft would support you. I am quite sure that regardless of the
above I am sure that you would still be supported since we all know that "not
supported" actually means "not tested" Jason
From: [email protected]
To: [email protected]
Subject: RE: [mssms] ConfigMgr 2012 R2 OSD + PXE :: IP Helper vs. DHCP Options
Date: Fri, 19 Sep 2014 14:18:24 +0000
Supported or not supported (by Microsoft) doesn’t really matter here though
because Microsoft products have nothing to do with most of the PXE process –
it’s almost entirely in the hands of the NIC to do the
right thing. If something truly breaks down, it’s either the NIC’s fault or
the network’s. The DHCP server can play a small role here, but ultimately, that
role is truly insignificant as it’s still up to the NIC to determine what to do
and then to do it. If
the NIC does the wrong thing, there is no way to really troubleshoot it either
and your only real recourse is to call the NIC vendor. There are NICs out there
that some of us have encountered that simply refuse to do the right thing –
these are pretty rare
now days, but they do exist. With iphelpers, you simply have to watch the
traffic if something weird is going on because it’s not up to the NIC anymore.
Experience has shown that iphelpers simply work better and as pointed out, with
UEFI and architecture restrictions, DHCP cannot get the job done because it can
only handle a single architecture.
J
From: [email protected] [mailto:[email protected]]
On Behalf Of Marcum, John
Sent: Friday, September 19, 2014 7:13 AM
To: [email protected]
Subject: RE: [mssms] ConfigMgr 2012 R2 OSD + PXE :: IP Helper vs. DHCP Options
DHCP options are supported.
From:
[email protected] [mailto:[email protected]]
On Behalf Of Jason Wallace
Sent: Thursday, September 18, 2014 6:20 PM
To: [email protected]
Subject: Re: [mssms] ConfigMgr 2012 R2 OSD + PXE :: IP Helper vs. DHCP Options
IP helpers is supported and recommended. DHCP is not and is not
On 19 Sep 2014, at 00:14, Trevor Sullivan <[email protected]> wrote:
Over the past years that I have worked with Configuration Manager, I have
learned to use IP helpers instead of DHCP options, to point client systems to a
Windows Deployment Services (WDS) / PXE service. I have personally experienced
multiple
instances at customer sites, just over the past year, where DHCP options have
simply not worked as expected, and caused erroneous error messages during PXE
boot. As soon as we implement IP helpers, everything “just works.”
I am interested in gathering feedback from people on this mailing list to
confirm or deny my current understanding on this topic. Do you use DHCP options
or IP helper to point clients to the WDS/PXE service? Have you had a negative
experience
using one or the other?
Cheers,
Trevor Sullivan
Microsoft PowerShell MVP
<image001.png>
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.
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.
