I followed Andreas' white paper and can UEFI PXE boot across routers to specific IPs using reservations and dhcp options. It works great. before anybody admonishes me for using options over iphelpers, options serve my needs better. It's a mix of OSes on each subnet, not everybody lives in the same neighborhood here. All of our hosts are on disparate networks and all boot desperate OSes. I need the control per IP to boot to cobbler for linux, WDS for non-SCCM devices and SCCM for SCCM devices. Options let me do that.
The only thing I'll say about it though, is that the errors through the UEFI process leave a lot to be desired. It's the same on screen error whether you're missing a boot wim (x86 and x64) as it is if you don't have a TS advertised to the device. I can control the Class down to one IP like I've done here. [cid:image001.png@01D21B71.FB102780] In this scope when a client gets 109 it will be able to UEFI PXE. And only 109. I set a reservation for a specific host to have 109 and then I can UEFI PXE boot just that one host on this one scope. It crosses routers and ESX host networks. Works quite well. Todd From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Friday, September 30, 2016 3:23 PM To: mssms@lists.myitforum.com; mdt...@lists.myitforum.com Subject: [mssms] RE: UEFI PXE Across Router Are you sure of that it's not using DHCP scopes? I would expect that behavior if using DHCP scopes and you haven't got the option #60 set in the the DHCP scope as there is a bug in the Windows loaders. //A From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike Sent: den 30 september 2016 14:26 To: mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com>; mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] UEFI PXE Across Router I'm setting up a ConfigMgr lab in Hyper-V and testing my OSD task sequence. I can PXE boot both Gen1 (BIOs) and Gen2 (UEFI) VMs that are on the same subnet as my primary site server and PXE enabled DP. So far, so good. I use a VM running Windows Server with RRAS as a router between the "main" subnet and a second subnet that represents a remote office. I have a DHCP Relay Agent defined that points to my DHCP server as well as the IP address of my PXE enabled DP. I can successfully PXE boot a Gen1 (BIOs) machine on this remote subnet, but Gen2 (UEFI) machines eventually time out. In the SMSPXE log on the DP I can see that the request to PXE reached the DP but nothing seems to be reaching back to the client. If I move the Gen2 VM from the "remote" subnet to the "main" subnet (where the servers all reside) then it will successfully PXE boot. It just will not PXE boot across the router. I am not using DHCP scope options. I am only using the DHCP Relay Agent within RRAS. A Gen1 VM will PXE across the router successfully, but a Gen2 will time out. Both Gen1 and Gen2 VMs successfully PXE boot if they are on the same subnet as the servers. Any ideas? I feel like I'm just missing something simple. Thanks Mike Marable Microsoft Systems Engineer Lead Enterprise Device Engineering and Management MCPS, MCITP, MCTS, MCSA, MCSE, MS [ Profile<http://www.mycertprofile.com/Profile/5319166625> ] [ Blog<http://thesystemsmonkey.wordpress.com/> ] ---------------------------------------------------- "The whole point of racing is to charge all the time." -Gilles Villeneuve "If you don't fail, then you're not even trying." -Denzel Washington "Other people's opinions of you do not have to become your reality." -Les Brown ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
