Heya Todd, Have read most of the PXELinux articles I could find, but they all talk about chaining to WDS and not SCCM.
Thanks for sharing. Appreciated. rg Richard 9. januar 2014, 23:10:48, you wrote: > > > > From what I remember, I don’t think you can mess with the PXE stuff > for SCCM without it breaking, as you have to actually change the > boot programs wds uses at the command line with wdsutil. I’d much > prefer to do that on a separate server from my SCCM implementation. > > > > I'm sure you've seen this, but this is where I started : > http://www.syslinux.org/wiki/index.php/WDSLINUX. Just the top > section down to but not including "Adding linux images to > boot/install" was useful for me. In the end, I had my "central PXE > server" chaining PXE requests to SCCM 2007, SCCM 2012, WDS, Cobbler, > and local disk or aborting PXE altogether based on the menu option. > You can control everything through the menu file named 'default'. > There's an example of one in the link there. The only addition > you’ll need is pxechain.com from SYSLINUX 4.04. It goes in the > same place as pxelinux.0. In fact looking at all of the versions > available, some of the files have changed in more recent versions, > so I’d stick to 4.04. It has all of the files listed and should work as the > page describes. > > > > I'll look when I get home to see if I still have a copy of my > 'default' on an older work computer archive. My work machine was > life cycled to a smaller disk and it may not have made the switch. > It looked like this though when it was done. You can add the > picture in the background easily enough and change the colors all in that > ‘default’ file. > > > > I’m pretty positive this is what chained sections look like, but > I’ll look for the one that actually worked for me tonight at home… > > > > LABEL linuxpxe > > MENU LABEL Linux PXE server... > > KERNEL pxechain.com > > APPEND 123.45.67.89::pxelinux.0 > > > > LABEL WDS > > MENU LABEL Another Windows Deployment Services Server > > KERNEL pxechain.com > > APPEND 12.34.56.78::Boot\x86\wdsnbp.com > > > > LABEL SCCM > > MENU LABEL An SCCM Server > > KERNEL pxechain.com > > APPEND 12.34.56.79::SMSBoot\x86\wdsnbp.com > > > > > > Hope this helps. > > > > Todd > > > > > > > > > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Richard > Sent: Thursday, January 9, 2014 2:58 PM > To: Mote, Todd > Subject: Re: [mssms] PXE Chaining to SCCM 2012 R2 from PXELinux > > > > Heya Todd, > > > > Sounds much like what we have in mind. > > > > Could the main WDS server be the SCCM server ? (perhaps playing with > > the binding order?) > > (We are currently doing a overhaul of some infrastructure components, > > and would like to kill off a few servers with only very light roles, > > like PXE) > > > > Do you happen to have or can you remember how you configured the > > menu entry for SCCM ? > > > > Thanks. > > > > rg > > Richard > > > > 9. januar 2014, 15:46:25, you wrote: > > > >> I've done this in a lab. PXEChaining means passing PXE instructions > >> on to another PXE server. > > > >> In my test, this is what I did. > > > >> Install WDS on a "main PXE server" > >> Add the necessary PXELinux files and edit the service and the menu > >> files to forward PXE requests on to the next PXE server, the SCCM > >> server, cobbler, another WDS, etc.. > > > >> My original intent was to provide central PXE address for everything, > >> Linux, SCCM and WDS, and just forward each request depending on the > >> menu item chosen. It worked in practice, but because there is always > >> a choice, zero touch is no longer an option. > >> Because we image servers using zero touch I scrapped the idea. My > >> server task sequence depends on being able to PXE again and make it > >> back to the SCCM server, during the sequence. > > > >> But yes, it works. > > > >> Todd > > > > > > > >> -----Original Message----- > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Andrew Craig > >> Sent: Thursday, January 9, 2014 7:07 AM > >> To: [email protected] > >> Subject: RE: [mssms] PXE Chaining to SCCM 2012 R2 from PXELinux > > > >> Nope, there is a standalone (completely separate from sccm) wds server > >> with a pxelinux component installed. It has a GUI which allows user to > >> select which boot image to use. The boot image must then redirect to > >> the sccm server. Unless I am missing what true chaining is, I haven’t > >> heard the term before > > > >> Andy > > > >> -----Original Message----- > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Tigchelaar, > >> Martijn > >> Sent: 09 January 2014 13:51 > >> To: [email protected] > >> Subject: RE: [mssms] PXE Chaining to SCCM 2012 R2 from PXELinux > > > >> Craig, > > > >> In that case you are basically loading a regular boot WIM of the PXE > >> server. That is not the same as chaining from PXELinux to SCCM. > >> I think the true chaining option is preferred. > > > > > > > >> -----Original Message----- > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Andrew Craig > >> Sent: Thursday, January 09, 2014 1:26 PM > >> To: [email protected] > >> Subject: RE: [mssms] PXE Chaining to SCCM 2012 R2 from PXELinux > > > >> Yes. And it works. > > > >> I create a bootable media from sccm, then modify this and upload to an > >> existing wds infrastructure which uses a custom pxelinux setup. > >> You need to extract the boot wim from the bootable media and copy the > >> sms data from the root of the media to the wim, reseal and then upload > >> this to the pxe image store. > > > >> I have a document somewhere with exacter instructions, I'll try and > >> dig it out this afternoon > > > >> -----Original Message----- > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Richard > >> Sent: 09 January 2014 13:14 > >> To: [email protected] > >> Subject: [mssms] PXE Chaining to SCCM 2012 R2 from PXELinux > > > > > >> Hi > > > >> Anyone one tried (and succeded) to implementent SCCM 2012 R2, into an >> existing PXE infrasstructure ? > > > >> The hope is to just add a menu item to the PXE Boot menu, and then pass the >> control onto SCCM. > > > >> Current PXE setup is based on PXELinux. > > > >> rg > >> Richard > > > > > > > > > > > >> This e-mail message and any attachments may contain legally > >> privileged, confidential or proprietary Information, or information > >> otherwise protected by law of Meritor, Inc., its affiliates, or third > >> parties. This notice serves as marking of its "Confidential" > >> status as defined in any confidentiality agreements concerning the > >> sender and recipient. If you are not the intended recipient(s), or the > >> employee or agent responsible for delivery of this message to the > >> intended recipient(s), you are hereby notified that any dissemination, > >> distribution or copying of this e-mail message is strictly prohibited. > >> If you have received this message in error, please immediately notify > >> the sender and delete this e-mail message from your computer. > > > > > > > > > > > > > > > >
