Debian 8, Fog trunk, PXELinux on MS Server and MS DHCP help
-
@FlowLive said:
@george1421 Well with this one you just sent I still get a blinking cursor (I added /boot/x86/wdsnbp.com)
This is what worked:
set wdsserver:ipv4 <ip_addr_wds_server> set next-server ${wdsserver} chain tftp://${wdsserver}/Boot\x86\wdsnbp.comFunny thing is just changing to forward slashes after Boot and x86 brings back the blinking cursor… thought the changes to the registry was especially for that…
Anyhow, now I tried;
set wdsserver:ipv4 x.x.x.x set net0/next-server ${wdsserver} chain tftp://${wdsserver}/Boot\x86\wdsnbp.comIt Works!!!
Got my PXE Menu showing, got to WDS, booted the wim file!
This is great! Thanks a bunch!
#wiki hash tagging this for addition to the WiKi.
-
I wonder if ip helper on the switches should be changed, I was informed it had been added before, you guys know?
I guess if it works I shouldnt change more but if there’s a potential problem with this let me know!Funny thing now as well is booting to hard drive works, before it was booting memtest instead…
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?
-
@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?
I just tried and succeeded. Here were my steps:
MariaDB [fog]> select pxeID, pxeName from pxeMenu; +-------+-------------------+ | pxeID | pxeName | +-------+-------------------+ | 1 | fog.local | | 2 | fog.memtest | | 3 | fog.reginput | | 4 | fog.keyreg | | 5 | fog.reg | | 6 | fog.quickimage | | 7 | fog.multijoin | | 8 | fog.quickdel | | 9 | fog.sysinfo | | 10 | fog.debug | | 11 | fog.advanced | | 12 | fog.advancedlogin | | 13 | fog.approvehost | | 14 | win7 | | 15 | DBAN | | 16 | DBAN-Zero | +-------+-------------------+ 16 rows in set (0.00 sec) MariaDB [fog]> update pxeMenu set pxeID=17 where pxeID=2; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 MariaDB [fog]> select pxeID, pxeName from pxeMenu; +-------+-------------------+ | pxeID | pxeName | +-------+-------------------+ | 1 | fog.local | | 17 | fog.memtest | | 3 | fog.reginput | | 4 | fog.keyreg | | 5 | fog.reg | | 6 | fog.quickimage | | 7 | fog.multijoin | | 8 | fog.quickdel | | 9 | fog.sysinfo | | 10 | fog.debug | | 11 | fog.advanced | | 12 | fog.advancedlogin | | 13 | fog.approvehost | | 14 | win7 | | 15 | DBAN | | 16 | DBAN-Zero | +-------+-------------------+ 16 rows in set (0.00 sec) MariaDB [fog]> update pxeMenu set pxeID=2 where pxeID=16; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 MariaDB [fog]> select pxeID, pxeName from pxeMenu; +-------+-------------------+ | pxeID | pxeName | +-------+-------------------+ | 1 | fog.local | | 17 | fog.memtest | | 3 | fog.reginput | | 4 | fog.keyreg | | 5 | fog.reg | | 6 | fog.quickimage | | 7 | fog.multijoin | | 8 | fog.quickdel | | 9 | fog.sysinfo | | 10 | fog.debug | | 11 | fog.advanced | | 12 | fog.advancedlogin | | 13 | fog.approvehost | | 14 | win7 | | 15 | DBAN | | 2 | DBAN-Zero | +-------+-------------------+ 16 rows in set (0.00 sec) MariaDB [fog]> update pxeMenu set pxeID=16 where pxeID=17; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 MariaDB [fog]> select pxeID, pxeName from pxeMenu; +-------+-------------------+ | pxeID | pxeName | +-------+-------------------+ | 1 | fog.local | | 16 | fog.memtest | | 3 | fog.reginput | | 4 | fog.keyreg | | 5 | fog.reg | | 6 | fog.quickimage | | 7 | fog.multijoin | | 8 | fog.quickdel | | 9 | fog.sysinfo | | 10 | fog.debug | | 11 | fog.advanced | | 12 | fog.advancedlogin | | 13 | fog.approvehost | | 14 | win7 | | 15 | DBAN | | 2 | DBAN-Zero | +-------+-------------------+ 16 rows in set (0.00 sec) MariaDB [fog]> -
@Wayne-Workman Nice, how do you get to MariaDB? Are those change sticking through trunk updates?
-
@Wayne-Workman
Is it normal that the latest commit I see in sourceforge is r4393?Nervermind, I just realized how it’s setup…
-
@FlowLive said:
@Wayne-Workman Nice, how do you get to MariaDB? Are those change sticking through trunk updates?
The settings should stick.
mysql use fog@FlowLive said:
Is it normal that the latest commit I see in sourceforge is r4393?
Yep.
-
@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.
-
@george1421 said:
@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 have the urge to delete my post but the inner-tech in me says not to… lol
-
I’m going to guess that its not possible to change the display order. There is no concept of display order in the database so I assume the display order is being set based on the record ID where boot from the hard drive is record ID 1. I would not recommend messing with any record ID to alter the display order.
You will receive much bad karma if you do go ahead with this plan.
-
@george1421 Yeah you’re right. The DB changes below do alter the order in which the items are showed, but it doens’t change what’s done.
It appears that the fog default items are hard-coded somehow.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
@Wayne-Workman Magic.
-
I’m late to the party, but no I never got WDS and FOG to play well together. I wasn’t just trying to get them to coexist on the same network though, I was pressing their faces so hard together that they’d forget if they were kissing or not. My goal was to work around the now solved issue of using a Windows DHCP environment to handle Legacy and UEFI PXE coexistence, which WDS can inherently handle.
-
@need2 said:
I’m late to the party, but no I never got WDS and FOG to play well together.
@FlowLive was just able to do this. Its a bit down in the thread, but he has FOG acting as the PXE boot server then you can select the WDS environment from the FOG Menu.
I went the other way around and setup FOG to be able to boot the MDT litetouch image so that you can deploy through MDT from the FOG boot menu. Two different ways to have FOG and MDT/WDS coexist.
-
Saw that. Good work. The only reason I wanted WDS and FOG to work together was to leverage WDS’s handling of UEFI/BIOS identification. But the DHCP method is much more elegant and less resource intensive.
I am glad that you got that working though. Options are valuable when doing IT work.
-
I only want one list of options, is there a way to build a list with FOG management GUI and copy it to: BootMenu.class.php file directly? Or any other suggestion…
Where is located that Advanced boot menu settings? I just want simple list with couple of options, like: “Boot from local drive”, “Diagnostic” (that’s .ISO image) and make a “Quick inventory”… -
Not sure I totally understand what your goal is.
But for the easy part first. You have to be running the SVN trunk build (pre 1.3.0) not the 1.2.0 base. Under the fog settings there is the ipxe boot menu. You must add a new entry then you can set the options to display the new menu item depending on the state of the target computer (new, undefined, all, etc [stating from my memory]). You can add in the iso image as I outlined below. Also @Wayne-Workman just updated a wiki about adding items to the ipxe menu.
Now about the part I’m not sure about. Do I understand that you want to remove most of the standard FOG menu items except for a select few? If that is the case you will need to edit the mysql database. Before I go into that, lets make sure that is what you want to do. (personally I don’t recommend this approach [tweaking the database] because there is no way to know how it will impact FOGs execution, stated as a non developer). Wayne kind of laid out what needs to be done to the database about midway down in this thread.
-
Do I understand that you want to remove most of the standard FOG menu items except for a select few?
That’s exactly what I want… My use of FOG is just as that minimal and I don’t want users to get confused.
… I want to run my .ISO file directly from the first menu, I was succesfully start it from the Advanced menu for now, but I don’t know how to link it to first list below default choice . -
@jukka2015 Ok then, my first recommendation is for you to start a new thread so this one doesn’t get polluted with off topic discussions. Then we can focus on your specific needs.
-
@george1421 said:
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)
Is it important to actually use /var/www/html/ or can I just use /var/www/?
I read docs, in part http://ipxe.org/howto/winpe and I already have a wim file but also created an .iso from MDT 2012, now I’m trying to get all this to boot.
My issue is if I use the ISO, I have to press a key to boot from CD or DVD like if I was booting from an install disc which is a bit different than the current setup on PXE which brought us directly to the LiteTouch environment.
Can’t I simply take the wim file already in MDT and along with other needed files have the same “feel” as if I was using the old PXE boot?
Anyone did that or knows what I mean? -
-
@FlowLive said:
Is it important to actually use /var/www/html/ or can I just use /var/www/?
I read docs, in part http://ipxe.org/howto/winpe and I already have a wim file but also created an .iso from MDT 2012, now I’m trying to get all this to boot.
My issue is if I use the ISO, I have to press a key to boot from CD or DVD like if I was booting from an install disc which is a bit different than the current setup on PXE which brought us directly to the LiteTouch environment.
Can’t I simply take the wim file already in MDT and along with other needed files have the same “feel” as if I was using the old PXE boot?
Anyone did that or knows what I mean?As for point 1. the path is specific to your distribution. The rhel branch of linux has /var/www/html the debian branch uses /var/www. To answer your question it needs to be what is correct for your distribution. What I should have said (maybe) is off the root of your web servers base directory (I’m not sure if that is any clearer).
OK, remember that the ISO image IS a CDROM image. This (press any key to boot) is exactly what you get when you boot from a CDROM. So on the plus side it is working exactly correct. Whoot!! but not as you need.
To get roughly the equivalent of what you have with WDS you need to use the option 2 from my post. This is a bit more complicated to setup, but in this case you will take the boot.wim (or what ever the wim file is called) from MDT rename it to boot.wim and install it in the ISO folder.
Let me see what I can do to archive my setup.
