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.
