@george1421

Ok ! Thank you for the answer 😉

@george1421 Thank you! This is all i wanted to know 🙂

@r-pawlowski I would be happy to help in anyway I can. Personally, I deploy a bootmanager (grub2win) and the ipxe.efi file to each machines efi partition. Then I can just change the boot managers default to boot straight to fog. It takes a bit of time to get setup, but I found it to be the most reliable as I then didn’t have to worry as much about the bios settings. Theoretically you can use bcdedit commands to change the boot order to boot to network, but that also differs on different hardware.

I digress though, the easy bit for queueing an image to deploy

Follow the setup instructions for the fog API (involves installing the module from powershell gallery and then inputting your API keys and fog server address) Then make sure the host you’re imaging is assigned the correct image, this can be changed in the API if you need that, but for this quick example, we’ll pretend it’s set correct. For an example, we’ll say the hostname of a computer in fog is ‘test-computer’, so this will find the host in fog, then queue an image to deploy on it right now $hostID = (Get-FogHost -hostname 'Test-Computer').id #create a quick json string, this can also be done in a powershell object and converted, but this is just a quick example. #tasktypeID of 1 is a deploy task, if no runtime/schedule time is specified, it defaults to instant deploy # shutdown = 0 is not scheduling with shutdown # I believe other2 = 0 means not a debug # other4 = 1 means to enable wol # isactive =1 means the task is active $jsonData = "{`"taskTypeID`": 1,`"shutdown`":`"0`",`"other2`":`"0`",`"other4`":`"1`",`"isActive`":`"1`" }"; # make the API call to create the new task for your host New-FogObject -type objecttasktype -coreTaskObject host -jsonData $jsonData -IDofObject $hostId;

Once you have this all setup in a powershell module or script internally, you can get things automated pretty smoothly. It’s meant to be modular so it can be applied to any infrastructure or workflow and built upon.

If you need more help let me know and I’ll see what I can do.

@ookami said in Expand Registration Info:

register a machine without a disk installed

Pretty sure you can create hosts from the web UI, all you need is the MAC address.

As to your other questions, I suppose you’re talking about the IPXE registration, and not the web UI. I don’t think RAM is a supported field, or DIMM slot allocation either, nor specific details about RAM.

What your looking for is extra fields in the database. Those are easy enough to add manually, but having them show up in the UI is a lot more work, and involves PHP as well as JS, and I’d be very little help in that area. My PHP skills are basic at best, and FOG’s PHP is fairly advanced. As to the JS, I’ve got zero experience with it.

@george1421 Thank you for your explanation! This makes sense and I was thinking of that same scenario with having more then one of same cloned disk in the same system. I tested most of our external applications and found no issues including ones that record or reference the UUID of the disk in some way and found no conflicts. As you said, the disk is attached to the “parent” record.

@Sebastian-Roth Thanks for the code reference, this does appear to be the function performing what I am referring to and I appreciate your honesty 🙂

Thank you again to both of you on your input! Tremendously appreciated.
I’ve found this to be a great community and hopefully I’ll be able to be give back in one way or another 😄

@boyan-biandov said in How to PXE boot to a Windows PE ISO:

Has there been any development on the ability to boot into one’s custom WinPE ISO on a UEFI system?

Not booting the ISO directly but if you pull apart the ISO you can pxe boot the wim file with FOG.

@wt_101 said in USB Booting a usb network adapter:

ncm–ecm–axge.efi

I have no idea what that boot loader does. Its a component of iPXE.

So tell me about your dhcp server. What is the manufacturer and model.

The idea is that if we can uniquely identify that usb drive, maybe we can send the proper boot file name. If you are using a windows dhcp server and setup efi policies, that is getting us in the direction. That policy looks to see if the arch value is 0 (bios) or 7 or 9 then its uefi. If we can combine the uefi test with the manufacturer id of the mac address then we could send that alternate boot file name when the target computer is uefi and the mac manufacturer matches. Its easier to do with a linux dhcp server or using dnsmasq as a proxydhcp server.

thanks @george1421 i’ll set up a test configuration according to your recommendation…

@brakcounty Well is there a technical reason… none that I can think of. NFS and SMB are similar protocols. They have similar pitfalls in (in)security. But off the top of my head I think it would work. Why isn’t fog using it? Because NFS is built into linux and nothing extra is needed., NFS IS a very fast protocol. too.

You would need to install and enable samba on the FOG server. Two shares will be needed /images and /images/dev.

You will need to rebuild FOS Linux initrd to include the smbclient program. The you will need to update the fog.mount script (in FOS) to use the smbclient to mount the remote storage instead of using the linux mount command.

This thread will give you clues where to look for the tweaks for smb: https://forums.fogproject.org/topic/14791/feature-request-for-fog-1-6-x-configure-image-capture-to-use-nfsv4-instead-of-nfsv3

@george1421 As you said those ports are dynamic, however I found a way to lock some ports to make sure they don’t change from this thread

I did everything except RPCRQUOTADOPTS and the post init scripts ran fine without delay. I’m assuming this won’t change as I had to restart the nfs-kernel-server.service to apply the changes. Hopefully this will stick.

Small note at the bottom of the linked thread, make sure you allow the ports in ufw.

@brakcounty Pretty sure it’s not required.

@p4cm4n ipxe is loaded from the USB drive, EFI/BOOT/bootx64.efi. This file is actually the ipxe.efi kernel file taken from my FOG server in /tftproot/

@zfeng Glad you figured this out. When you find a contradiction, check your premises. You will find that one or more is incorrect, or they are incomplete.

@george1421 WE GOT IT! Thanks for your help!

@juelson Yes and what didn’t work? From your other thread you are using fog 1.4.4. That should support uefi systems, but it probably won’t see your nvme drives. For UEFI systems you need to send a different boot loader than for bios. For bios, dhcp option 67 should be undionly.kpxe that will pxe boot a bios based computer. For uefi based systems you need to have dhcp option 67 set to ipxe.efi. or snp.efi. Since you are using a really old version of FOG with new hardware you might be out of luck until you upgrade to FOG 1.5.x branch.

Points of interesting.

You need to update your FOS Linux kernel to 5.15.x series for the latest hardware support (FOG Web UI -> Kernel update) You need FOG 1.5.9 to update your version of iPXE to the latest version. In the Dell firmware set the disk mode to ahci mode. The default of raid-on will not work with FOG. Disable secure boot in the uefi frimware.

@george1421 Got it. I set up the rules using ufw with the ports from that list. I only tested a Full Reg and Inv so far. It hangs on Running Init Scripts for while then skips it, I think that is the script that pulls the serial number from the bios and auto-populates it as the hostname. I confirmed this when I disabled ufw and that step went right through without delay.

@george1421 So the second part of this is; I would create a custom FOG iPXE menu item to test this next bit. Since refind exists in the http path we can use the http protocol to grab the files you need.

I would start out by cloning the FOG provided refind.conf file to… for this example refind2.conf. Place any files you want to load in the http path on the fog server but not in the fog file path because an upgrade will delete your custom files. For this example lets create a new directory with
mkdir /var/www/html/crefind place your cloned refind2.conf file in there plus any other files you want to load onto the refind vhd.

set http-path http://${fog-ip} set custrefind-path ${http-path}/crefind set refind-path ${http-path}/forg/service/ipxe kernel ${refind-path}/refind_x64.efi imgfetch --name refind.conf ${custrefind-path}/refind2.conf refind.conf imgfetch --name os_linux.png ${custrefind-path}/os_linux.png os_linux.png imgfetch --name theme.conf ${custrefind-path}/theme.conf theme.conf boot || goto MENU

Understand I did not debug this menu at all, I just glued the bits together. So it might work or might now. But the idea is correct. Remember in your refind2.conf file the ipxe vhd has no paths so everything is stored in the root of the vhd. So this config file stanza
icon /EFI/refind/themes/rEFInd-minimal-drunkcj/icons/os_linux.png
Needs to be rewritten as
icon os_linux.png