Andreas, for what it’s worth I’m hoping to try to set this up in my lab this week.
Thanks for the work you put into this. Mike From: Andreas Hammarskjöld <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, March 23, 2015 at 4:32 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: RE: [MDT-OSD] Legacy and UEFI PXE in same environment Ping pong? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: den 20 mars 2015 08:51 To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Legacy and UEFI PXE in same environment Chis and Daniel, did you get it to work? //A From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: den 17 mars 2015 16:07 To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Legacy and UEFI PXE in same environment Ok, here it is: http://2pintsoftware.com/new-whitepaper-using-dhcp-to-control-uefi-bios-pxe-booting/ //A From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: den 16 mars 2015 23:40 To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Legacy and UEFI PXE in same environment Yeah… Puh… just finished will double check some stuff and launch tomorrow. Seems to work fine all the way though, although lots of inaccurate MS info. //A From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Todd Hemsell Sent: den 16 mars 2015 18:11 To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] Legacy and UEFI PXE in same environment make sure the date is correct in the UEFI or it will not boot. Spent a few days learning that. On Mon, Mar 16, 2015 at 8:49 AM, Andreas Hammarskjöld <[email protected]<mailto:[email protected]>> wrote: Ok, found one bug in Microsoft EFI loaders and the guide is now 16 pages long… Was hoping to get it out the door today but might not make it… rest assure though, it works well. //A From:[email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Chris Carbone Sent: den 13 mars 2015 20:36 To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Legacy and UEFI PXE in same environment Really looking forward to this, thanks for taking the time to write this up. From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: Friday, March 13, 2015 10:50 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Legacy and UEFI PXE in same environment Ok, got it all working with DHCP policies, written most of it up and will make it a little cleaner and test some more over the weekend. So will expect to post this on Monday on our blog. Have a great weekend! //A From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: den 12 mars 2015 20:02 To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Legacy and UEFI PXE in same environment Could be that you end up with a mixture of 66,67 and IP Helpers. Also check if option 43 is set. //A From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Wolf Sent: den 12 mars 2015 19:00 To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Legacy and UEFI PXE in same environment I’m sorry to bring this up but I’m completely pulling my hair our here, and I’m not sure if this is the same issue. We’ve moved into a new building with new Juniper infrastructure, and booting gets me this error: PXE-E53: No boot filename received We have DHCP relay configured, DHCP snooping (security) is off, and I can see in the “Deployment-Server-Diagnostics\Metadata” log the PXE queries being processed. I’ve also loaded Wireshark and I’m no expert but it looks like it all makes sense. But I’m still getting that error above. I have built WDS on 2008R2, 2012R2, and Windows Server TP and none of my attempts are working. I’ve tried adding boot media from Windows 7, MDT, and Windows 10 TP. [cid:[email protected]] Any ideas? I appreciate even the stupidest, most obscure suggestions at this point. Thank you so much everyone, Daniel Wolf From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: Thursday, March 12, 2015 7:12 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Legacy and UEFI PXE in same environment Ok, will try to write something up tomorrow if I find the time, today is not possible. Just to point out, if you are using option 66 and 67 and it doesn’t work without them you are not using IP helpers. Its only required to use the DHCP options when its not possible to use IP helpers. MS also only really “supports” IP Helpers so that should be the approach worth fixing if you can. Some people cannot use IP Helpers, so they have to use DHCP, so will write this up for them. //A From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jacob Alifrangis Sent: den 12 mars 2015 00:56 To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] Legacy and UEFI PXE in same environment We are using DHCP on 2012 R2, do you have a guide or document to do this with 2012? If so, could you send it or copy it on the list? also, we are using ip helpers, but when dhcp options 66,67 are turned off, the systems won’t boot at all. I would hope someone with Juniper knowledge would be able to write a how-to guide for this. I’m sure that cisco has one. Thanks. On Mar 11, 2015, at 1:37 PM, Andreas Hammarskjöld <[email protected]<mailto:[email protected]>> wrote: Hey, Ok, let’s get the facts straight: 1. WDS/PSP can boot UEFI and BIOS machines at the same time, that’s not the issue. 2. When WDS is using IP Helpers/Forwarders (or whatever you want to call it) the DHCP request package from PXE is being forwarded by the router/switch to the WDS box who sends the right boot loader depending on what’s in the request package. So new HW gets UEFI if that’s configured so, and older gets the BIOS bits. All well. 3. When using DHCP scopes and not IP Helpers, they control what you get going. Typically you can only configure one loader at the time, making dual boot impossible. The only way you can deal with this is to configure the DHCP server to send the right options depending on HW capabilities. MS added policy to their DHCP in Server 2012 (I believe) which adds these capabilities. Which DHCP server are you running? If its MS, which OS version? If you are on 2012 then I might be nice and write up in a blog article on how to configure it. //Andreas From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jacob Alifrangis Sent: den 11 mars 2015 04:14 To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] Legacy and UEFI PXE in same environment That's what I'm working on at the moment, as you can see by my post, I can boot either or but not both, Option 60 in dhcp seems to be the culprit, even with ip helpers turned on, I can't boot the workstations. I have full control over dhcp. I am opening a case on Thursday. Sent from Outlook<http://taps.io/outlookmobile> _____________________________ From: Matt Tinney <[email protected]<mailto:[email protected]>> Sent: Friday, March 6, 2015 5:04 PM Subject: [MDT-OSD] Legacy and UEFI PXE in same environment To: <[email protected]<mailto:[email protected]>> How do i get legacy and UEFI PXE with SCCM 2012 R2 CU4 working in the same VLAN? I have my DHCP and PXE Service Point separated on different VLANs. How is it possible to get working? -- Matthew Tinney (206) 778 4432<tel:(206)%20778%204432> Windows Management Experts, Inc www.windowsmanagementexperts.com<http://www.windowsmanagementexperts.com/> This electronic mail transmission may contain confidential information intended only for the use of the individual(s) identified as addressee(s). If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this electronic mail transmission is strictly prohibited. If you have received this transmission in error, please notify me by telephone immediately. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
