Topics created by drumnj

@lsdo I may also ask you to open a new topic and post your own details there!

You might also read this topic, possibly answers your question as well: https://forums.fogproject.org/topic/15025/move-partitions-on-gpt-layouts-need-people-to-test

That’s a bingo.

However I found this topic: https://forums.fogproject.org/topic/13172/how-to-create-a-fog-ipxe-menu-entry-that-deploys-a-specific-image
A nicer representation with of args through pictures. That topic does go into creating a new iPXE menu entry, which is what I plan to do in preventing fog.deployimage from getting mucked up.

Oh this topic too: https://forums.fogproject.org/topic/8760/pxe-boot-menu-advanced
Though it’s a little dated.

@george1421 you provided some good keywords to help me find those topics.

 

For those that find this post. The steps to my solution:

Use the link george provided, though you don’t need mac:
http://<fog_server_ip>/fog/service/ipxe/boot.php?qihost=1&username=<fog>&password=<password>&imageID=<image_id> To get a better understanding of what you are copying and what is all defined and how they are reprosented read this post:
https://forums.fogproject.org/topic/13172/how-to-create-a-fog-ipxe-menu-entry-that-deploys-a-specific-image In your iPXE menu Parameters text box you just need the long line that starts with kernel making sure to replace bzImage32 with bzImage and init_32.xz with init.xz
Next line: imgfetch init.xz
Then boot as the last line

Thanks again for the help @george1421

Mod Note: I forked your topic off from the hardware working with FOG because your situation needs a bit more explaining.

The newest hardware does not work with the FOS Linux kernels shipped with FOG 1.5.8. The issue is the linux kernel developers are no longer back porting the newest drivers to the Linux 4.19.x series of linux kernels. They are only writing new drivers for 5.x series of linux kernels. (if you want to equate this to the windows world, hardware manufacturers are no longer creating drivers for Windows 7, but now they only release drivers for Windows 10). The linux developers are doing the same, leaving the older ones behind and only writing for the new OS.

Because of this the FOG developers have released 5.6.18 version of the FOG Linux kernel. Understand this kernel has NOT been widely tested with FOG at this time. The deverlopers released this as an option for those FOG admins that have very new hardware that is not supported by linux 4.19.x. Since FOG 1.5.9 is on the edge of final release, 1.5.9 will continue to ship with linux 4.19.x with the option of the FOG admin to upgrade to 5.6.18. Once more people test this new kernel and it proves to be stable then the 5.x line of linux will become default for FOG.

I know its a lot of words to explain, yes I see 5.6.18 addressed your problem, well done.

@drumnj said in Deploying BIOS Boot Order to multiple computers (booting to network 1st):

You said you return yours to “normal” boot (I take it hd 1st)

What I was referring to here is with Dell and CCTK you can set a flag in the bios that basically says on the next reboot boot to the network. On reboot+1 boot what ever the default boot device is.

So if you wanted to do an unattended imaging but your normal boot device was the hard drive you could push out a FOG snapin that called cctk on next boot-boot to the LAN, then schedule a fog deployment. If the fog client is installed it will reboot the target computer and then start imaging right away.