• FOG 1.6 – Dependencies between Software Management and Snapins?

    Unsolved
    6
    0 Votes
    6 Posts
    54 Views
    Tom ElliottT

    @lperoma Run before software is ready to test.

    Agent: FOG Agent v0.1.27 is released. It runs snapins marked Run before software first, then the software set, then the other snapins. Server: the Run before software checkbox is going into dev-branch now. You find it on the snapin’s General tab, under Snapin Arguments Hidden. It reaches stable with the December 11 release.

    For your VM test before then:

    Put the test server on dev-branch. Get the VM on v0.1.27. Set its Agent Update Ring to 0, or set its Desired Agent Version to 0.1.27. On the activation snapin, turn on Run before software, and queue it with the Avast package assigned.

    What you should see in the agent log on that check-in:

    the activation snapin’s result first; then the software lines, Avast included; then any other snapins.

    If the activation snapin comes back as a retry, the agent holds the software until the next check-in, so Avast does not install ahead of it.

    Two things to know:

    An agent older than v0.1.27 ignores the flag and still runs the snapin after the software. So check the agent version before you judge the result. If you import snapins from a CSV with no header row, the new column shifts the columns after Snapin Arguments Hidden. An export from the UI has a header row and is not affected.
  • Fog 1.6.0.14 Master Storage Node not handing off to Slave Storage Nodes

    Solved
    29
    0 Votes
    29 Posts
    420 Views
    F

    I set my Master Storage Node and 2 Slave Nodes to 3 clients each. I then imaged 9 computers and everything went smoothly. each Node was imaging 3 clients. This was on Fog Dev 1.6.0.195

  • FOG Agent on new image PC not communicating with server

    Solved
    3
    0 Votes
    3 Posts
    63 Views
    rogalskijR

    @Tom-Elliott I believe that took care of it. As always thank you so much for this product and the wonderful support!

  • 1.6.0.158 unable to approve agent

    Solved
    12
    0 Votes
    12 Posts
    154 Views
    Tom ElliottT

    @chscduo Glad it works, and thanks for running each check so quickly.

    The fix is in dev-branch, so the next FOG update includes it. The update replaces the helper you installed by hand with the same code, so you have nothing to undo.

  • 0 Votes
    4 Posts
    113 Views
    L

    @Tom-Elliott Thanks!

  • 1.6.0.158 Unable to join machine to he domain and change Hostname

    Solved
    5
    0 Votes
    5 Posts
    80 Views
    Y

    @Tom-Elliott So that was all it took, thank you very much, the issue is resolved.

  • 1.6.0.167 Time wrong in logs

    Solved
    2
    0 Votes
    2 Posts
    70 Views
    Tom ElliottT

    @FlareImp yes, this is expected.

    All times are stored in UTC for consistency now and translated to whatever time is configured (by default) and each user can define their own timezone if they want it.

    https://docs.fogproject.org/en/latest/management/web/unadjusted-timestamps/

  • Fog 1.6.14 Driver Replication Issue

    Solved
    17
    0 Votes
    17 Posts
    476 Views
    F

    @Tom-Elliott now it is showing

    [11-13-26 8:30:16 pm] * Starting Image Replication. [11-13-26 8:30:16 pm] * We are group ID: 8. We are group name: Nashport Storage Group [11-13-26 8:30:16 pm] * We are node ID: 13. We are node name: TVNE-Fog [11-13-26 8:30:16 pm] * Attempting to perform Group -> Group image replication.

    Replication seems to be working now. After replication completed I restarted the service and nothing was recopied.

  • 1.6.0.14: Web UI not staying signed in?

    Solved
    4
    0 Votes
    4 Posts
    160 Views
    S

    @Tom-Elliott Thank you once again for the amazing support and turnaround.

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

    Unsolved
    2
    0 Votes
    2 Posts
    134 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

  • FOG 1.5.10 - Problem with AD Join.

    Unsolved
    6
    0 Votes
    6 Posts
    445 Views
    R

    I ran this command on the host, and then restarted the FogService., but my issue might have been slightly different.

    reg add “HKLM\System\CurrentControlSet\Control\Lsa” /v NetJoinLegacyAccountReuse /t REG_DWORD /d 1 /f

    Then it joined to AD with no issues.

    Are those exisiting machines in AD that you re-imaged with FOG, or were they new devices?

    This only happened to us with exisitng machines in AD that we re-imaged and then couldn’t join AD again after.

  • 0 Votes
    7 Posts
    325 Views
    Tom ElliottT

    @Shuttleu Thank you for testing on the HP. That confirms the fix on real firmware.

    The task error after a menu enrollment. This is a FOS bug, not the agent. The menu item runs the enrollment with no task scheduled. When the enrollment finishes, FOS tries to close the task. The server answers “No Active Task found”, and FOS shows an error. The enrollment itself succeeded. The fix is in FOS release 20261106-134043. After a menu run, FOS now says that no task is scheduled and ends normally. The server records the enrollment on the host only when you schedule the task from the web UI.

    FOG Agent. You found the cause. Uninstall keeps C:\ProgramData\FOG on purpose. It holds the machine’s key, its certificate and the trusted CA, so a reinstall keeps the same identity. The reinstall kept the CA of your earlier server, so every connection failed and the token was never used. Agent v0.1.21 fixes this. Setup now checks the stored trust against the server. If it no longer verifies, setup settles trust again like a first install, and the host enrolls again with the token. Until you install v0.1.21, deleting C:\ProgramData\FOG before the reinstall is the right workaround.

    Your server certificate comes from your company CA, which Windows already trusts. So no fingerprint is needed, as the probe said. Leave CAFINGERPRINT out on these machines.

  • IPXE boot no longer works after upgrade to 1.6. Error code 0216eb

    Unsolved
    12
    0 Votes
    12 Posts
    514 Views
    T

    @Tom-Elliott

    Hopefully I’ll have the answer to that question within the next two weeks!

  • FOG Server : Certificate validation failed

    Solved
    12
    0 Votes
    12 Posts
    457 Views
    Tom ElliottT

    @fgaudin Good to hear it works.

    UEFI alone does not need secureboot=1. The setting is only for computers that have Secure Boot turned on in the firmware. With secureboot=0, FOG does not sign its boot files, and a computer with Secure Boot on refuses to boot them.

    If Secure Boot is off on your computers, keep secureboot='0'. If Secure Boot is on, set secureboot='1' and run ./installfog.sh -y. Do not use -C or -K. Each computer then enrolls the FOG key one time at its first PXE boot.

    Install sudo before you set it to 1. The Secure Boot signing helper needs /etc/sudoers.d.

  • 0 Votes
    6 Posts
    269 Views
    F

    @Tom-Elliott All is working now

    Hey Tom, updated to 1.6.0.97 this morning and everything checks out:

    Exports: migrated to /etc/exports.d/fog.exports, and my kubuntu.exports came through untouched.
    SSH keys: fog@fogger key landed in authorized_keys, works on my custom port. Pulled the Match password exception, so the box is key-only again.
    Dashboard: 1.5 history is back, and the Nov 3 runs are on Nov 3 now.
    Capture: new capture shows local time, no asterisk, and moved out of /images/dev over the key with no errors in the log.
    Ports: FOG_SSH_PORT now shows up under FOG Settings → General Settings with my 2416, and the per-node fields are blank, so it falls back to that.

    Seriously impressive turnaround. Thanks for taking the reports seriously and running with them!

  • 0 Votes
    7 Posts
    308 Views
    F

    @Tom-Elliott Hey Tom, updated to 1.6.0.97 this morning and everything checks out:

    Exports: migrated to /etc/exports.d/fog.exports, and my kubuntu.exports came through untouched.
    SSH keys: fog@fogger key landed in authorized_keys, works on my custom port. Pulled the Match password exception, so the box is key-only again.
    Dashboard: 1.5 history is back, and the Nov 3 runs are on Nov 3 now.
    Capture: new capture shows local time, no asterisk, and moved out of /images/dev over the key with no errors in the log.
    Ports: FOG_SSH_PORT now shows up under FOG Settings → General Settings with my port, and the per-node fields are blank, so it falls back to that.

    Seriously impressive turnaround. Thanks for taking the reports seriously and running with them!

  • Fog 1.6 Multiple Sites, Location not working as intended

    Solved
    12
    0 Votes
    12 Posts
    501 Views
    F

    @Tom-Elliott All good! Thank you and keep up the awesome work!

  • LDAP broken since upgrade to 1.6

    Solved
    9
    0 Votes
    9 Posts
    341 Views
    Tom ElliottT

    @rogalskij Glad to be of help and your finding did notice an issue that was also addressed on the dev-branch so thank you!

  • "Detected a web certificate managed outside FOG"

    Solved
    3
    0 Votes
    3 Posts
    167 Views
    R

    @Tom-Elliott As always, thanks for the answer and quick fix 😊

  • [1.6.0-beta.5547] Uploading Snapin fails with 500

    Solved
    4
    0 Votes
    4 Posts
    534 Views
    W

    @Tom-Elliott Thanks fo the quick reply!
    I did rerun the installer today and it seems to be working now, thanks a lot for the quick feedback and fix!

27

Online

12.8k

Users

17.7k

Topics

157.5k

Posts