\nNow I wanted to install a VM on my Windows 10 Hyper-V environment, but when I tried to boot PXE, the machine stays for a while on this status:
\nPerforming DHCP Negotiation
\n
![\"DHCP](\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2015\/09\/dhcp_pxe01.png\")
<\/a>\n
\nAfterwards the System told me, that there was DHCP failed:
\n
![\"DHCP](\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2015\/09\/dhcp_pxe02.png\")
<\/a><\/p>\nI thought, that this would be Firewall\/DHCP\/DHCP-Relay related issue, thus the clients did also not get a Lease on the DHCP Server, I only saw some Discovers and Offers, but not more. The firewall did not show any packets that would be dropped because of missing rules (but while searching the net I found this interesting Site about the Broadcast of DHCP Relays: https:\/\/supportforums.cisco.com\/discussion\/11853326\/dhcp-relay-pxe-nexus-5500).<\/p>\n
It took a while until I realized what I’m missing:
\nDHCP Boot Option 66 and 67!
\n*facepalm*<\/p>\n
After configuring Boot Option 66 to my SCCM\/WDS Server, and added \\smsboot\\x86\\wdsnbp.com to Option 67 from my Client Scope, it worked like a charm.<\/p>\n
Option 66<\/strong>: FQDN-Of-Server (IP is also usable) This means, that you should use the UEFI PXE image within boot Option 67 So how can you get both?<\/strong> Hope this helps<\/p>\n","protected":false},"excerpt":{"rendered":" Hi reader, A few weeks ago I changed a lot within my LAB: I divided the Clients from the Servers into separate VLANs to have a more accurate Lab. Now I wanted to install a VM on my Windows 10 Hyper-V environment, but when I tried to boot PXE, the machine stays for a while […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27,35],"tags":[],"class_list":["post-1903","post","type-post","status-publish","format-standard","hentry","category-operating-system-deployment","category-sccm-2012"],"_links":{"self":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/1903","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1903"}],"version-history":[{"count":0,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/1903\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1903"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1903"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1903"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nOption 67<\/strong>: \\smsboot\\x86\\wdsnbp.com
\nBut wait!<\/strong>
\nWith Option 67 set like above, UEFI Clients will not be able to boot the PXE Image, a Generation 2 Hyper-V VM will show you:
\n<\/a>
\n“The PE\/COFF image is invalid”<\/p>\n
\nOption 67<\/strong>: SMSBoot\\x64\\wdsmgfw.efi
\nAfterwards Hyper-V Gen2 VMs and UEFI Clients will be able to boot from PXE, but BIOS based clients no longer. Here is the PXE Error PXE-E79 shown, when a Generation 1 Hyper-V machine tries to boot a UEFI image:
\n<\/a><\/p>\n
\nDo not use DHCP options, use ip helpers to configure the PXE Server. The client will then automatically ask for the correct PXE boot image.<\/p>\n