<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>Hello,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I’ve been trouble-shooting an issue were I was unable to PXE boot/install Windows 10 in a RHEL 7.4 KVM VM from a Server 2016 WDS. Note that RHEL 7.4’s KVM VM uses iPXE v1.0.0+ for its PXE boot loader. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>After many hours of trouble-shooting, I finally came up with a work-around that allowed an unattended iPXE boot/install within the KVM VM. I had to change the (DHCP Server Option 67) “Bootfile Name” on the WDS from this:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>C:\RemoteInstall\boot\x86\wdsnbp.com<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>to this:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>boot\\x86\\wdsnbp.com<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I've attached screen captures of the healthy KVM iPXE boot process and WDS server “Bootfile Name” setting.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Although the solution I came up with was to make a modification on the WDS server, that doesn't make it a Microsoft/Windows problem. The WDS configuration change is a work-around specifically for iPXE compatibility. The “C:\RemoteInstall\boot\x86\wdsnbp.com” syntax previously used works fine with a multitude of other PXE boot loaders.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>A friend and I just spent 60+ labor hours trouble-shooting this issue that seems to only exist between iPXE (used in KVM) and Server 2016 WDS. Any chance you could add some compatibility information to your website concerning this issue (to help others with a similar issue)? Any chance you’ll release a version if iPXE that is more compatible with or tolerant of possible WDS “Bootfile Name” syntax?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thanks,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Rob<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>RHEL7.4_KVM_iPXE_Boot_Screen_00.png<o:p></o:p></p><p class=MsoNormal>iPXE startup in KVM<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>RHEL7.4_KVM_iPXE_Boot_Screen_01.png<o:p></o:p></p><p class=MsoNormal>Successful use of the Bootfile Name value<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>RHEL7.4_KVM_iPXE_Boot_Screen_02.png<o:p></o:p></p><p class=MsoNormal>Proper transition to TFTP for initial Pre-installation Environment (PE) download<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>RHEL7.4_KVM_iPXE_Boot_Screen_03.png<o:p></o:p></p><p class=MsoNormal>Initial PE menu - Post-iPXE boot<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Server_2016_WDS_Bootfile_Name.png<o:p></o:p></p><p class=MsoNormal>Server 2016 WDS “Bootfile Name” configuration<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>*********************************<o:p></o:p></p><p class=MsoNormal>Rob Ramsey<o:p></o:p></p><p class=MsoNormal>Network Engineer / Unix System Admin.<o:p></o:p></p><p class=MsoNormal>Paragon Solutions Inc./EPASS<o:p></o:p></p><p class=MsoNormal>Office: 850-883-4034<o:p></o:p></p><p class=MsoNormal>Cell: 719-201-2362<o:p></o:p></p><p class=MsoNormal>Robert.Ramsey.10.ctr@us.af.mil<o:p></o:p></p><p class=MsoNormal>*********************************<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>