• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. JYost
    3. Topics
    • Profile
    • Following 1
    • Followers 0
    • Topics 29
    • Posts 70
    • Groups 0

    Topics

    • JYostJ

      Question regarding the new Fog Agent (FOG 1.6.x) prior to syspreppping

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      2
      0 Votes
      2 Posts
      127 Views
      Tom ElliottT

      @JYost With agent 0.1.23 or later, you do not need to stop or disable it before Sysprep, and you do not need the SetupComplete.cmd line. The agent waits until Windows setup has finished before it enrolls, checks in, or reboots. It starts on its own after OOBE completes.

      On an older agent, update it on the reference machine first. Or use the same steps as before with the new service name: sc config fog-agent start= disabled before Sysprep, then sc config fog-agent start= delayed-auto and sc start fog-agent in SetupComplete.cmd.

      You also do not need to clear the agent’s key before capture. Each deployed machine has different firmware IDs, so the agent drops the captured key and enrolls as itself. A deploy from your server approves it automatically.

      No firewall rule is needed. The agent opens no listening port. It only connects out to the FOG server over HTTPS.

      Details: https://docs.fogproject.org/installation/client/install-fog-agent#capturing-an-image-with-the-agent-installed

    • JYostJ

      FOG 1.6 web interface

      Watching Ignoring Scheduled Pinned Locked Moved General
      1
      2 Votes
      1 Posts
      140 Views
      No one has replied
    • JYostJ

      Windows Recovery Screen after imaging with USB dongle

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      3
      0 Votes
      3 Posts
      1k Views
      N

      @Tom-Elliott to note, this has been happening on all our Lenovo L14s laptops (with no LAN ports), tested with 3 different Lenovo USB-C LAN Adaptors

      When booting back up, it brings the Blue screen error:

      ‘Recovery
      Your PC couldn’t start properly
      After multiple tries, the operating system on your PC failed to start, so it needs to be repaired.
      Error code: 0xc0000001
      You’ll need to use recovery tools. If you don’t have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer.
      Press Enter to try again
      Press F1 to enter Recovery Environment
      Press F8 for Startup Settings
      Press Esc for UEFI Firmware Settings’

      As John mentioned, we used the same LAN adaptor previously and managed to image via FOG successfully before.

      i even tried changing the mac address to the default internal laptop mac address after the initial fog image completed (when it shutdowns the laptop) and booted the laptop back up to see if it helps but no luck

    • JYostJ

      Broken iPXE boot loader

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      13
      0 Votes
      13 Posts
      12k Views
      JJ FullmerJ

      @george1421 said in Broken iPXE boot loader:

      @Mightmar I wonder if the devs for iPXE has changed something in the ipxe source code to cause this error message about autoexec.ipxe not found. This should be supplied by the fog project add on files. I’ll take a look at the compiler to see if something has changed. You should not see this error.

      Reinstalling 1.5.10 will fix the error of the latest build of iPXE. Also you mentioned about a later version of FOG. Yes you can install that over 1.5.10 without issue. It should also have updated (but not the newest version of iPXE).

      This is the first post I found searching autoexec.ipxe so replying here for future searchers.

      This was an addition in a recent ipxe version, and is meant to be a way to add ipxe based functionality without needing to recompile ipxe in order to edit an embedded script (https://github.com/ipxe/ipxe/discussions/1237#discussioncomment-9847219), I can’t find the post/doc again but I remember reading in one place that ipxe added it as part of the hopes of getting a signed ipxe shim so users could use the signed shim and then use this script to add what they can’t embed. While technically we can create a blank file in /tftpboot/ i.e. just

      #!ipxe

      which will remove the error during boot, this can then cause kernel panics when loading into FOS. Why it does this is a bit of a mystery at the moment, maybe it’s adding to or replacing another part of our pxe menu scripts that causes something in loading the kernels to lose access to ramdisk drivers. But adding it can break everything, so for the time being, just ignore the error.

    • JYostJ

      Snapin File Exists option missing from Create New Snapin after 1.5.10 update

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      2
      0 Votes
      2 Posts
      589 Views
      No one has replied
    • JYostJ

      Disabled snapins are still showing up in snapin selection screen

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      1
      0 Votes
      1 Posts
      535 Views
      No one has replied
    • JYostJ

      Question on hostname changer

      Watching Ignoring Scheduled Pinned Locked Moved General Problems
      1
      0 Votes
      1 Posts
      501 Views
      No one has replied
    • JYostJ

      Domain username name not auto populating in field

      Watching Ignoring Scheduled Pinned Locked Moved General Problems
      3
      0 Votes
      3 Posts
      1k Views
      JYostJ

      @Sebastian-Roth
      Thank you Sebastian, I will give that a try. Thanks again for the excellent support! You can close this ticket.

    • JYostJ

      Unable to capture image after performing iPXE boot loader update

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      15
      0 Votes
      15 Posts
      6k Views
      JYostJ

      @george1421

      I just tried another capture after changing the FOG client on the image to point to our FOG server in Germany. This time there was a normal 1 minute pause during the resizing process then Partclone G-zip started and imaged without problems. All seems normal again…gremlins have been eradicated. You can mark this as solved.

    • JYostJ

      Unable to Image a Lenovo E14 Gen2 (Type 20TA/20TB)

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      8
      0 Votes
      8 Posts
      4k Views
      JYostJ

      Just heard back from our Cali, Columbia office. All is well, device imaged fine with no errors. Thanks again for the awesome support!

    • JYostJ

      Question regarding Snapin install order

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      2
      0 Votes
      2 Posts
      580 Views
      Wayne WorkmanW

      @jyost Search the forums for snapin order. You’ll find several threads. Here’s one that probably will help:
      https://forums.fogproject.org/topic/12784/snapin-order

    • JYostJ

      Snapins check in but don't install

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      2
      0 Votes
      2 Posts
      813 Views
      JYostJ

      Disregard - problem has been solved. I renamed a .msi setup file but forgot to edit the filename in the snapin configuration.

    • JYostJ

      Question regarding fogproject password reset

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      2
      0 Votes
      2 Posts
      778 Views
      S

      @jyost Use that value set as password=... in /opt/fog/.fogsettings to (re)set the fogproject account password.

    • JYostJ

      Kernel Update failed

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      5
      0 Votes
      5 Posts
      2k Views
      JYostJ

      Well, sync’ing everything up a second time worked like a charm. Thank you for your help Sebastian!!

    • JYostJ

      Question regarding the snapins ordering

      Watching Ignoring Scheduled Pinned Locked Moved General Problems
      1
      0 Votes
      1 Posts
      482 Views
      No one has replied
    • JYostJ

      Old MAC's retained after being changed in web interface

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      2
      0 Votes
      2 Posts
      648 Views
      S

      @jyost said in Old MAC's retained after being changed in web interface:

      FOG 1.58

      We don’t have a team of developers to backport fixes so this needs to be verified an issue in the latest dev-branch version. We won’t be able to help you with a fix for 1.5.8.

      With that said we can still see if this is really a bug or just a missunderstanding. From what I remember when you change a MAC address it will add the old one as a secondary MAC to that Host. And I think there was a bug in 1.5.8 web UI that did not show the secondary MACs (were somehow hidden). Please see if that’s the case.

    • JYostJ

      Roughly half of reimaged devices do not run first run scripts in autounattend.xml after imaging.

      Watching Ignoring Scheduled Pinned Locked Moved Windows Problems
      8
      0 Votes
      8 Posts
      4k Views
      george1421G

      @jyost said in Roughly half of reimaged devices do not run first run scripts in autounattend.xml after imaging.:

      If the renaming/domain join occurs AFTER the final restart I will need to run a powershell script to install our AntiVirus software and also add a domain user account to the Remote Desktop Users group –

      You might want to consider deploying this action with a snapin. Snapins will run after all of the other imaging actions are complete.

    • JYostJ

      Which Linux distro(s) have been tested with FOG - What is recommended?

      Watching Ignoring Scheduled Pinned Locked Moved General
      6
      0 Votes
      6 Posts
      3k Views
      JYostJ

      We will be building a new VM with Ubuntu 20.x…it won’t be an in-place upgrade. I will post any issues we run into…fingers crossed.

    • JYostJ

      Lenovo T14 won't Pxe Boot - "Kernel missing the correct driver"

      Watching Ignoring Scheduled Pinned Locked Moved Hardware Compatibility
      7
      0 Votes
      7 Posts
      3k Views
      I

      I need to update the storage nodes, how are they updated? the Web Master updated it and it worked correctly

    • JYostJ

      Best practice regarding AD accounts and FOG imaging

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      4
      0 Votes
      4 Posts
      1k Views
      Wayne WorkmanW

      @JYost are you registering all of the hosts? How are you setting the preferred names? The way I did it was I set names as I registered, and then did an image deploy right there during registration from FOG’s boot menu, typically. I don’t know how much experience you have with FOG but Tom is right, naming and domain joining should work 100% of the time. If it’s not, something isn’t right and we need those logs to help.

    • 1 / 1