<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Ah, perfect! It's very straightforward. Pop into the Windows Deployment Services console, navigate to the Boot Images category and right click on a boot image and choose Create Discovery Image. This is also defined here: http://technet.microsoft.com/en-us/library/dd637996(v=ws.10).aspx . If you don't have any boot images, you can import them off of any Windows installation disc.<div><br></div><div>Follow the wizard steps and it will save a WIM file at the end. Now you just need to wimboot that wim file! For example, if your current wimboot setup is:</div><div><br></div><div><div>:wimboot</div><div> cpuid --ext 29 && set arch amd64 || set arch x86</div><div> kernel wimboot</div><div> initrd winpe/${arch}/ISO/bootmgr bootmgr</div><div> initrd winpe/${arch}/ISO/boot/bcd BCD</div><div> initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi</div><div> initrd winpe/${arch}/winpe.wim boot.wim</div><div> boot || goto failed</div><div> goto start </div><div><br></div><div><br></div><div><br></div><div>You could put your Discover image next to winpe.wim as discover.wim and create a new script section with this modification:</div><div><br></div><div><div><span style="font-size: 12pt;">[...]</span></div><div><span style="font-size: 12pt;"> initrd winpe/${arch}/discover.wim boot.wim</span></div><div> boot || goto failed</div><div> goto start </div></div><div><br></div><div><br></div><div>This would work. If you wish, you can create more than one discover image, for example an x86 one and an x64 one.</div><div><br></div><div>The discover image is just a Windows Setup wim file with additional command line parameters passed to setup.exe, documented here: http://technet.microsoft.com/en-us/library/cc770495(v=ws.10).aspx</div><div><br></div><div>I hope this helps!</div><div><br></div><div>--Ian</div><br><div><hr id="stopSpelling">From: nicholas.krouse@nccvt.k12.de.us<br>To: ian@internals.io<br>Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>Date: Tue, 15 Apr 2014 13:21:36 +0000<br><br>
<style><!--
.ExternalClass .ecxshape {
}
--></style><style><!--
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink {
color:blue;
text-decoration:underline;
}
.ExternalClass span.ecxMsoHyperlinkFollowed {
color:purple;
text-decoration:underline;
}
.ExternalClass p {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass p.ecxmsonormal, .ExternalClass li.ecxmsonormal, .ExternalClass div.ecxmsonormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass p.ecxmsochpdefault, .ExternalClass li.ecxmsochpdefault, .ExternalClass div.ecxmsochpdefault {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass p.ecxmsonormal1, .ExternalClass li.ecxmsonormal1, .ExternalClass div.ecxmsonormal1 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass p.ecxmsochpdefault1, .ExternalClass li.ecxmsochpdefault1, .ExternalClass div.ecxmsochpdefault1 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass span.ecxmsohyperlink {
}
.ExternalClass span.ecxmsohyperlinkfollowed {
}
.ExternalClass span.ecxmsohyperlink1 {
}
.ExternalClass span.ecxmsohyperlinkfollowed1 {
}
.ExternalClass span.ecxemailstyle181 {
}
.ExternalClass span.ecxemailstyle28 {
}
.ExternalClass p.ecxmsonormal2, .ExternalClass li.ecxmsonormal2, .ExternalClass div.ecxmsonormal2 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass span.ecxmsohyperlink2 {
color:blue;
text-decoration:underline;
}
.ExternalClass span.ecxmsohyperlinkfollowed2 {
color:purple;
text-decoration:underline;
}
.ExternalClass p.ecxmsochpdefault2, .ExternalClass li.ecxmsochpdefault2, .ExternalClass div.ecxmsochpdefault2 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass p.ecxmsonormal11, .ExternalClass li.ecxmsonormal11, .ExternalClass div.ecxmsonormal11 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass span.ecxmsohyperlink11 {
color:#0563C1;
text-decoration:underline;
}
.ExternalClass span.ecxmsohyperlinkfollowed11 {
color:#954F72;
text-decoration:underline;
}
.ExternalClass span.ecxemailstyle1811 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}
.ExternalClass p.ecxmsochpdefault11, .ExternalClass li.ecxmsochpdefault11, .ExternalClass div.ecxmsochpdefault11 {
font-size:10.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass span.ecxemailstyle281 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}
.ExternalClass span.ecxEmailStyle38 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}
.ExternalClass .ecxMsoChpDefault {
font-size:10.0pt;
}
.ExternalClass div.ecxWordSection1 {
}
--></style>
<div class="ecxWordSection1">
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">How could I use wimboot to boot the discover image? That would be very excellent as my wimboot works great!</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Nick</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in;">
<p class="ecxMsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";"> Ian Bannerman [mailto:ian@internals.io]
<br>
<b>Sent:</b> Tuesday, April 15, 2014 9:19 AM<br>
<b>To:</b> Nicholas Krouse<br>
<b>Cc:</b> ipxe-devel@lists.ipxe.org<br>
<b>Subject:</b> RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2</span></p>
</div>
</div>
<p class="ecxMsoNormal"> </p>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">Perhaps there may be someone who will take you up on the screenshare; myself, I must work in bit :)</span></p>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">Since you can browse to the ftp share normally, I'm not sure what may be behind the error (I just don't have much experience with tftp :)</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">Is your :wimboot script entry work currently, can it start downloading files? If so, you could work around the issue by creating a discover image and using wimboot to boot the Discover Image
wim file; you would not need to chain wdsnbp.com. <br>
<br>
--Ian</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
<div>
<div class="ecxMsoNormal" align="center" style="text-align:center;"><span style="font-family:"Calibri","sans-serif";">
<hr size="2" width="100%" align="center" id="ecxstopSpelling">
</span></div>
<p class="ecxMsoNormal" style=""><span style="font-family:"Calibri","sans-serif";">From:
<a href="mailto:nicholas.krouse@nccvt.k12.de.us">nicholas.krouse@nccvt.k12.de.us</a><br>
To: <a href="mailto:ian@internals.io">ian@internals.io</a><br>
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
Date: Tue, 15 Apr 2014 13:11:08 +0000</span></p>
<div>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">I did everything is that thread to try to trouble shoot the issue, however I am running WDS 2012r2 without SCCM. Also Yes I have browsed to that tftp server
and had no issues grabbing the file, my DHCP server is on a separate windows box. And it has no problem. If you would be interested we could set up a screen share and I could show you what I mean. I really appreciate your time! But the ipxe linux server running
Ubuntu server has all the diag content and live content and I would like it to point to my WDS server to manage the win images.</span><span style="font-family:"Calibri","sans-serif";"></span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span><span style="font-family:"Calibri","sans-serif";"></span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Thanks</span><span style="font-family:"Calibri","sans-serif";"></span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Nick Krouse</span><span style="font-family:"Calibri","sans-serif";"></span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span><span style="font-family:"Calibri","sans-serif";"></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in;">
<p class="ecxMsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";"> Ian Bannerman [<a href="mailto:ian@internals.io">mailto:ian@internals.io</a>]
<br>
<b>Sent:</b> Tuesday, April 15, 2014 8:58 AM<br>
<b>To:</b> Nicholas Krouse<br>
<b>Cc:</b> <a href="mailto:F.Hummel@ads-tec.de">F.Hummel@ads-tec.de</a>; <a href="mailto:ipxe-devel@lists.ipxe.org">
ipxe-devel@lists.ipxe.org</a><br>
<b>Subject:</b> RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2</span><span style="font-family:"Calibri","sans-serif";"></span></p>
</div>
</div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
<div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">I threw the photo on imgur so it wasn't lost in the chain here: <a href="http://i.imgur.com/TPcEOEb.png" target="_blank">http://i.imgur.com/TPcEOEb.png</a></span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">I don't have much experience with tftp myself, so I'm not particularly sure what steps to take to troubleshoot the error. From your previously sent out menu file I can see you've tried pulling
in various suggestions from the forum thread here: <a href="http://forum.ipxe.org/showthread.php?tid=7242" target="_blank">http://forum.ipxe.org/showthread.php?tid=7242</a> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">How about this, have you confirmed that you can browse to the FTP server from another machine over the path
<a href="ftp://10.200.0.74/boot/x86/" target="_blank">ftp://10.200.0.74/boot/x86/</a> and see the file wdsnbp.com?</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">--Ian</span></p>
<div>
<div class="ecxMsoNormal" align="center" style="text-align:center;"><span style="font-family:"Calibri","sans-serif";">
<hr size="2" width="100%" align="center">
</span></div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">From: <a href="mailto:nicholas.krouse@nccvt.k12.de.us">
nicholas.krouse@nccvt.k12.de.us</a><br>
To: <a href="mailto:ian@internals.io">ian@internals.io</a><br>
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
Date: Tue, 15 Apr 2014 12:28:09 +0000</span></p>
<div>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Ian</span><span style="font-family:"Calibri","sans-serif";"></span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span><span style="font-family:"Calibri","sans-serif";"></span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Thanks for your help. Attached photo is the error I get when trying to boot ipxe then chain load a wds server. The ipxe server has all diags and live environments
and I use wds 2012 r2 from my windows installs for students (its very easy for me to manage). I believe the issue is with my WDS server not having the correct tftp packet size. Thanks in advance for your time!</span><span style="font-family:"Calibri","sans-serif";"></span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span><span style="font-family:"Calibri","sans-serif";"></span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Thanks</span><span style="font-family:"Calibri","sans-serif";"></span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Nick Krouse</span><span style="font-family:"Calibri","sans-serif";"></span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span><span style="font-family:"Calibri","sans-serif";"></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in;">
<p class="ecxMsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";"> Ian Bannerman [<a href="mailto:ian@internals.io">mailto:ian@internals.io</a>]
<br>
<b>Sent:</b> Tuesday, April 15, 2014 8:14 AM<br>
<b>To:</b> Hummel Frank; Nicholas Krouse; <a href="mailto:ipxe-devel@lists.ipxe.org">
ipxe-devel@lists.ipxe.org</a><br>
<b>Subject:</b> RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2</span><span style="font-family:"Calibri","sans-serif";"></span></p>
</div>
</div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">I have systems downloading various wims to 'boot.wim' as he has without issue, yep! </span></p>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">But! I do not have personal experience using bootmgr without fonts (prior to Windows 8), nor info on the potential impact it has on errors. I just gleaned that from the documentation / fourms
discussions. For example, the iPXE documentation has examples on <a href="http://ipxe.org/howto/winpe" target="_blank">http://ipxe.org/howto/winpe</a> and <a href="http://ipxe.org/howto/sccm" target="_blank">http://ipxe.org/howto/sccm</a> where fonts are listed
for older bootmgrs. </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">Thanks,</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">--Ian</span></p>
<div>
<p class="ecxMsoNormal"><span style="font-family:"Calibri","sans-serif";">> Subject: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
> Date: Tue, 15 Apr 2014 14:08:06 +0200<br>
> From: <a href="mailto:F.Hummel@ads-tec.de">F.Hummel@ads-tec.de</a><br>
> To: <a href="mailto:ian@internals.io">ian@internals.io</a>; <a href="mailto:nicholas.krouse@nccvt.k12.de.us">
nicholas.krouse@nccvt.k12.de.us</a>; <a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
> <br>
> Well – found that sequence to be functional by trial-and-error.<br>
> Did you try it?<br>
> <br>
> As far as the fonts are concerned - I do not use older bootmgr versions.<br>
> If you don't load the fonts (there are other sets for older bootmgr) you will not see error messages if the PE does not boot successfully.<br>
> You will just see a black or blue (not BSOD) screen...<br>
> <br>
> mit freundlichen Grüßen<br>
> with kind regards<br>
> <br>
> i. A. Dipl.Ing. (FH) Frank Hummel<br>
> Systementwicklung<br>
> System development<br>
> <br>
> ads-tec GmbH<br>
> Raiffeisenstr.14<br>
> 70771 Leinfelden-Echterdingen<br>
> Germany<br>
> <br>
> Tel.: +49 711 45894-220<br>
> Fax: +49 711 45894-987<br>
> E-Mail: <a href="mailto:F.Hummel@ads-tec.de">F.Hummel@ads-tec.de</a><br>
> Web: <a href="http://www.ads-tec.de" target="_blank">www.ads-tec.de</a><br>
> <br>
> <br>
> <br>
> <br>
> Von: Ian Bannerman [<a href="mailto:ian@internals.io">mailto:ian@internals.io</a>]
<br>
> Gesendet: Dienstag, 15. April 2014 13:23<br>
> An: Hummel Frank; Nicholas Krouse; <a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
> Betreff: RE: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
> <br>
> That's odd. I have not encountered any issues using a similar set up to this - initrd winpe/${arch}/winpe.wim winpe.wim ← Names must match and must match the entry in your bcd!<br>
> <br>
> Are you sure that's a requirement? If boot.wim matches the reference in the BCD this should be fine.<br>
> <br>
> My understanding is also that fonts are only required for Windows 8 and newer WIM/bootmgr combos.<br>
> <br>
> --Ian<br>
> > Date: Tue, 15 Apr 2014 09:30:44 +0200<br>
> > From: <a href="mailto:F.Hummel@ads-tec.de">F.Hummel@ads-tec.de</a><br>
> > To: <a href="mailto:nicholas.krouse@nccvt.k12.de.us">nicholas.krouse@nccvt.k12.de.us</a>;
<a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
> > Subject: Re: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
> > <br>
> > Hi,<br>
> > <br>
> > :wds-server<br>
> > dhcp<br>
> > set wdsserver 10.200.0.74<br>
> > set alternatetftp 10.200.0.74<br>
> > set net0/dhcp-server ${wdsserver}<br>
> > set net0/filename wdsbnp.com ← Typo, not the cause for the current prob<br>
> > set net0/gateway ${wdsserver}<br>
> > set net0/next-server ${wdsserver}<br>
> > set net0/user-class PXEClient<br>
> > -------------------------------------------------------------------<br>
> > Your sequence:<br>
> > :wimboot<br>
> > cpuid --ext 29 && set arch amd64 || set arch x86<br>
> > kernel wimboot<br>
> > initrd winpe/${arch}/ISO/bootmgr bootmgr<br>
> > initrd winpe/${arch}/ISO/boot/bcd BCD<br>
> > initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi<br>
> > initrd winpe/${arch}/winpe.wim boot.wim<br>
> > boot || goto failed<br>
> > goto start<br>
> > -------------------------------------------------------------------<br>
> > You are missing the fonts and left and right must look the same. Should look like this:<br>
> > <br>
> > :wimboot<br>
> > cpuid --ext 29 && set arch amd64 || set arch x86<br>
> > kernel wimboot<br>
> > initrd winpe/${arch}/ISO/bootmgr bootmgr<br>
> > initrd winpe/${arch}/ISO/boot/bcd bcd ← take care! Case sensitive!<br>
> > initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi<br>
> > initrd winpe/${arch}/ISO/boot/segmono_boot.ttf segmono_boot.ttf<br>
> > initrd winpe/${arch}/ISO/boot/segoe_slboot.ttf segoe_slboot.ttf<br>
> > initrd winpe/${arch}/ISO/boot/segoen_slboot.ttf segoen_slboot.ttf<br>
> > initrd winpe/${arch}/ISO/boot/wgl4_boot.ttf wgl4_boot.ttf<br>
> > initrd winpe/${arch}/winpe.wim winpe.wim ← Names must match and must match the entry in your bcd!<br>
> > Imgstat ← enables you to see if all files have been loaded<br>
> > prompt ← stops until you continue after reading imgstat output<br>
> > boot || goto failed<br>
> > goto start<br>
> > <br>
> > My experience with wimboot is that it is quite unreliable. Sometimes it works, sometimes not - depending on the boot.wim file. But I could not find out why it fails with some wim-files and succeeds with others.<br>
> > That's why I use syslinux memdisk and the ISO file containing the very same wim-file failing with wimboot which always works.<br>
> > E.g.:<br>
> > set sanboot-url <a href="http://123.456.789.012" target="_blank">http://123.456.789.012</a><br>
> > initrd ${sanboot-url}/win7pe_x86.iso<br>
> > chain syslinux/memdisk iso raw<br>
> > <br>
> > <br>
> > <br>
> > mit freundlichen Grüßen<br>
> > with kind regards<br>
> > <br>
> > i. A. Dipl.Ing. (FH) Frank Hummel<br>
> > Systementwicklung<br>
> > System development<br>
> > <br>
> > ads-tec GmbH<br>
> > Raiffeisenstr.14<br>
> > 70771 Leinfelden-Echterdingen<br>
> > Germany<br>
> > <br>
> > Tel.: +49 711 45894-220<br>
> > Fax: +49 711 45894-987<br>
> > E-Mail: <a href="mailto:F.Hummel@ads-tec.de">F.Hummel@ads-tec.de</a><br>
> > Web: <a href="http://www.ads-tec.de" target="_blank">www.ads-tec.de</a><br>
> > <br>
> > <br>
> > <br>
> > <br>
> > Von: <a href="mailto:ipxe-devel-bounces@lists.ipxe.org">ipxe-devel-bounces@lists.ipxe.org</a> [<a href="mailto:ipxe-devel-bounces@lists.ipxe.org">mailto:ipxe-devel-bounces@lists.ipxe.org</a>] Im Auftrag von Nicholas Krouse<br>
> > Gesendet: Montag, 14. April 2014 20:22<br>
> > An: <a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
> > Betreff: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
> > <br>
> > Hello <br>
> > <br>
> > I use iPXE for my main boot menu in my classroom for my students. When I attempt to chainboot to my WDS Server 2012 r2 I get error 0x3d126001 and the boot fails. I have searched google and ipxe forums high and low looking for a solution. I use wds over
wimboot as it make management of my wim files quick and easy for me and my students. If there is any way you could help me it would be greatly appreciated! Attached is my current menu.ipxe. Thanks for your time in advance.<br>
> > <br>
> > Thanks<br>
> > Nick Krouse<br>
> > Computer Support Instructor<br>
> > Delaware Skills Center<br>
> > Deskillscenter.org<br>
> > _______________________________________________<br>
> > ads-tec GmbH<br>
> > Sitz: 70771 Leinfelden-Echterdingen<br>
> > Registergericht Stuttgart HRB 224527<br>
> > <br>
> > Geschaeftsfuehrer:<br>
> > Dipl.-Ing. Thomas Speidel<br>
> > _______________________________________________<br>
> > Diese E-Mail enthaelt vertrauliche und/oder rechtlich<br>
> > geschuetzte Informationen. Wenn Sie nicht der richtige<br>
> > Adressat sind oder diese E-Mail irrtuemlich erhalten<br>
> > haben, informieren Sie bitte sofort den Absender und <br>
> > vernichten Sie diese E-Mail. Das unerlaubte Kopieren,<br>
> > jegliche anderweitige Verwendung sowie die unbefugte<br>
> > Weitergabe dieser Mail sind nicht gestattet.<br>
> > _______________________________________________<br>
> > <br>
> > This e-mail may contain confidential and/or privileged<br>
> > information. If you are not the intended recipient (or have<br>
> > received this e-mail in error) please notify the sender<br>
> > immediately and destroy this e-mail. Any unauthorized<br>
> > copying, disclosure, distribution or other use of the<br>
> > material or parts thereof are strictly forbidden.<br>
> > _______________________________________________<br>
> > _______________________________________________<br>
> > ipxe-devel mailing list<br>
> > <a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
> > <a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
> _______________________________________________<br>
> ads-tec GmbH<br>
> Sitz: 70771 Leinfelden-Echterdingen<br>
> Registergericht Stuttgart HRB 224527<br>
> <br>
> Geschaeftsfuehrer:<br>
> Dipl.-Ing. Thomas Speidel<br>
> _______________________________________________<br>
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich<br>
> geschuetzte Informationen. Wenn Sie nicht der richtige<br>
> Adressat sind oder diese E-Mail irrtuemlich erhalten<br>
> haben, informieren Sie bitte sofort den Absender und <br>
> vernichten Sie diese E-Mail. Das unerlaubte Kopieren,<br>
> jegliche anderweitige Verwendung sowie die unbefugte<br>
> Weitergabe dieser Mail sind nicht gestattet.<br>
> _______________________________________________<br>
> <br>
> This e-mail may contain confidential and/or privileged<br>
> information. If you are not the intended recipient (or have<br>
> received this e-mail in error) please notify the sender<br>
> immediately and destroy this e-mail. Any unauthorized<br>
> copying, disclosure, distribution or other use of the<br>
> material or parts thereof are strictly forbidden.<br>
> _______________________________________________</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></div> </div></body>
</html>