• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Recent
    Log in to post
    Load new posts
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All categories
    • All tags
    • N

      Create New Host with API - Snapins wont install - Rename Host not working.

      General Problems
      • • • neuferchris
      1
      0
      Votes
      1
      Posts
      3
      Views

      No one has replied

    • C

      Solved Capturing at Gigabit speeds however only Unicasting at 50Mbps

      FOG Problems
      • • • Clebboii
      7
      0
      Votes
      7
      Posts
      193
      Views

      C

      @Tom-Elliott Yes correct, if its not to do with R8169, then I am unsure what is going on.

    • AxeMeAQuestion22A

      Unsolved Fog iPXE Menu no input

      FOG Problems
      • • • AxeMeAQuestion22
      16
      0
      Votes
      16
      Posts
      328
      Views

      Tom ElliottT

      @jfernandz https://stackoverflow.com/questions/4713088/how-do-i-use-git-bisect

      This is just very basic overview and probably unhelpful.

      If you’re familiar with git, you can switch to different points in time (via the dev-branch) to figure out when we last knew things were good. So first, I’d suggest trying to find exactly when that would’ve been.

      I’d likely start, using dev-branch as the primary “tester case”

      git checkout -b dev-branch

      If you haven’t already done so of course.

      Then I’d put the branch at the same level as when we pushed out 1.5.10:

      git checkout 081d1f4

      Run your install and see if things worked, if they do:

      git checkout dev-branch git bisect start git bisect bad git bisect good 081d1f4

      Of course the 081d1f4 is the hash of the commit where things were good: this might or might not be the 1.5.10 release, so your mileage may very and may need some more adjustment.

      You can find these hashes on https://github.com/FOGProject/fogproject/commits/dev-branch/?after=f7fd3a7a3f188b4540f089a7f38c4d368b53376c+174 using the different pages at the bottom to find a point in time, and they show the hashes on the right and side of each commit.

      It will iterate through things and you just mark after each install/test what worked (as good or bad) by testing:

      If it still fails, you’d run git bisect bad, if it succeeds, you would run git bisect good each iteration.

      It’s tedious I know. but it will help us find the exact point things broke and hopefully from what (maybe it’s something we did, maybe something within ipxe, but gives us a starting point to test things out.)

      Thanks

    • C

      LENOVO L13 : IPXE initialising Devices

      Hardware Compatibility
      • • • Ced58
      5
      0
      Votes
      5
      Posts
      194
      Views

      JJ FullmerJ

      @Ced58 I use this model. It’s best to get either the official Lenovo usb c ethernet adapter or the proprietary Lenovo adapter for the special ethernet port on these. Also in the bios there’s a Mac pass through option that you want to set to internal or second Mac address. With the latest version of fog and kernel it should see that internal mac even if you share an adapter for imaging multiple of that device.

    • K

      Unsolved Deploy image slow speed

      FOG Problems
      • • • Kevinn
      1
      0
      Votes
      1
      Posts
      43
      Views

      No one has replied

    • J

      Lenovo ThinkPad L14 Gen 5 - kernel panic

      Hardware Compatibility
      • • • jflash
      20
      0
      Votes
      20
      Posts
      734
      Views

      J

      @rodluz said in Lenovo ThinkPad L14 Gen 5 - kernel panic:

      @jflash Great! Did you use the default kernel from FOG after the update, or did you use the kernel from my repo?

      I don’t try older kernel, just put new one 🙂

    • I

      Unsolved Install Failed when Compiling iPXE

      FOG Problems
      • • • Itay1787
      2
      0
      Votes
      2
      Posts
      71
      Views

      R

      @Itay1787 I just pushed a change to the dev-branch. Please try installing it again from there and let me know how it goes.

    • R

      Unsolved Disk Selection in FOG

      Windows Problems
      • • • richie086
      2
      0
      Votes
      2
      Posts
      52
      Views

      X

      That would definitely be useful.

    • A

      Change menu when client registers

      General
      • • • alterak
      2
      1
      Votes
      2
      Posts
      85
      Views

      george1421G

      @alterak If you know how to program linux bash scripts this is possible. You will need to edit a script called fog.man.reg that is in FOS Linux (the OS that runs on the target computer to capture/deploy images). I have a tutorial on modifying that program to set a default hostname. But the concepts you need to do what you ware are listed here: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg

    • A

      Unsolved Booting from SAN device 0x08 failed

      FOG Problems
      • • • Alan Lim
      7
      0
      Votes
      7
      Posts
      210
      Views

      A

      I found out what’s causing the problem. The HP BIOS somehow configured the hard disk as a RAID by default. Removing the RAID, and the machine will boot to Windows after iPXE instead of looping.
      Thank you for your input.

    • F

      PXE over IPv4

      General Problems
      • • • Faurel
      7
      0
      Votes
      7
      Posts
      240
      Views

      george1421G

      @Faurel ok good that looks like a clean dhcp process. It would be helpful to have the pcap file in my hand, but you want to expand the OFFER packet. The OFFER packet you can tell from the Info column.

      In the packet you may need to expand the dhcp section. You should see the image similar to below. What is important is the next server IP address should point to IP address of your fog server. and boot file name should be ipxe.efi. You see in this example that the boot file name was not given, this is the error with this packet. The next server and boot file are in the ethernet header. This is the legacy bootp pxe section.

      The next place you need to check is the dhcp options below. You should see dhcp options 66 which should be the IP address of the fog server and dhcp 67 should be the boot file name of ipxe.efi. In this picture this packet is also in error since the dhcp server is not sending out all of the pxe booting info. So if your offer packet looks like this you have a problem.

      Screenshot from 2025-05-07 17-14-20.png

    • A

      FOG operation in different network segments

      General
      • • • alterak
      4
      0
      Votes
      4
      Posts
      135
      Views

      george1421G

      @alterak said in FOG operation in different network segments:

      is there a possibility of automatic separation of locations,

      I’m not sure I fully understand the question, but if you are asking can it automatically pick which location to select based on the IP address of the computer being registered. The quick answer is no, FOG doesn’t currently have that capabilities.

      The bit longer answer is it could if you can be a little creative and can do a little linux bash script programming. In a nutshell, you can customize the bash script that is setup for full registration of computers. The basics of what needs to be done is covered in this tutorial: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg

      The IP address bit can come from this script: https://forums.fogproject.org/post/69725 This post is for getting the IP address to be used in a FOG postdownload script. But the concept will be the same for the fog.man.reg script.

    • G

      could not verify mount point, check if .mntcheck exists /bin/fog.download

      General Problems
      • • • geardog
      2
      0
      Votes
      2
      Posts
      144
      Views

      M

      Any luck clearing up this error? Running into the same thing now setting up a separate storage node location(still local). I get this when trying to deploy an image.

    • V

      Unsolved Kernel panic after selecting a FOG menu item (Full Reg and Inventory, Quick Reg and Inventory, Deploy Image)

      FOG Problems
      • • • villankd47
      1
      0
      Votes
      1
      Posts
      39
      Views

      No one has replied

    • T

      Unsolved Issues Setting Up FOG Server with Hyper-V (Network Boot Fails)

      FOG Problems
      • • • Tycho
      3
      0
      Votes
      3
      Posts
      130
      Views

      T

      @rodluz

      Alright it works thank you.

    • I

      Unsolved added a new storage disk but now I can only image and not restore

      FOG Problems
      • • • icemannz
      4
      0
      Votes
      4
      Posts
      154
      Views

      I

      @JeremyL Hi, yes I am sure I have run Fog under Proxmox as well successfully but this time it didn’t want to work. Anyway once I switched to using Fog running under a Container, it uses much fewer resources and runs just as well.
      So I would recommend switching to running it under a container when possible.

    • R

      Unsolved Run script after OOBE

      Windows Problems
      • • • robertkwild
      6
      0
      Votes
      6
      Posts
      136
      Views

      R

      @rodluz

      ok scrap the local GPO done this and it works

      reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v firstlogon /t REG_SZ /d powershell -noexit -ep bypass c:\users\admin\sysprep\firstlogon.ps1 /f
    • F

      Unsolved FOG 1.5.10.1606 Time of captured image shows UTC time not local time

      FOG Problems
      • • • Fog_Newb
      10
      0
      Votes
      10
      Posts
      215
      Views

      tiatualizadoT

      @Fog_Newb

      Hi,
      I had the same problem as you, and I solved it this way:
      I updated FOG to the latest version (1.5.10.1655), and configured the time zone I wanted in the graphical interface, in “Fog Configuration > Fog Settings > General Settings > TZ INFO”.
      On the VM where I have the FOG server installed, which is an Ubuntu Server 24.04, I only edited the file “/etc/php/8.3/fpm/php.ini” adding the information: date.timezone = “America/Fortaleza” (this is my local time zone). I added this information just below the explanation about timezone that the file itself brings, as you did and showed here in the images.
      I restarted the VM and the time was finally correct in the FOG records.

      I also followed this topic by @Sebastian-Roth, it helped a lot!
      https://forums.fogproject.org/topic/15434/time-lag-between-the-fog-web-interface-and-the-system-time/2

    • P

      realtek RTL8111EPV

      Hardware Compatibility
      • • • pilipp_edv
      5
      0
      Votes
      5
      Posts
      150
      Views

      R

      @pilipp_edv I had a very similar issue to this a while back but it was with an HP laptop. It turned out to be a hardware defect. I was able to get the motherboard replaced under warranty, so maybe you can too for this laptop.

    • J

      Dell Optiplex & Fog PXE Connectivity

      Hardware Compatibility
      • • • Jim Holcomb
      8
      0
      Votes
      8
      Posts
      244
      Views

      J

      Hello All! (Especially Wilsol)

      I used the top configuration ideas from Wilsol, and before I could get through the entire list, darned thing started working. (yeah probably secure boot, thanks Tom for pointing us in the right direction)

      Thanks to everyone for the assist.

      -Jim

    • 1
    • 2
    • 3
    • 4
    • 5
    • 9
    • 10
    • 1 / 10