Edited undionly.kpxe now receive params: command not found

[george1421]

@jlober1981 Switching over to chat, please check the chat bubble at the top of this window.

[george1421]

@george1421 Working through chat and with Tom’s help we’ve come up with this chain command that should work from the FOG iPXE menu: chain tftp://<SCCM_Server_IP>/SMSBoot\x64\pxeboot.0

So the idea we came up with is to create a menu entry in fog to call the sccm pxe boot instead of doing it from the sccm end to call fog boot.

Once the OP has the pxe booting into FOG setup, he can use FOG to either default or fall through the FOG iPXE menu and chain to the sccm pxe boot by setting the sccm chain menu as default or just use fog as normal and leave the menu entry to select sccm boot if that is required.

The key to getting this setup to work was getting the proper path on SCCM to the pxeboot.0 file.

The OP is going to continue to test this setup, but the preliminary test was successful.

[Tom Elliott]

@george1421 While I know some of SCCM, I can say, I think this method is probably much more accurate than trying to do it in reverse. SCCM, as I understand it, is meant to be used on request. Meaning, when you need to image a device, you tell the device to network boot. From there, it will get its information from the SCCM server and perform the boot to perform the tasking requested.

In our modified scenario, we’re enabling systems to be on network boot mode consistently. All we’re doing is adding a new menu option that allows the user at the system to choose to boot up to disk or if they need to, they can select the SCCM menu option to perform the task sequences as needed.

Hopefully this fits the bill with the requirements, and it allows the users to have a dual type of system for setting up imaging. Essentially you can maintain your ‘light touch’ model if that’s how you’re using SCCM and have a golden base on the FOG Server. (That’s my thoughts, your mileage may vary.)