SCCM 2012 with Linux PXE

[PolishPaul]

I'm setting up an SCCM 2012 lab and i need to be able to integrate an existing Linux based PXE environment. Does anyone have any experience in setting up such an environment or perhaps can point me in the right direction while i try to read up on the whole topic?

[PolishPaul]

I'm attempting to pxe chain from either my SCCM 2012 server or from the linux server. Still not able to get it to work and i'm working out the kinks.

 

For booting from windows, i found this article:

http://www.vcritical.com/2011/06/peaceful-coexistence-wds-and-linux-pxe-servers/

however, this doesn't seem to work for me. My guess, from what i can see, is that SCCM handles the PXE configuration and not WDS. I tried to set the wdsutil settings but the PXE boot doesn't seem to respond to them.

 

So my question is:

How can i tell SCCM PXE to boot using a specific file? (goal here is to have a cusom menu like in the linked example)

[anyweb]

i havnt tried what you are trying to do but you could configure configmgr as normal and enable PXE, then once done reconfigure WDS to point to your pxe chain, this may work, but i havn't tried it, so maybe you can try it ?

[desek]

I'm attempting to pxe chain from either my SCCM 2012 server or from the linux server. Still not able to get it to work and i'm working out the kinks.

 

For booting from windows, i found this article:

http://www.vcritical...ux-pxe-servers/

however, this doesn't seem to work for me. My guess, from what i can see, is that SCCM handles the PXE configuration and not WDS. I tried to set the wdsutil settings but the PXE boot doesn't seem to respond to them.

 

So my question is:

How can i tell SCCM PXE to boot using a specific file? (goal here is to have a cusom menu like in the linked example)

 

I followed the same guide a couple of months ago. However, with SCCM PXE Point you should copy the files to "\RemoteInstall\SMSBoot" folder and got it working.

[PolishPaul]

I noticed that WDS and SCCM have their boot / PXE files in a different location (\remoteinstall\boot vs \remoteinstall\SMSboot) as Desek described. The guide mentiones setting the WDS with this command:

wdsutil /set-server /bootprogram:boot\x64\pxelinux.0 /architecture:x64

Which i believe refers to \remoteinstall\boot. I tried using a different path such as \smsboot\ etc.. but i have not been able to get this to work. Somehow i feel that SCCM is doing its own thing with the PXE settings and the wdsutil is not affecting its PXE boot settings. Am i correct in that assumption?

 

I'm going to double check my work again....

 

EDIT:

Also,

 

I noticed that when i do:

wdsutil /get-server /show:all

I get this output:

SETUP INFORMATION FOR SERVER
[---------------------------------------------

Server State:
OS version: 6.1
WDS operational mode: Native
Installation State:
RemoteInstall location: C:\RemoteInstall
RemoteInstall share up-to-date: Yes
Boot files installed:
		x86  - Yes
		x64  - Yes
		ia64 - No

[---------------------------------------------

CONFIGURATION INFORMATION FOR SERVER
[---------------------------------------------
An error occurred while trying to execute the
Error Code: 0x4E66
Error Description: <No description available>

 

Desek, in the system that you have it working, can you get more output with that command than i did?

Edited April 23, 2012 by PolishPaul

[Tuomas järvinen]

Hi, I'm trying to implement a kind of menu for SCCM managed WDS pxe using pxelinux.

I found this thread, and wondering, if you got it to work.

 

The problem I have on the lab environment is that every time only SCCM boot.wim is booted, no pxelinux menu is given, and the boot goes to sccm boot wim image. I have changed the dhcp option value 067 (bootfile name) to boot\x86\pxelinux.com (or smsboot\x86\pxelinux.com) and copied/renamed files to right SMSboot folder.

 

also tied to execute

 

wdsutil /set-server //bootporgraM:boot\x86\pxelinux.com /arcitehture:ARCH

wdsutil /set-server /N12bootprogram:boot\x86\pxelinux.com /arcitehture:ARCH

 

and

wdsutil /set-server //bootporgraM:SMSboot\x86\pxelinux.com /arcitehture:ARCH

wdsutil /set-server /N12bootprogram:SMSboot\x86\pxelinux.com /arcitehture:ARCH

 

where ARCH is substituded with x86 and x64).

But allways SCCM boot.wim is used...

 

Thanks.

[Ryleh]

Old thread and there is hardly any info out there but because this is the only link that comes up with a Google search, I figured I'd share my solution.

 

The solution is renaming pxelinux.com to pxeboot.com (effectively replacing it) in your \\Reminst\SMS Boot\ folder.

 

I used syslinux 6.03 with the syslinux components being from the bios subfolders (not EFI!).

[spgsitsupport]

I have it setup this way using Syslinux 4.0.6 (seems that 6.0.1/2 do not work due to chainload freezes as per this):

 

 

pxelinux.0 being served from SCCM PXE (DHCP entry), which presents menu via RemoteInstall\SMSBoot\x86\default

(boot local HD, boot SCCM, boot to my OTHER menu where I boot iPXE undionly.0 (undionly.kpxe * created with specific internal script using

make EMBEDDED_IMAGE=

to autoload pxelinux.cfg\default from my other server) & then boot anything via IIS http (way faster then tftp)

#!ipxe
dhcp net0 
set 209:string pxelinux.cfg/default 
set 210:string http://10.0.0.55/tftpboot/
chain ${210:string}pxelinux.0

* .kkpxe: PXE NBP payload which keeps vendor-provided (non-[g|i]PXE) UNDI and vendor-provided (non-[g|i]PXE) PXE intact

 

"pxe http iso boot" search on reboot.pro will give even more info, and also forum.ipxe.org

# default on SCCM server
DEFAULT vesamenu.c32
PROMPT 0
timeout 80
TOTALTIMEOUT 9000

MENU TITLE PXE Boot Menu (x86)
MENU INCLUDE pxelinux.cfg/graphics.conf
MENU AUTOBOOT Starting Local System in 8 seconds

label localboot
  MENU LABEL Boot from first hard drive
  COM32 chain.c32
  APPEND hd0 0
  timeout 80

label sccm
menu label Start SCCM 2012 R2
COM32 pxechn.c32
APPEND 10.0.0.86::smsboot\x86\wdsnbp.com -W

label tftp-other
menu label Back to SPGS default PXE menu
COM32 pxechn.c32
APPEND 10.0.0.55::undionly.0

LABEL Abort
MENU LABEL Exit
KERNEL abortpxe.0

# default on my OTHER server
DEFAULT vesamenu.c32

  menu hshift 0
  menu width 59
  menu margin 8
  menu color title * #FFFFFFFF *
  menu color border * #00000000 #00000000 none
  menu color sel * #ffffffff #999999ff *
  menu color hotsel 1;7;37;40 #ffffffff #999999ff *
  menu color tabmsg * #ffffffff #00000000 *
  menu vshift 8
  menu rows 16
  menu helpmsgrow 16
  prompt 0
  allowoptions 1
  
MENU BACKGROUND pxelinux.cfg/boot.png
MENU TITLE SPGS PXE Boot Menu

LABEL localboot
  MENU LABEL Boot from first hard drive
  COM32 chain.c32
  APPEND hd0 0
  timeout 80

   LABEL TinyCore-Ghost
        MENU LABEL TinyCore with Ghost
	kernel tinycore/withGhost/vmlinuz
	append initrd=tinycore/withGhost/core.gz cde vga=791 nozswap
	
   LABEL HTTP-grub.exe-win7pe
   	MENU PASSWD ***********************
	MENU label http Win7PE iso - command line
	LINUX grub.exe
	INITRD http://10.0.0.55/tftpboot/isos/win7pe.iso
	APPEND --config-file="map (rd)+1 (hd32); map --hook; root (hd32); chainloader (hd32)"   

   LABEL wimboot
       MENU PASSWD ***********************
       MENU label wimboot multiWin7PE - Gui
       KERNEL ipxe.lkrn
       initrd wim-boot.ipxe

where wim-boot.ipxe is:

#!ipxe
 dhcp net0 && echo IP address: ${net0/ip} ; echo Subnet mask: ${net0/netmask}
    kernel http://10.0.0.55/tftpboot/wimboot 
    initrd http://10.0.0.55/tftpboot/BOOTMGR          BOOTMGR
    initrd http://10.0.0.55/tftpboot/BOOT/BCD         BCD
    initrd http://10.0.0.55/tftpboot/BOOT/BOOT.SDI    BOOT.SDI
    initrd http://10.0.0.55/tftpboot/boot/WINPE.WIM BOOT.WIM
    boot

One could read more here or here

[spgsitsupport]

And for UEFI use just pure ipxe menu (with no pxelinux at all) while booting to ipxe.efi

[spgsitsupport]

This has nice writeup