• Nice to have

    3
    0 Votes
    3 Posts
    2k Views
    O

    Hello
    We primarily use Fog for software management on the clients
    This works relatively well, even if it wasn’t intended for that purpose.
    We would still like to keep this as this function is very convenient for us.

    You can certainly add the version number to the name.
    I actually wanted to avoid this because I can’t guarantee that there might be problems here in Fog if the name of an assigned packet changes all of a sudden.

    To the node status
    I currently know that you can read this in the logs

    One field in the dashboard for each storage node would be enough for me to operate it
    what the status is

    Example
    synchronization
    Ready
    Error

    If there are errors, you can read them in the log.

    Thank you for the great work on this project

  • Use a serial console

    7
    0 Votes
    7 Posts
    3k Views
    george1421G

    @rpeterson ok, so the pcbios is sending characters to the serial port and CONSOLE_SERIAL is also sending characters to the serial port. This is what I’m guessing because of this post: https://superuser.com/questions/1358359/putty-serial-port-access-to-rs-232-console-showing-double-character-display-with

    So I have to ask the question. Have you tested the fog stock ipxe boot loader? If PCBIOS is redirecting what would go to the screen out the serial port then that is all you should need. Now once you get the fog ipxe menu to display correctly, when you pick a menu item on the ipxe menu and bzImage and init.xz are loaded that is where the kernel parameters console=ttyS0,115200n8 come into play. You don’t need to edit bootmenu.class… just go into FOG Configuration->FOG Settings->Kernel Parameters and add in that line. It will be added to every computer that pxe boots into fog.

  • Authentication options for image uploads

    1
    0 Votes
    1 Posts
    354 Views
    No one has replied
  • 1 Votes
    30 Posts
    13k Views
    george1421G

    @hancocza Its a bit complicated, but the short answer is that the inits will need to be updated to support NFSv4 then its needs to be paired with the current kernel. You will have this issue with usb booting or booting via PXE. The default inits don’t support nfsv4. The answer is they can be fixed.

    @Developers can we enable the inits to be compiled with NFSv4 support but not update the scripts to include NFSv4 support. This way the FOG Admin can just unpack, add the settings and repack the inits because everything would be already compiled in. Or simply include my hack below to enable a kernel variable to enable nfsv4 and only have one master inits package.

  • USB boot without IPXE

    2
    0 Votes
    2 Posts
    629 Views
    george1421G

    @dashwell Are you using the “usb boot easy way” to get into the iPXE menu? iPXE should support multiple network adapters out of the box. It should support 2 or maybe 3 external adapters and will try them in order.

    There is a different way to usb boot directly into FOS Linux (the engine that moves data on the client). The tutorial is covered here: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image read the entire article top to bottom. Also check the FOG Form chat for a few more hints.

  • Generate barcode for host from inventory

    13
    0 Votes
    13 Posts
    4k Views
    D

    @Sebastian-Roth I wanted to put my 2 cents on generating barcodes for individual hosts. It’s definitely possible to add a barcode feature for each host, which could be printed using a Zebra label maker and stuck on the PCs.

  • Snapins public storage

    1
    0 Votes
    1 Posts
    253 Views
    No one has replied
  • 0 Votes
    3 Posts
    760 Views
    george1421G

    @tcthorne If you want to switch over to the 1.5.9 dev branch I can give you instructions. That will take your fog build to 1.5.9.115 or later. The dev branch also contains fixes for single disk resizable function with windows 20H2 and later OS’

  • Secure Boot Support for Windows 11

    6
    0 Votes
    6 Posts
    5k Views
    D

    @jj-fullmer said in Secure Boot Support for Windows 11:
    “As long as your CPU supports TPM 1.2 you can do a clean install of windows 11, you just can’t in-place upgrade (without a registry change).”

    Is it possible to share the registry change? Unless something even better has changed, I am thinking of in-place windows 10 21H2 to 11 in a dual-boot ubuntu environment. I figure this would stop me from having to reinstall Ubuntu (or grub repair).

  • Popularity Contest

    50
    2 Votes
    50 Posts
    17k Views
    Wayne WorkmanW

    @Sebastian-Roth as well as all the others ( @developers @moderators @testers )

    Would we want anything besides kernel information? I had some ideas:

    Number of hosts
    Number of images
    Number of each type of image
    Number of systems imaged in the last 7 days
    Number of storage nodes
    Number of storage groups
    Other things?

    It’s been said before, but will say it again. This is all anonymous data. There is no way to correlate this data back to any system.

    It just provides us insight (and possibly bragging rights). imagine us being able to say “FOG imaged a bazillion systems last week, we’re proud of that” or maybe “FOG assists with managing a quadrillion million computer systems every day”. I’m being funny with the imaginary figures here, but you get the idea. It’d be nice to make statements like that on the home page fogproject.org

  • Adjusting last partition Windows 10/11

    4
    0 Votes
    4 Posts
    906 Views
    S

    @dashwell The files are init.xz (64 bit CPU) and init_32.xz (32 bit CPU). Download those and move them into /var/www/html/fog/service/ipxe in your FOG server. Rename the existing files instead of overwriting them.

  • Scripted process to remove a file/folder before imaging

    2
    0 Votes
    2 Posts
    421 Views
    george1421G

    @dashwell Normally you would delete the file before capture in our source OS. But I know sometimes you just need to edit / remove one file from the target system.

    You can do what you want with a FOG post install script. I have a tutorial on how to inject drivers into a target windows system that you can use as the basis. Start by reading this: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

    The only scripts you will need to start with is fog.custominstall

    In this section of the code you will need to change it for your purposes.

    debugPause . ${postdownpath}fog.copydrivers # . ${postdownpath}fog.updateunattend umount /ntfs ;;

    Lets change it to

    debugPause . ${postdownpath}fog.nukemyfile # . ${postdownpath}fog.updateunattend umount /ntfs ;;

    Now that above script will connect the C drive on the target computer disk to the /ntfs directory. The thing you have to remember is the FOG Post install script runs under linux and not a windows batch file. So there are some pain points you must remember. The first is the directory paths are forward slash ( / ) and not a backslash ( \ ). Second linux is case sensitive. So lets say you want to edit the unattend.xml file you would reference that file as /ntfs/Windows/Panther/Unattend.xml Note the path and case matching.

    So now you will need to create a file called fog.nukemyfile in the /images/postdownloadscripts directory on the fog server. Hint: If you first create the file on a windows box use notepad++ not windows notepad. You will save some headaches later.

    In that fog.nukemyfile file put the following.

    #!/bin/bash rm "/ntfs/apps/broadcom/config.ini"

    Assuming you wanted to remove the config.ini file in c:\apps\broadcom directory.

    The last bit from the tutorial you will need to hook the fog.custominstall script into the fog.postdownload script as mentioned.

  • Persistent Groups - Snapins added to host but not deployed

    39
    0 Votes
    39 Posts
    14k Views
    A

    Hello,

    I am using fog to manage a data center deployment consisting of over 1000 servers.

    I am replying here as the UX feedback provided by @GeorgeBells here perfectly sums up issues I’ve been having as well.

    If a feature request / ‘fix’ per details referenced above is NOT possible or planned, then I sincerely urge the dev team to consider allowing users to assign Snapins directly to images.

    All of my equipment is of a similar spec, and the image I flash to them contains pre-configured FOG client as well as auto-setup scripts to configure UUID-based values on first boot.
    All of my “snapins” are entirely image-specific by design.

    I would like to quick register all new equipment, immediately flash the same specific image, and then deploy the same snapin every time.

  • Persistent groups and snapin deployment

    1
    0 Votes
    1 Posts
    269 Views
    No one has replied
  • Ability to tidy images up

    3
    0 Votes
    3 Posts
    623 Views
    M

    Yes, this is true, I could do that but it won’t change anything the way the “Image Managament” page looks. I was thinking about the ability to browse through folders and display the content rather than displaying all the images. (I know there is the searching field but it’s not exactly the same)
    We could imagine a tree on the left side of the panel and browse through categories like an explorer if you prefer.

    Well, that was just an idea and the way it works at the moment suits my needs but I thought it could bring a little something.

    Cheers.

  • Web interface SSL

    Solved
    16
    0 Votes
    16 Posts
    4k Views
    G

    @astrugatch We are booting and imaging over the internet.

  • 0 Votes
    3 Posts
    610 Views
    F

    @junkhacker

    Thank you

  • Torrent cast without tracker server

    1
    0 Votes
    1 Posts
    532 Views
    No one has replied
  • Feature Request for FOG 1.6.X - Add image integrity verification check

    8
    0 Votes
    8 Posts
    1k Views
    J

    @george1421

    By and large I agree with you about the hash algorithm being irrelevant, however, some entities have requirements for minimum acceptable hashing for such kind of verification. I think a baseline of a choice between md5 and shasum baseline is fine, especially while development of the feature is ongoing (md5 is still widely used in forensics), however that will not always be the case and building support in for additional options might be better. The time cost involved is something the end user should accept when they select the additional complexity.

    Just as a test, I timed sha 512 on my Windows 10 image. Here is the results:

    d0715180-198f-4f02-93d6-a638d573b1e9-image.png

    Took about 2m 8s for 8 GB give or take. So the wait isn’t terrible at higher algorithm complexity. This test was done with a two virtual processor VM on a server with a bunch of other vms running.

    Interestingly enough, the shasum utility on ubuntu can compare hashes to a text file for verification.

    4e873e2c-fd44-4f6e-b026-0462cccbd356-image.png

    Also, I don’t think the hash need be taken inline with the imaging process, but be done post imaging, either on demand, or run in background automatically before image is made available for distribution.

    Thoughts?

  • Centos 8/CentosStream PHP module stream

    2
    0 Votes
    2 Posts
    625 Views
    S

    @Quazz While I do understand the good intend in this I think it’s very hard to maintain. We see enough issues with trying to make it work in the different distros. Adding the Stream PHP versions will be a nightmare I reckon.

161

Online

12.4k

Users

17.4k

Topics

155.9k

Posts