@Seb77 this might be helpful. https://wiki.fogproject.org/wiki/index.php?title=CentOS_7#Continue_pre-config
The services are listed, and some UDP ports. This config does work.

@kgosset Well I’m a strong believer of you learn more from your mistakes than your successes, so I’ll only give you a push in a direction.

So lets take a hacker’s approach to this (the 1980s definition of a hacker not the 2000s blackhat).

I already gave you one clue. Point your browser to http://<fog_server_ip>/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00 That will display the FOG iPXE menu as the FOG Project developer (wizards) have create. I figure they know a lot more than I do about the iPXE menu commands and structure. So copy the contents of that menu save it into a text file (save yourself some grief by using notepad++ and not ms windows notepad to edit this file). Save the file as a UNIX script file and name it something like custommenu.ipxe. The ipxe extension is important.

Now you can throw out a lot in this menu, but look for a :Menu line label. Delete the content below (but leave :Menu) down to :bootme (leave :bootme)

Now insert this into the deleted section (between :Menu and :bootme)

NOTE: this has NOT been tested. I only dreamed it up moments ago

menu item fog.mainmenu Return to the FOG iPXE menu item --gap menu --name dell-laptop Dell Laptops item fog.dell.7400 Dell Latitude 7400 item --gap menu --name dell-desktop Dell Desktops item fog.dell.3060 Dell Optiplex 3060 (mini) item --gap menu --name utilities item fog.mdt Boot into MDT choose --default fog.mainmenu --timeout 10000 target && goto ${target} :fog.mainmenu params param mac0 ${net0/mac} param arch ${arch} param platform ${platform} param product ${product} param manufacturer ${product} param ipxever ${version} param filename ${filename} param sysuuid ${uuid} chain http://${boot-url}/service/ipxe/boot.php##params boot || goto MENU :fog.dell.7400 boot || goto MENU :fog.dell.3060 boot || goto MENU :fog.mdt mdt.1903 kernel http://${fog-ip}/wimboot imgfetch --name BCD http://${fog-ip}/mdt/Boot/BCD BCD imgfetch --name boot.sdi http://${fog-ip}/mdt/Boot/boot.sdi boot.sdi imgfetch --name boot.wim http://${fog-ip}/mdt/Sources/Boot.wim boot.wim boot || goto MENU

Place this file on the FOG server in the /tftpboot directory.

Now you need to make a new iPXE menu entry to call this menu.

Menu Item: fog.CustomMenu
Description: Custom FOG Menu
Parameters:
chain tftp://${fog-ip}/custommenu.ipxe
boot || goto MENU

Now pxe boot a target computer. See if your menu works to go into and out of the custom menu. I’ll say this again, I did not test this menu design so there are probably bugs in it. But this is the framework. Once your menu works then we can work on filling out the menu items in your custom menu. I will show you how to get the details for the menu items.

ref:

Contents of /tftpboot/default.ipxe https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images https://ipxe.org/cmd/menu

The ( -5 ) is not part of the name. It is the display of the image number. You would use that number during manual registration of a host where you can assign the image to the host by the number.

@george1421 Many thanks that was along the lines that I was thinking but you’ve confirmed my thoughts are correct. I’ll go ahead now and set it up. Thanks again.

@brakcounty Over all the details about GRUB I lost sight on what this topic is all about… The USB method uses GRUB as boot loader because it can be installed into MBR on the USB to be used to boot legacy machines. As I said before, the alternative USB boot method is not part of the official FOG stuff and has not had enough attention to be fully integrated yet. Not because it’s impossible to do but because we have way to many things on the list.

Now that you use UEFI only in your setup you could skip GRUB altogether and directly boot using iPXE from the hard drive’s UEFI boot partition and should be able to use FOG exactly the way you would if it does PXE boot. For that you just grab one of the iPXE .efi binaries from your FOG server (e.g. /tftpboot/ipxe.efi) and but that on your disk’s EFI boot partition as \BOOT\EFI\BOOTX64.EFI (case doesn’t matter here as Windows will ignor it). When booting the iPXE binary will run its embedded script to get an IP from DHCP and chainload to the FOG boot menu.

@Sebastian-Roth You have to remember that memdisk only works for bios based computers. FOG does not ship a uefi compatible version of memdisk. Also with memdisk that 2.7GB iso image needs to be transferred and fit into memory on the target computer.

As I said if that IS the SUU disk it may not support netbooting. BUT on the PE620 if you use the lifecycle controller to update the system I know you can update the system from a USB stick with the files on it as well as link to an external repository. I just can’t remember at the moment if NFS is supported. I know ftp and CIFS is supported. If its NFS then the OP can just unpack the files in /images and access them via the lifecycle controller.

@Foglalt What would be interesting to know from a running windows OS, to look at the installed nvme hard drive. Were the computers that used that exact hard drive slow where the same model that used brand Y of the nvme drive OK? We seen this condition on a dell computer where they intermixed nvme drives on a single model.

OMG it’s working I spent like 5 hours searching for a solution and now it’s done by your answer.
you are the best bro thanks :)))))))))))))))))))

@george1421 Thanks!, Got it…
I will try your solutions it’s make sense.
🙂

@lelinh Hello and welcome to the FOG project forums. Have you got FOG installed yet? Which version? Anything we can help you with?

@fritoss007 I can give you a hackers approach at doing what you want with the registration process. FOG calls fog.man.reg to invoke the registration process. You can find the source of this program here: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.man.reg

If you understand bash shell programming you can make modifications to this program to alter it registration. I will give you a hint to use notepad++ to edit this file because windows notepad add extra windows junk into the file that will cause error messages during execution.

So now you have this file how can you inject it into the FOS Linux booting process?

You can do the recommended method to unpack and repack the inits as Sebastian outlined. Take a bit of the hacker approach and use a FOG pre-startup script (i.e. post init script) to copy the fog.man.reg from the FOG server to the FOS Linux disk as FOS Linux boots. If you look at this tutorial: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg in the section called fog.patch.customhostname you can see how to “patch” FOS Linux as it boots.

@fritoss007 This may help too, as I believe @Sebastian-Roth has made this script native to the github fogproject code, and can be run at any time:
https://github.com/FOGProject/fogproject/blob/master/utils/FOGiPXE/buildipxe.sh

Just one thing, i can boot only on uefi. It’s a long story…

@george1421 said in better web performance?:

… "I could just copy the 443 virtualhost as 444"but instead of creating a virtual host just setup https on your fog server. There is really 2 sides to this equation. First you have all of the fog inner workings of pxe booting and fog clients. Leave them on port 80. Second use your enterprise ssl certificates on the https port. (actually I’m going to be doing something similar in about a week to our fog server because more browsers are complaining about http sites.)

I’ve started outlining a basic (hack) configuration here to add ssl support to the FOG sever without much pain or messing with PXE or FOG Clients. https://forums.fogproject.org/topic/14464/adding-https-support-to-fog-server-with-centos-7

So far its working.

@dijsil As you seem to have a fairly old version I would suggest you wait until we have released FOG 1.5.9! It’s got a fair amount of bugs fixed since 1.5.8 came out…

@p4cm4n This sounds like an interesting project. I hope that you deleted the posts not by intention!

While I have not used wireguard myself yet it seems to be a nice tool and should allow you to setup things as you intend to. Might need some more considerations on where to place the VPN gateways in each network to get the routing right and not make it too complex.

The slowest link between any one route of them will be 20 Mbps.

A 20 GB image would take two and a half hours if you look at the plain numbers. I am sure it will take longer as you can’t have full speed all the time. It would even be wise to throttle replication speed to not lock up internet access for the offices. But if you don’t change images on a daily basis I reckon this is a reasonable setup.

I would suggest you set Image Manager to “Partcline Gzip Split 200 MB” for the images. This way replication can pick up again if a connection break terminates the replication of an image half way.

I’d like to be able to login to MAIN, and find the host sitting at Client C

For this setup you install FOG in master mode and the main site and as storage nodes at site A, B, C, … but you need to know that capturing an image at a remote site will push this through your VPN tunnel to the master node directly! There is no way to capture “local images to a storage node only”.

Sorry my Portuguese is not good so I’ll answer in english.

If you have windows 2012 server you can configure it to support dynamic dhcp option 67. For windows 2008 you have no joy. For 2008 you can only pick bios or uefi booting. You can still make FOG work in your environment. You will need to install DNSMASQ on your FOG server and let DNSMASQ send out the pxe boot information.

If you have Windows 2012 or later server you can follow these instructions for dynamic booting of bios/uefi: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

To instal DNSMASQ on your fog server: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

One doubt with DNSMASQ is if your client computers are on a different subnet than your fog server you will need to make a change to the dhcp-relay service on your router. You will need to add the FOG server’s IP as the last dhcp server in the dhcp-relay service list.

Mod Note: Translation via Google
Good morning, I have a doubt about dhcp, I am using fog as the right image server !, and using the dhcp server in Windows server 2008, I am having difficulties in options 67 where I put which file to use at boot, this is working all in how much, my doubt and the following is there any way that I can leave the boot options in the dhcp UEFI and LEGACY together, or every time I will have to change within the scope of DHCP?
Thanks in advance!

@j00k4 As I said, the fog-client can run so called snapins to do certain jobs for you automatically, like install software.

Thank you guys. I have now got the latest RC 1.3 and found a problem. I made another thread about it.

@hillie Thanks!