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.
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:
:wimboot cpuid --ext 29 && set arch amd64 || set arch x86 kernel wimboot
initrd winpe/${arch}/ISO/bootmgr bootmgr initrd
winpe/${arch}/ISO/boot/bcd BCD initrd winpe/${arch}/ISO/boot/boot.sdi
boot.sdi initrd winpe/${arch}/winpe.wim boot.wim boot || goto failed
goto start
You could put your Discover image next to winpe.wim as discover.wim and create
a new script section with this modification:
[...] initrd winpe/${arch}/discover.wim boot.wim boot || goto failed
goto start
This would work. If you wish, you can create more than one discover image, for
example an x86 one and an x64 one.
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
I hope this helps!
--Ian
From: [email protected]
To: [email protected]
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
Date: Tue, 15 Apr 2014 13:21:36 +0000
How could I use wimboot to boot the discover image? That would be very
excellent as my wimboot works great!
Nick
From: Ian Bannerman [mailto:[email protected]]
Sent: Tuesday, April 15, 2014 9:19 AM
To: Nicholas Krouse
Cc: [email protected]
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
Perhaps there may be someone who will take you up on the screenshare; myself, I
must work in bit :)
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 :)
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.
--Ian
From:
[email protected]
To: [email protected]
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
Date: Tue, 15 Apr 2014 13:11:08 +0000
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.
Thanks
Nick Krouse
From: Ian Bannerman [mailto:[email protected]]
Sent: Tuesday, April 15, 2014 8:58 AM
To: Nicholas Krouse
Cc: [email protected];
[email protected]
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
I threw the photo on imgur so it wasn't lost in the chain here:
http://i.imgur.com/TPcEOEb.png
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:
http://forum.ipxe.org/showthread.php?tid=7242
How about this, have you confirmed that you can browse to the FTP server from
another machine over the path
ftp://10.200.0.74/boot/x86/ and see the file wdsnbp.com?
--Ian
From:
[email protected]
To: [email protected]
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
Date: Tue, 15 Apr 2014 12:28:09 +0000
Ian
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!
Thanks
Nick Krouse
From: Ian Bannerman [mailto:[email protected]]
Sent: Tuesday, April 15, 2014 8:14 AM
To: Hummel Frank; Nicholas Krouse;
[email protected]
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
I have systems downloading various wims to 'boot.wim' as he has without issue,
yep!
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
http://ipxe.org/howto/winpe and http://ipxe.org/howto/sccm where fonts are
listed
for older bootmgrs.
Thanks,
--Ian
> Subject: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> Date: Tue, 15 Apr 2014 14:08:06 +0200
> From: [email protected]
> To: [email protected];
[email protected]; [email protected]
>
> Well – found that sequence to be functional by trial-and-error.
> Did you try it?
>
> As far as the fonts are concerned - I do not use older bootmgr versions.
> 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.
> You will just see a black or blue (not BSOD) screen...
>
> mit freundlichen Grüßen
> with kind regards
>
> i. A. Dipl.Ing. (FH) Frank Hummel
> Systementwicklung
> System development
>
> ads-tec GmbH
> Raiffeisenstr.14
> 70771 Leinfelden-Echterdingen
> Germany
>
> Tel.: +49 711 45894-220
> Fax: +49 711 45894-987
> E-Mail: [email protected]
> Web: www.ads-tec.de
>
>
>
>
> Von: Ian Bannerman [mailto:[email protected]]
> Gesendet: Dienstag, 15. April 2014 13:23
> An: Hummel Frank; Nicholas Krouse; [email protected]
> Betreff: RE: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
>
> 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!
>
> Are you sure that's a requirement? If boot.wim matches the reference in the
> BCD this should be fine.
>
> My understanding is also that fonts are only required for Windows 8 and newer
> WIM/bootmgr combos.
>
> --Ian
> > Date: Tue, 15 Apr 2014 09:30:44 +0200
> > From: [email protected]
> > To: [email protected];
[email protected]
> > Subject: Re: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> >
> > Hi,
> >
> > :wds-server
> > dhcp
> > set wdsserver 10.200.0.74
> > set alternatetftp 10.200.0.74
> > set net0/dhcp-server ${wdsserver}
> > set net0/filename wdsbnp.com ← Typo, not the cause for the current prob
> > set net0/gateway ${wdsserver}
> > set net0/next-server ${wdsserver}
> > set net0/user-class PXEClient
> > -------------------------------------------------------------------
> > Your sequence:
> > :wimboot
> > cpuid --ext 29 && set arch amd64 || set arch x86
> > kernel wimboot
> > initrd winpe/${arch}/ISO/bootmgr bootmgr
> > initrd winpe/${arch}/ISO/boot/bcd BCD
> > initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi
> > initrd winpe/${arch}/winpe.wim boot.wim
> > boot || goto failed
> > goto start
> > -------------------------------------------------------------------
> > You are missing the fonts and left and right must look the same. Should
> > look like this:
> >
> > :wimboot
> > cpuid --ext 29 && set arch amd64 || set arch x86
> > kernel wimboot
> > initrd winpe/${arch}/ISO/bootmgr bootmgr
> > initrd winpe/${arch}/ISO/boot/bcd bcd ← take care! Case sensitive!
> > initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi
> > initrd winpe/${arch}/ISO/boot/segmono_boot.ttf segmono_boot.ttf
> > initrd winpe/${arch}/ISO/boot/segoe_slboot.ttf segoe_slboot.ttf
> > initrd winpe/${arch}/ISO/boot/segoen_slboot.ttf segoen_slboot.ttf
> > initrd winpe/${arch}/ISO/boot/wgl4_boot.ttf wgl4_boot.ttf
> > initrd winpe/${arch}/winpe.wim winpe.wim ← Names must match and must match
> > the entry in your bcd!
> > Imgstat ← enables you to see if all files have been loaded
> > prompt ← stops until you continue after reading imgstat output
> > boot || goto failed
> > goto start
> >
> > 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.
> > That's why I use syslinux memdisk and the ISO file containing the very same
> > wim-file failing with wimboot which always works.
> > E.g.:
> > set sanboot-url http://123.456.789.012
> > initrd ${sanboot-url}/win7pe_x86.iso
> > chain syslinux/memdisk iso raw
> >
> >
> >
> > mit freundlichen Grüßen
> > with kind regards
> >
> > i. A. Dipl.Ing. (FH) Frank Hummel
> > Systementwicklung
> > System development
> >
> > ads-tec GmbH
> > Raiffeisenstr.14
> > 70771 Leinfelden-Echterdingen
> > Germany
> >
> > Tel.: +49 711 45894-220
> > Fax: +49 711 45894-987
> > E-Mail: [email protected]
> > Web: www.ads-tec.de
> >
> >
> >
> >
> > Von: [email protected]
> > [mailto:[email protected]] Im Auftrag von Nicholas Krouse
> > Gesendet: Montag, 14. April 2014 20:22
> > An: [email protected]
> > Betreff: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> >
> > Hello
> >
> > 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.
> >
> > Thanks
> > Nick Krouse
> > Computer Support Instructor
> > Delaware Skills Center
> > Deskillscenter.org
> > _______________________________________________
> > ads-tec GmbH
> > Sitz: 70771 Leinfelden-Echterdingen
> > Registergericht Stuttgart HRB 224527
> >
> > Geschaeftsfuehrer:
> > Dipl.-Ing. Thomas Speidel
> > _______________________________________________
> > Diese E-Mail enthaelt vertrauliche und/oder rechtlich
> > geschuetzte Informationen. Wenn Sie nicht der richtige
> > Adressat sind oder diese E-Mail irrtuemlich erhalten
> > haben, informieren Sie bitte sofort den Absender und
> > vernichten Sie diese E-Mail. Das unerlaubte Kopieren,
> > jegliche anderweitige Verwendung sowie die unbefugte
> > Weitergabe dieser Mail sind nicht gestattet.
> > _______________________________________________
> >
> > This e-mail may contain confidential and/or privileged
> > information. If you are not the intended recipient (or have
> > received this e-mail in error) please notify the sender
> > immediately and destroy this e-mail. Any unauthorized
> > copying, disclosure, distribution or other use of the
> > material or parts thereof are strictly forbidden.
> > _______________________________________________
> > _______________________________________________
> > ipxe-devel mailing list
> > [email protected]
> >
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
> _______________________________________________
> ads-tec GmbH
> Sitz: 70771 Leinfelden-Echterdingen
> Registergericht Stuttgart HRB 224527
>
> Geschaeftsfuehrer:
> Dipl.-Ing. Thomas Speidel
> _______________________________________________
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich
> geschuetzte Informationen. Wenn Sie nicht der richtige
> Adressat sind oder diese E-Mail irrtuemlich erhalten
> haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese E-Mail. Das unerlaubte Kopieren,
> jegliche anderweitige Verwendung sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
> _______________________________________________
>
> This e-mail may contain confidential and/or privileged
> information. If you are not the intended recipient (or have
> received this e-mail in error) please notify the sender
> immediately and destroy this e-mail. Any unauthorized
> copying, disclosure, distribution or other use of the
> material or parts thereof are strictly forbidden.
> _______________________________________________
_______________________________________________
ipxe-devel mailing list
[email protected]
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
