• Full registration customised

    General
    2
    0 Votes
    2 Posts
    2k Views
    J

    Do you think writing this in fog.man.reg after line

    [[ $exists != "#!ok" ]] && handleError "Unable to register host: $exists ($0)\n Args Passed: $*"

    could do it :

    host="" imageid="999" blDoAD="Y" realdoimage=$(echo -n 1 | base64) res="" user64=$(echo "fog" | tr -d '\012' | base64) pass64=$(echo "password" | tr -d '\012' | base64) while [[ $res != "#!ok" ]]; do echo -n " * Enter hostname for this computer: " read host if [[ ${#host} -gt 15 ]]; then host=${host:0:15} echo " | Truncated to 15 characters: $host" usleep 2000000 fi host=$(echo $host | base64) res=$(curl -Lks --data "host=$host" ${web}service/hostnameloop.php 2>/dev/null) [[ $res != "#!ok" ]] && echo "$res" done dots "Attempting to register host" res="" while [[ -z $res ]]; do res=$(curl -Lks --data "sysuuid=${sysuuid}&mac=$mac&advanced=$(echo -n 1 | base64)&host=$host&imageid=$imageid&doimage=$realdoimage&doad=$blDoAD&username=$user64&password=$pass64" ${web}service/auto.register.php 2>/dev/null) echo "$res" usleep 2000000 done . /bin/fog.inventory usleep 2000000
  • Problems with storage nodes in the same system

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    151 Views
    No one has replied
  • 0 Votes
    6 Posts
    578 Views
    I

    This can sometimes happen after you have sysprepped an machine and missed the boot menu prompt, entering the Out-of-box-experience. Trying to shutdown the device will leave the dirty bit resulting in the unclean error.

    To avoid having to sysprep again, allow the device to enter OOBE again and hit shift+F10 and enter “oobe\bypassnro” at the resulting command prompt. Once you hit enter, the system will perform a clean reboot, clearing the dirty bit and allowing Fog to capture the filesystem correctly.

    Hopes this helps someone else as some Dell machines are notorious for failing to get an IP from IPV4 PXE boot.

  • FOG Service on Client reboot loop

    Unsolved Linux Problems
    2
    0 Votes
    2 Posts
    878 Views
    A

    @adam1972 FYI, there are no pending tasks… I just tried creatinga snapin bash that uninstalls the client, to see if it would stop repeatedly rebooting… It just sits there. The log has a “a power operation is pending, aborting module”… I can’t find anything that’s is pending… especially after rebooting several times lol

  • 0 Votes
    2 Posts
    323 Views
    I

    are they all in a clean shutdown state before starting?
    do they already have an OS?

  • srvpublic.crt has wrong IP

    Unsolved FOG Problems
    5
    0 Votes
    5 Posts
    751 Views
    I

    Just came across the same issue, did you fix it?

  • HP Pro SFF 400 G9 deploy very slow

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    188 Views
    No one has replied
  • Error when deploying images

    General Problems
    2
    0 Votes
    2 Posts
    1k Views
    P

    @Pingu Ok, i find out that my /images was a little bit bugged and got my snapshots in dev folder with the mac address as name folders, i moved them into /images and renamed them with the image name i configured on the Web Interface and it runs !!
    Hope this will not happen for the next snapshots.

  • W10 Error when capturing image (ACPI Bios Error)

    Unsolved Windows Problems
    2
    0 Votes
    2 Posts
    1k Views
    R

    @ReinierG said in W10 Error when capturing image (ACPI Bios Error):

    Hey,

    I’m trying to capture an image on a Surface Go 2. The process starts off well, but when it reaches 6.79%, the speed drops significantly, and I encounter the following error message:

    ACPI BIOS Error (bug): Could not resolve symbol [\Tz.TZ00], ZE_NOT_FOUND (20230628/psargs-332) ACPI Error: Aborting method \_SB.PC10.LPCB.ECO._Q14 due to previous error (AE_NOT_FOUND) (20230628/psargs-529)

    What can I try to fix this issue? The machine hasn’t been sysprepped, but I also haven’t fully installed the OS yet, so that shouldn’t be necessary. The current installation is at the keyboard/language selection screen. Also stopping and resending the task did not fix this issue.

    Thanks in advance!

    I tried capturing the image on an HP ProBook G7, and it worked fine. Online, I found some information suggesting that this error might be related to a firmware issue. Could that be the case?

  • W11 : Unattend file.

    Unsolved Windows Problems
    1
    0 Votes
    1 Posts
    818 Views
    No one has replied
  • Boot Menu: rEFInd Initializes Too Quickly

    Unsolved Windows Problems
    8
    0 Votes
    8 Posts
    2k Views
    R

    @ReinierG said in Boot Menu: rEFInd Initializes Too Quickly:

    @Tom-Elliott said in Boot Menu: rEFInd Initializes Too Quickly:

    Pxe Menu Timeout

    Hey @Tom-Elliott ,

    No, the issue is not that we don’t see a menu. When we start netboot and the main FOG menu opens (where we can deploy an image and access other options), it automatically exits after 3-5 seconds and proceeds to rEFInd, which is not correct.

    I allready see the setting, can i just set the timeout as high as i want without issue’s?

  • import an image to a USB from FOG Image

    Unsolved Windows Problems
    1
    0 Votes
    1 Posts
    789 Views
    No one has replied
  • Queue problems when deploying

    Unsolved FOG Problems
    3
    1 Votes
    3 Posts
    425 Views
    DBailey635D

    @tian I’ve got exactly the same problem. The initial 10 queue items complete, but the next batch won’t start. I have to click the lightning bolt icon in the task list to force it to start. Am running up to date FOG software on a fully patched Ubuntu server.

  • RHEL 8.10 clones fail to boot

    Unsolved Linux Problems
    2
    0 Votes
    2 Posts
    886 Views
    T

    Edit: So, the target PC was not identical after all. It had an optical drive as well. Don’t know why that would change anything. From dracut emergency shell I found that the driver for the SAS controller card (aacraid) was not loaded for some reason. Works fine on other target PCs without the optical drive…

  • FOG on Jetson Orin NX ARM64

    Hardware Compatibility
    2
    0 Votes
    2 Posts
    1k Views
    george1421G

    @Nyeine I’ve got an Orin Nano at home and an AGX at work. I’m not sure you can image them with FOG. TBH I have never tried, so it would be interesting to find out.

    One comment before I get too deep into this, if you use for your dhcp server either WIndows 2016 or later or linux as your dhcp server, you can setup profiles with your dhcp server to automatically send the right ipxe boot loader based on the pxe booting computer. You won’t need to mess with the ipxe.efi files like you have. You can surely continue to do it that way, I just wanted to let you know there might be an easier way to go about it.

    So you are able to pxe boot into the iPXE boot loader, as soon as you pick a menu option that is where the wheels come off, so to say. Looking at the screen shot the process is failing at the handoff between ipxe and FOS Linux (arm_Image+arm_init). Its hard to tell if its ipxe or fos linux at fault.

    I have a process to create a debug usb image for x64, but I haven’t tried to create one for arm. In theory if you have a working Jetson Orin running ubuntu you should be able to follow this to create a FOS linux usb boot image: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image In your case you don’t want to use bzImage and init.xy but use the arm_Imag… (to replace bzImage) and arm_init (to replace init.xz). The idea here is to see if you can select register from the grub menu to get FOS Linux to boot on the jetson nx. If it can then the issue is with ipxe. If it doesn’t hopefully you can debug with the usb boot image.

    You may need to build a custom linux kernel for the Jetson. Just for reference https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/Kernel/KernelCustomization.html

  • Always Boot into PXE – Stuck in Boot Loop with FOG

    Unsolved General Problems
    1
    0 Votes
    1 Posts
    698 Views
    No one has replied
  • Error when capturing image. (Operation not permitted)

    Solved Windows Problems
    3
    0 Votes
    3 Posts
    1k Views
    R

    Hey @Tom-Elliott
    I tried the powercfg command and that fixed the issue, i think the device was not shutdown fully, we got it working again.
    Thanks!

  • Kernel Panic - Couldn't find valid RAM disk image

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    217 Views
    No one has replied
  • Capture : Update Database Failed but :

    Solved FOG Problems
    5
    0 Votes
    5 Posts
    497 Views
    G

    Finally , @Tom-Elliott

    Reinstallation of fog solved the problem . I think the issue was linked to the fogproject account. This issue can be closed.

  • Windows 11 problems when deploying

    Unsolved FOG Problems
    2
    0 Votes
    2 Posts
    491 Views
    Tom ElliottT

    @infotech_22 Generally speaking, if you do setupcomplete.com, you should completely disable the FOGService as re-enable it as the final step of the setupcomplete.com script.

    The reason:

    FOGService will attempt to start up and perform its actions alongside anything else that’s occurring. Generally, when the system is setup and running just fine, things are okay because there’s no interactions, but when you pair it with the OOBE configuration stuff, where it could be changing ini’s and Registry thigns, then the FOG Client is saying “Hey restart to change the name and join the domain” or “Hey restart because I completed installing this Snapin” or whatever else may be going on, it can leave your machine in an unknown and cause issues.

    This isn’t something we’re able to fix in a codified manner unfortunately and we have given instructions many times to allow FOG Client while in OOBE state.

    https://wiki.fogproject.org/wiki/index.php/FOG_Client#:~:text=If you plan to use,the image deployment is complete.

    I don’t know if this is in the more modern Documentation, but it is in the original documentation as well.