• 0 Votes
    1 Posts
    17 Views
    No one has replied
  • Windows 11 | 65x HP Z2 Tower G1i | UPDATE -

    Unsolved FOG Problems
    37
    0 Votes
    37 Posts
    2k Views
    Tom ElliottT

    @kratkale Please update the latest dev-branch. Yes I pushed something that had broken this, and then when it was brought to my attention we fixed the problem. To my knowledge this is working again.

    As for the actual snapin upload, I’m not aware of any issues there so you may need to look at your username/password for the storage node.

    I suspect there’s a special character that got encoded incorrectly, though I’m not 100% sure. This (too) could be a problem we introduced trying to fix a bunch of XSS issues (for security reasons) but you might be able to more simply fix this by just setting the value on the username/password out of the storage node’s fogsettings username/password inforrmation.

  • Error in creating host

    Solved FOG Problems
    4
    0 Votes
    4 Posts
    41 Views
    I

    Works well ! 😊

  • Error in sending inventory

    Solved FOG Problems
    4
    0 Votes
    4 Posts
    34 Views
    I

    Works well ! 😁

  • Script for a backup ?

    General Problems
    9
    0 Votes
    9 Posts
    2k Views
    Tom ElliottT

    @Bristow-0 You will need to upgrade to either dev-branch or wait until later today/tomorrow and update to stable. I backported this into the dev-branch as well the working-1.6 branch for consistency and ease.

  • FOG Secure Boot with Shim

    Tutorials
    13
    2 Votes
    13 Posts
    5k Views
    K

    @Florent Hi Florent,

    I actually have been meaning to look into this some more, but the likely answer is no, or at least, not entirely. The way that support works is, you download a signed iPXE 2.0 binary from iPXE and a copy of their signed shim. That shim is signed with the Microsoft keys and trusts the iPXE signing keys. What this means in practical terms is, all the steps above would still need to occur, it’s just that the signing of the iPXE binary is managed by iPXE, and you don’t need to enroll a key to boot iPXE.

    That said, I would imagine this only covers you for booting iPXE, any chainloaded binaries would still need to be signed either with Microsoft’s key or a MOK key you’ve enrolled on the machine. In FOG’s case this means the FOS kernel has to be signed and trusted on the system, in addition to any other binaries (for example memtest, refind) you plan to boot via FOG.

    The other likely blocker is the build itself. Naturally, only iPXE can sign binaries that the iPXE Shim will support. Currently the FOG installer actually builds a slightly modified iPXE binary from source. While I’m unsure if these are all that different from the pre-built binaries from 2.0 in terms of support and functionality, it would at the very least need to be changed to instead pull the iPXE 2.0 binaries.

    I don’t think any of these are particularly hard to overcome or deal with though. The bottom line is, 2.0 makes it easier, but only to a point. To get real proper Secure Boot support in FOG, they’ll likely need to generate their own signing keys, and start signing at least the FOS kernels (if not iPXE itself) and update FOG to include shim support somehow.

    That said, for basic support, I doubt they would need to go the full mile and get a Microsoft approved signing key, I think distributing a certificate/key you can enroll via MokManager and using a pre-existing signed shim (like the iPXE provided one) would more than suffice for most usecases. I’m not sure how difficult it would actually be to implement any of this into FOG, that’s a question for someone who knows PHP and is more familiar with the FOG codebase than I.

    Sorry if that’s a bit long winded, it’s not an easy topic to distill. Hope that helps though.

  • HP Z2 G1i Workstation failing to PXE

    Unsolved FOG Problems
    3
    0 Votes
    3 Posts
    791 Views
    D

    update the kernals on fog server / nodes

  • linux client on runit

    Solved Linux Problems
    2
    0 Votes
    2 Posts
    100 Views
    P

    seems to work when copying the directory from another host over to /opt/fog-service and creating a runit file /etc/sv/fog-service/run with content

    #!/bin/sh exec 2>&1 echo "Starting FOG Client..." exec mono-service /opt/fog-client/FOGService.exe -d /opt/fog-service -l /opt/fog-service/service.lock
  • Basics for WinPE PXE boot using fog

    Tutorials
    2
    3 Votes
    2 Posts
    3k Views
    R

    Hi,
    I know this is a bit old, but I found it when I was searching for an answer to the following question:

    I have prepared USB bootable image based in WinPE. I use it to boot from USB. I have this image in iso file and I use it to place it on USB with rufus software.

    I wonder if I can use this tutorial of yours in exactly same way only to use my custom iso image instead of your mentioned WinPE.

    I know this may be trivial question and I may just try it, but I am really only beginner in WinPE and fog project.

    Thank you for your kind answer.
    -r-

  • Snapin Log showing warning

    Solved FOG Problems
    5
    0 Votes
    5 Posts
    145 Views
    C

    Hello @Tom-Elliott

    Sorry for the delay 😞

    I checked what you told me to do. It appears I have a file that I didn’t check : /etc/php/8.4/fpm/pool.d/www.conf
    I set display_error=off and now I don’t have all those warnings.

    Thank you for your help.

    This is perfect 🙂

  • INTEL VROC RAID 1 - HELP PLS

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    84 Views
    No one has replied
  • Detected Hardware unit hang

    Unsolved FOG Problems
    5
    0 Votes
    5 Posts
    3k Views
    R

    @GregorS I have 3 Dell Models that are also doing this, but I will try the change to DHCP Boot file.

    I will post back when I have an update.

    Thanks!

  • Filters duplicating from table to others

    Unsolved FOG Problems
    3
    0 Votes
    3 Posts
    739 Views
    I

    So I am alone ?

  • SnapinClient ERROR: Hash does not match

    Solved Windows Problems
    10
    0 Votes
    10 Posts
    283 Views
    G

    @Tom-Elliott

    I pulled latest dev-branch version 1.5.10.1856, re-run installer and snapins are working again.

    Thank you very much for help.

  • Hosts detail page is not loading CSS

    Solved FOG Problems
    4
    0 Votes
    4 Posts
    259 Views
    neodawgN

    We can mark this closed. Turns out it was a old/bad snapin package on the old server. I set up Fog with a new DB and everything worked fine. Once I removed the snapins and exported and imported the DB again it all worked as expected.

    Thanks for the help.

  • Windows on ARM

    Hardware Compatibility
    43
    0 Votes
    43 Posts
    19k Views
    M

    @Tom-Elliott just bumping this. Is there anything I can do to help? I have some experience building Linux kernels from a few years ago.

  • Imaging system with two drives - Boot Error

    Unsolved FOG Problems
    2
    0 Votes
    2 Posts
    128 Views
    K

    @vanfifty1
    I have some simelar Problems maby read the post
    https://forums.fogproject.org/topic/18157/windows-11-65x-hp-z2-tower-g1i-update/2
    My problem is/was that Fog uses sometimes the wrong nvme …

  • Trying to USB Boot FOG client on MBP 2015

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    104 Views
    No one has replied
  • Web UI problem

    Unsolved FOG Problems
    3
    0 Votes
    3 Posts
    162 Views
    G

    @Tom-Elliott
    This is resolved in latest dev-branch version: 1.5.10.1853
    Thanks.

  • Blank web page after updating to 1.5.10

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    109 Views
    No one has replied