@FlowLive said:
Now I read that it’s not possible to change the menu order of things, WDS being all the way down, can’t I just bump it up a little?
Where it should be, way at the bottom. Where do you think the competition would put it, front and center?? 
I’m glad/happy you got that wds thing fixed out. From what I’ve read those forward / backslashes are a PITA to get worked out. It looks like you got the right combination to get it done.
Looking and the chain load link that you sent. I did see this reference
set netX/next-server ip.of.wds.server
imgexec tftp://${netX/next-server}/boot/x86/wdsnbp.com
What I think I might have missed is in my guess is setting the network adapter 0:
set wdsserver:ipv4 192.168.1.88
set net0/next-server ${wdsserver}
Its interesting that the chain does work (kind of) that it does gram the wdsnnp.com file, but there is something in the referral that its missing to continue.
FWIW: All of the 7010 SFF Dells we have have “Intel
82579LM Gigabit Network Connection” according to our inventory tool.
Just thinking out loud here, but if target device doesn’t support PXE net booting in UEFI mode, might it support USB booting in UEFI mode. The thought is build a ipxe boot environment on a usb flash drive and boot off that. I’m pretty sure that ipxe boot environment can be setup to boot off usb flash. The question would be does the hardware support this…
^^^^ (just using a graphic to isolate ideas)
On some hardware platforms you need to enable the legacy ROMS to get support for both USB and PXE booting in UEFI mode. I don’t have any lenovos here to test that idea on.
@Jbob said:
@george1421 Centos 6 appears to be missing some of the modules I require. I’ve been trying to hunt down the exact dependencies I’d need, or if need be, a new policy with different rules / modules.
That’s why we are going through this. 
No worries on my part. We’ll get them worked out.
@Jbob said:
@george1421 there is a DHCP section in the post. I will include DNS as well. Right now I wish to keep those options separate. Eventually the installer should automatically configure the firewall based on installation preference.
Sorry I missed that. I copied the top sections and skipped the bottom.
No luck compiling for me on Centos 6.7
[root@centtest SELinux]# make -f /usr/share/selinux/devel/Makefile fog.pp
Compiling targeted fog module
/usr/bin/checkmodule: loading policy configuration from tmp/fog.tmp
fog.te":50:ERROR 'unknown class service used in rule' at token ';' on line 3260:
allow unconfined_t init_t:service enable;
#============= unconfined_t ==============
/usr/bin/checkmodule: error(s) encountered while parsing configuration
make: *** [tmp/fog.mod] Error 1
During the install of FOG, it asks to make fog a dns and dhcp server but those ports are not listed in the script.
For clarity, I took and rebuilt a clean centos box. I set the firewall rules and then installed the latest SVN trunk. I just remembered that I need to set the selinux policy since it is centos defaults. But any way the plan is to apply your settings to a clean install install your policies and then install the latest SVN trunk.
Ok a couple of things that hit me right away.
The instructions above for rhel is for Centos 7.X and newer. The firewalld function is not available on Centos 5 and 6. Centos 5 iptables is a mess so I wouldn’t even recommend installing FOG on Centos/rhel 5. So for Cento/rhel 6 you must use the “Other” instructions.
The second thing I ran into using the Other instructions is the first line for adding the modules to the iptables-config. The last IPTABLES_MODULES entry config wins. So after running that first line and restarting iptables I only had one new module loaded “nf_conntrack_netbios_ns” The product of that line looks like this in the iptables-config file.
IPTABLES_MODULES=“nf_conntract_tftp”
IPTABLES_MODULES=“nf_conntrack_ftp”
IPTABLES_MODULES=“nf_conntrack_netbios_ns”
The correct syntax should be
IPTABLES_MODULES=“nf_conntract_tftp nf_conntrack_ftp nf_conntrack_netbios_ns”
I have the screen shots if you need them but I think that info should get you pretty close.
@FlowLive said:
Took longer than expected, had the FOGFTP error and had to fix that.
Now I try the option in the menu but unfortunately all I got is a blinking cursor
crud, I just noticed that the forum ate some of my command line. Lets try it as code. You have to pay attention to the double forward and back slashes.
Menu Item: wds.BootIt
Description: Launch WDS Boot x86
Parameters:
set wdsserver:ipv4 192.168.1.88
set next-server ${wdsserver}
chain tftp://${wdsserver}/Boot\\x86\\wdsnbp.com
The slowness in the forum is driving me a bit nuts today. Its taking me almost 12 minutes to post this.
The typical workflow for a fully configured but blank FOG server is this
@FlowLive No boot option: ?? I said it was a guess.
But that should build the FOG PXE menu correctly for chaining. Since the documentation for the new fog pxe menu management is not written yet, I could only try to reverse engineer what the fields are and what they do to the pxe menu. It should work, but no promises.
I’m going to take a SWAG at it.
If you go into FOG settings and add a new PXE Menu item, and enter these settings.
Menu Item: wds.BootIt
Description: Launch WDS Boot x86
Parameters:
set wdsserver:ipv4 <ip_addr_wds_server>
set next-server ${wdsserver}
chain tftp://${wdsserver}/Boot\x86\wdsnbp.com
In the example above replace <ip_addr_wds_server> with the real IP address of your wds server. Then PXE boot your client and see if it chains correctly.
As I mentioned before, I haven’t use WDS. Can you answer what do you need to enter in options 66 and 67 to make WDS work?
Can we make fog chain to WDS probably.
Can I make FOG boot the MDT lighttouch image (which your deploying with WDS), yes.
@FlowLive First let me apologize for hijacking this thread a bit. But in the end I think I have a workable solution for your environment to allow you to run FOG along side MDT. I understand what you are trying to do by chaining FOG and MDT/WDS. Wayne has provided a way for you to mesh WDS and FOG into a pxelinux boot menu here.
http://www.vcritical.com/2011/06/peaceful-coexistence-wds-and-linux-pxe-servers/
And in my case I have worked out a way to launch a MDT install from the FOG pxe boot menu. This would allow you to launch and install MDT as you do today, but though FOG. It would provide a smooth transition path from MDT deployment to eventually a FOG deployment.
I’m going to say this with the most sincerity. The path you are on is kind of a waste of time to building your own kernel. You can do it that way if you want, but there are now documented ways to get it done without having to mess with syslinux. One of the issues with PXELinux (at least the last time I looked at it) was it only supports tftp booting and all the restrictions round that. Where iPXE can use other boot methods like http. Now if you use ipxe for your boot loader then chaining would work better. Then you could chain to fog using something like a call to
kernel ipxe.krn dhcp && chain http://<fog_ip_address>/fog/service/ipxe/boot.php?mac=${net0/mac}
(stolen from the fog pxe default configuration)
Bingo, I have it.
I have two ways to boot a MDT litetouch image via FOG.
The first way is how I stated to take the iso image created by MDT and move that to your FOG server (on rhel variants) in /var/www/html/iso folder. The file I used was to move LiteTouchPE_x86.iso from the MDT deployment share to that …/iso folder as ltpe_x86.iso. Then to create the PXE boot menu as I outlined below. The freeze issue I had was related to how I created the VM. I created it as a linux VM not a windows VM (shame on me). Once I reset it to a windows 7 VM the system booted to the lite touch menu.
By using instructions found in Wayne’s link below. http://ipxe.org/howto/winpe I used this as the bases of option 2. I’ve created WinPE USB boot drives so I already had WAIK installed and already had a boot.wim created, so I’m not going into that part. But in the target winpe environement I took the ISO folder and moved it to the fog server in /var/www/html/ISO (which is different than the <lowercase> iso folder from option 1). I placed the wimboot file (downloaded from the link provided by Wayne) in the web root folder /var/www/html. Then copied the LiteTouchPE_x86.wim from MDT deployment share to /var/www/html/ISO as boot.wim. And finally created the FOG PXE menu with these settings.
Menu Item: winpe.BootMDT_x86
Description: Boot MDT LiteTouch x86
Parameters:
kernel http://<fog_server_ip>/wimboot
initrd http://<fog_server_ip>/ISO/boot/bcd BCD
initrd http://<fog_server_ip>/ISO/boot/boot.sdi boot.sdi
initrd -n boot.wim http://<fog_server_ip>/ISO/boot.wim boot.wim
boot
I still would like to understand how I can use the variables to the fog server IP address so I don’t have to hard code the IP address into the boot menu. That would make the instructions a bit more dynamic.
Understand what I’ve done is a first pass attempt to make FOG deploy both FOG images and to launch MDT’s litetouch image without the need of a WDS server (which would have made things a bit easier in one respect)
@Wayne-Workman said:
I would disagree with where the ISO is being kept - the installer blasts the fog web root every time it runs. I would suggest using /var/www/html/iso or creating an /iso directory and then doing a symbolic link to /var/www/html
Lets not get what I’ve done so far confused with the finished and working solution. Right now I’m in the mode, “Can I just make it work”. The next phase is; “How should it be setup for production”. I agree with you that the container should not be in the …/html/fog directory. It should probably be a symbolic link from /var/www/html/iso to /opt/fog/iso or something similar to keep the big files on the /opt partition (if setup that way) and off the / partition.
I am going through this for selfish reasons since with our old (non-FOG) pxe server we had utilities setup (like dban and bart-pe) that I need to bring those forward and launch them from the FOG server. I now have a slightly better understanding of the fog pxe boot menu so I think I can do this without a whole lot of pain.
I have had some successes and a failure with this approach but I think I’m on to something.
What I found so far (through a bit of hacking) is that I can create a new PXE menu using the FOG management GUI.
Menu Item: winpe.x86
Description: WinPE LiteTouch x86
Parameters:
initrd http://<fog_server_ip>/fog/iso/ltpe_x86.iso
chain memdisk iso raw
I created a directory /var/www/html/fog/iso
Then I copied the MDT LiteTouchPE_x86.iso to that iso folder as ltpe_x86.iso
I then created a new VM with 4GB of ram and configured it to boot via pxe.
I was able to pxe boot into the iso image but somewhere during the boot the system hung. The GUI came up and I did have a user surface before the system froze.
The other thing I found is that in the boot menu, I would have thought that the following variable ${boot-url} would have expanded but it did not, so I had to use a text literal ‘<fog_server_ip>/fog’ to get the system to boot. While this wasn’t a total success (because the image did not fully boot), it isn’t a total failure either because it started to work.
I’m going to have to table this for tonight, but I have a few other ideas I’ll try in the AM.
@Wayne-Workman said:
I didn’t want to go that route because of the number of files needed in the /tftpboot folder. I was holding that as a plan B. The iso image is just one file, plus changes to the ipxe boot menu. Do you know of a wiki that discusses the menu management? I’m having an issue finding much details on it.
In researching how to make pxe boot menu changes with the new system I found this link.
https://wiki.fogproject.org/wiki/index.php/Advanced_Boot_Menu_Configuration_options
The second frame under “Examples Basic Menu” shows exactly what needs to be done in the old menu to boot a winpe.iso image. So I’m not swimming in uncharted waters.