Subcategories

  • Technical help directly related to FOG.
    9k Topics
    85k Posts
    C

    Hello everyone,

    I have an interesting issue I am facing. I am testing having a storage node at another physical site. The connection seems fine as it can reach the FOG server but one thing I am facing is I am heavily reliant on the Subnet Groups plugin, specifically for identifying what IP a client is upon booting into FOG and assigning to the associated group.

    What I am finding is that when a client boots at the sub-site it will get the boot files from the storage node and get into the ‘DEVICE IS REGISTERED’ screen but the plugin hook never fires thus thwarting my desired process.

    My desired process is when computers are setup in a lab: Booted > Check-in with FOG > Subnet Group assigns computers to proper group > boot loop until all devices are in group > assign an image and task > machines are images. I have this working at the main site.

    Is my best option to have a separate full FOG setup at each site?

    Appreciate anyone’s input!

    FOG version: 1.5.10.1733
    Server OS: Ubuntu 24.04

  • Problems with specific computer models.
    708 Topics
    8k Posts
    A

    @FlorianLenz I did all these steps and it worked with normal USB adapters, but with USB-C-Ethernet adapters does not work, could you help me out?
    (It could be important to know this type-c adapter have 1 HDMI port and 3 normal usb ports)

  • Technical help related to a Windows Problem.
    1k Topics
    8k Posts
    A

    @Sebastian-Roth while poking round in the BIOS on some new Dell machines I did find an option called “Force PXE on next Boot” - https://www.dell.com/support/manuals/en-uk/dell-cmnd-config-v3.0/dell_command_configure_cli-v3/-forcepxeonnextboot?guid=guid-85c17652-4a18-4538-8665-e6b3e777d649&lang=en-us

    You have to have the dell tools installed, but this would be a possible option.

    I know with my current machines when a BIOS update happens it keeps overwriting the boot order so my PXE boot doesn’t happen. Quite annoying!

    I don’t know how I’d go about making the FOG Client execute this command before a task reboot though.

  • Technical help related to a Linux Problem.

    726 Topics
    6k Posts
    J

    @george1421

    Ok so the system in question has an on board nic (enp128s31f6), 1 single port Intel PCI-E Gigabit NIC (enp5s0), and 1 dual port Intel PCI-E Gigabit NIC (enp3s0 and enp4s0).

    So I booted the system with a Linux system rescue USB key. The network cable is plugged into the single port nic. You can see that it has the IP address 172.16.57.22 was fetched. Without any issues. The mac addresses on the identified nics are:

    enp128s31f6 - d4:a2:cd:b7:17:f2 enp3s0 - 00:13:3b:50:b2:b0 enp4s0 - 00:13:3b:50:b2:b1 enp5s0 - ec:08:6b:04:f9:d9 (the one that is attached to the network cable)

    SysResecue-Image.jpg

    Now when I boot the system up into debug mode with FOG into the FOS environment it seems whatever port is pluged into the lan it adopts another NIC’s mac address as shown below:

    FogClient-Image.jpg

    Now you can see when the fog client boots the mac address changes on the port that is connected to the LAN as:

    enp128s31f6 - d4:a2:cd:b7:17:f2 enp3s0 - 00:13:3b:50:b2:b0 enp4s0 - 00:13:3b:50:b2:b1 enp5s0 - ec:08:6b:04:f9:d9 --> Changed to 00:13:3b:50:b2:b0 (the one that is attached to the network cable)

    Now I’ve plugged the cable into enp128s31f6 and setup dhcp on that port as well and tested it. When the fog client starts all of sudden the enp128s31f6 has another NIC’s mac address…

    Just a re-cap if I pull the two network cards, and do the re-image on the system I have no issues. It only occurs when I put an additional nic into the system… Any suggestions?

  • Technical help related to a Mac Problem.

    80 Topics
    942 Posts
    B

    Hello everyone,

    As I work at a secondary school, I was able to get hold of some Catalina iMacs (iMac 14.3).
    I already use FOG to deploy Windows and Linux images on PCs.

    I would like to deploy a LinuxMint image on these iMacs.

    However, I am unable to boot into PXE on them with FOG, and I do not know what is wrong.

    I modified my DHCP server as follows:

    ## FOG class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Apple-Intel-Netboot" { match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386"; option dhcp-parameter-request-list 1,3,17,43,60; if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) { # BSDP List option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47; } elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) { #BSDP Select option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31; # filename "i386-efi/ipxe.efi"; filename "snp.efi"; } } } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } ### END FOG

    I tested ipxe.efi in 64-bit and 32-bit, as well as snp.efi, but it still doesn’t work. I get some kind of spinning planet when I try to boot.

    I admit I don’t fully understand the documentation page: https://wiki.fogproject.org/wiki/index.php/FOG_on_a_MAC

    Thanks in advance!

  • General Developer questions relating to FOG.
    678 Topics
    5k Posts
    S

    Hello!
    I’m new to using FOG and currently having the issue that after a deployment, windows will change the boot order to be first in the boot priority list.
    I’ve done some reading and someone published a FogAPI command to Set-WinToBootToPxe, however I am just not sure how to do this.

    If there are any other solutions for this problem please let me know!
    Cheers.

168

Online

12.4k

Users

17.5k

Topics

156.0k

Posts