• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Tom Elliott
    • Profile
    • Following 27
    • Followers 83
    • Topics 140
    • Posts 19,368
    • Groups 0

    Tom Elliott

    @Tom Elliott

    5.1k
    Reputation
    39.0k
    Profile views
    19.4k
    Posts
    83
    Followers
    27
    Following
    Joined
    Last Online

    Tom Elliott Unfollow Follow

    Best posts made by Tom Elliott

    • Gratitudes

      I know I’ve been out of this for a little bit. I check in here or there, but just been extremely busy.

      I don’t want to stop contributing, I just am taking time for myself after my workly duties.

      I have to give a big gratitude and thanks for everyone here trying to help out whether by code, by helping the rest of the community, or documentation.

      @Sebastian-Roth I know you’re busy but you’ve kept the project rolling even with the minimal availability you have. Thank you.
      @george1421 I’m sure you’re busy, but I still see you posting and helping where possible and amenible. Thank you.
      @Wayne-Workman I know you’re helping where you can as well. (Of course I can’t exactly post everybody because I’ve been busy and honestly not keeping up with the forums as much as I probably should.)

      @everyone Thank you. Thank you for still believing in this project. We’re doing the best with what we have. Please understand in we’re lacking, it’s most likely unintentional. I know I’m just busy.

      posted in Announcements
      Tom ElliottT
      Tom Elliott
    • FOG 1.3.5 and Client 0.11.11 Officially Released

      https://news.fogproject.org/fog-1-3-5-and-client-0-11-11-officially-released/

      posted in Announcements
      Tom ElliottT
      Tom Elliott
    • FOG 1.5.0 RC 11

      https://news.fogproject.org/fog-1-5-0-rc-11/

      posted in Announcements
      Tom ElliottT
      Tom Elliott
    • Ubuntu is FOG's enemy

      TLDR; Rerun the fog installer if you have lost “Database Connectivity” to your fog server, or run the ALTER USER syntax shown below.

      So Ubuntu 16, among others I suppose, enable a “security updates” to be applied automatically as a “default” to things. Why, well it makes it simpler to ensure your Ubuntu systems are in compliance and patched for any potential exploits. This causes unknown and unexpected issues.

      I figured it’d be a safe thing to express that there could be problems (as many of you have already experienced) that when these updates go up (with or without your knowledge) it can break functionality in unexpected and inopportune ways.

      The quickest fix is to simply rerun the fog installer which should correct the problem.

      As a note, it seems this problem is specific only when the mysql account is the 'root' user AND the password is blank.

      The “fix” if you must do it manually is to open a terminal and obtain root:
      Super (Windows Key) + T then sudo -i (in most cases).

      From there, open mysql with mysql -u root

      NOTE: MySQL MUST be run with ROOT.

      Run:

      ALTER USER 'root'@'127.0.0.1' IDENTIFIED WITH mysql_native_password BY ''; AND
      ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '';

      It’s okay if one of them fails. This is going to fix Most people’s issues.

      I would highly recommend removing the unattended-upgrades as many of these “sudden” issues came as a security patch ubuntu pushed out. By default Ubuntu typically set’s this for you as enabled and it can cause havoc on you as you (the admin) may not have “done” anything.

      To prevent this problem from happening in the future you could run:

      apt-get -y remove unattended-upgrades (AS Root again).

      posted in Announcements
      Tom ElliottT
      Tom Elliott
    • FOG Activity - Status

      FOG is still actively being developed. It’s not necessarily readily apparent, but we can assure you things are still being worked on. These updates may not be communicated in a way that everybody just knows, but can easily be seen if one were to look at our repository site.

      Between our own schedules and lives, we can get very busy. We try to keep things updated and help out on the forums even during lull periods. This might mean we aren’t pushing an RC or release as frequently. It may mean we’re working on other things for the project, such as can be seen if looking at our github site.

      Our forums are heavily active, and this should point as an indicator to our “status” as well.

      If anybody would like to see an increase in developers donating their time to making this free software, consider donating either with monetary support or by spending personal time to help with development.

      FOG is an open source project - it’s even in the name. It is driven by people donating their time and resources. The releases of FOG revolve around when developers can spare a few hours throughout the week. Sometimes that will mean releases will be further, sometimes that will mean releases will be faster. That’s just the nature of our project, and many other open source projects.

      posted in Announcements
      Tom ElliottT
      Tom Elliott
    • I'm away, but back?

      Hey everybody,

      I know you see me here on occasion from time to time. Life decisions have made it more difficult for me to do things I would normally be doing. Rest assured, I am still around, and while I’m not quite as active as I was in the past, it’s not because I don’t want to be.

      I had to move, and as part of that I have none of my normal development stuff readily available. Part of the move made me not have a laptop, until today.

      I need to setup my dev environment again, so it may take a little bit, but I will be back up.

      posted in Announcements
      Tom ElliottT
      Tom Elliott
    • FOG 1.5.10.41 and forward

      https://news.fogproject.org/fog-1-5-10-41-officially-released/

      While this maybe spur of the moment, it should officially release 1.5.10 with all relevant bug/security fixes encapsulated (among a few other features.)

      This has brought a new methodology of releases in that bug/security releases should be done much more regularly.

      dev-branch, historically, was a place where new development occurred (hence its name) but over the last couple of years or so it’s mainly been a bug/security thing, not really a true development approach.

      This is OKAY, in my head. Why:

      Well we have the master branch which is the ‘baseline’ of a verions. We have the dev-branch, which allows us to work on bugs/security issues. We have the working branches for what will eventually become master. Working is our “dev branch” but keeps proper seperation of things in my opinion.

      Basically:
      master -> basis for dev-branch (which merges into stable on a regular cadence - still being worked out)
      working -> basis of forward development

      So we effectively have:
      production
      staging
      development well seperated.

      THis may mean on the regular automated releases, no announcement or news article will be created, and I think that’s okay.

      Hopefully exciting we have a release after 1.25 years 🙂

      Thank you!

      posted in Announcements
      Tom ElliottT
      Tom Elliott
    • RE: Release plan for FOG

      That’s correct. The main reason fog is constantly moving forward is because the codebase is improved upon. Major bugs tend to be addressed for the next release. We don’t do an LTS because there’s really two main people working on fog in a consistent manor. Those two are @Joe-Schmitt and myself. Debian and Libreoffice have the team too be able to perform such a feat. Their product is Opensource but they have an employment team which can afford them that luxury. FOG has a team but we make no money and as such are required to work full time jobs. We work on FOG in our free time. I’ve had the ability to even work on it from work because we used the software.

      Maintaining many different versions is difficult. And we don’t have a support team. WYSIWYG and I think we’ve done pretty well on support, even if we don’t have the ability to do dedicated support for our product. 1.5 was a major step toward modernizing the GUI. 1.6 will vastly improve on this. It was only recently we kind of came up with a road map on how best to proceed. Of note, 1.5 will be maintained until 1.6 is released. 1.6 is focused on making he GUI much more modern. 1.7 will be focused mostly toward fixing and refactoring the FOG client. 1.8 will focus on making the FOS system more modular and usable. I don’t know yet for 1.9. 2.0 will bridge the gap for our rewrite based on the work from 1.5 and up. While we do plan to try to do backports where possible, it’s much easier to ask people to update to the latest version than it is to try to maintain many different versions with backports in mind. At least for what FOG does.

      I doubt this will appease anybody, but it’s what I think needs to be said. We are working hard and provide support for our product as best we can. The community makes fogs support system, I think, one of the best around. Add to that and you can almost always have a developer working side by side to help and fix issues as they come up, I don’t think it’s unfair to ask users to update to a specific version. Even if there are bugs, we will always try to correct what we can, when we can. (And normally it’s a pretty quick turn around).

      I’m not perfect and I’ll give you that. We don’t even have a test suite to know if things are working as intended. We have to rely on the community and suggestions are great, just understand our answers won’t always be what people want to hear.

      posted in Feature Request
      Tom ElliottT
      Tom Elliott
    • FOG 1.4.0 Officially Released

      https://news.fogproject.org/fog-1-4-0-officially-released/

      posted in Announcements
      Tom ElliottT
      Tom Elliott
    • FOG 1.4.4 Officially Released

      https://news.fogproject.org/fog-1-4-4-officially-released/

      posted in Announcements
      Tom ElliottT
      Tom Elliott

    Latest posts made by Tom Elliott

    • RE: FOG 1.6: Can you install agent in each dual- or multiple-boot operating system or just one OS?

      @DBailey635 This is now available on the Patches update channel (1.6.0.226 or later). No new agent version is needed; any current agent works.

      To use it:

      • Install the agent in each OS as usual.
      • The second OS appears under pending agents as “New OS on a host that already has an agent”. Approve it. If FOG deployed the image within the deploy window, both OSes enroll on their own.
      • For an OS-specific snapin, set “Run on” in the snapin’s settings. A Windows snapin then waits until Windows boots.
      • If the host is set to join a domain, the Windows install does the join. The Linux side is left alone, so the two do not fight over one computer account. The product key also goes only to Windows.

      One limit: two installs of the same OS on one disk share one agent key.

      If you try it, let me know how it goes.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: A reimaged host stays stuck on an old directory join plan ("marker absent; automatic retry refused")

      @lperoma Thanks for the detailed report. Your reading of the code is right. I opened https://github.com/FOGProject/fogproject/pull/2122 to fix both problems.

      On your open question: the first attempt did run. The server stores awaiting_reboot only when the agent reports that Windows accepted the join. Your state also has last_deploy_task_id equal to trigger_task_id (16923), and that is set only when the agent claims the plan. So the join ran after Deploy 16923, and Windows waited for a restart. The disk was reimaged by 16927 before that restart, so the agent never reported “verified”. That also explains why the computer account in AD looked healthy.

      What changes in #2122:

      • A newer Deploy now supersedes an old attempt in started, awaiting_reboot, unknown or failed. Three things must be true: the agent has no marker for the old attempt, a newer Deploy has completed, and the machine booted after that Deploy ended. FOG then drops the old attempt, writes an audit entry, and plans a new join from the new Deploy. If the agent still has the marker, the old attempt stays.
      • The “Clear directory operation review” checkbox no longer marks the newest Deploy as used. It uses up only the cleared attempt’s own Deploy. It also keeps the workgroup flag and the observation. If a newer Deploy exists, the next check-in can plan the join again.
      • With the first change, a reimaged host no longer needs the checkbox, so I did not add a hint to the Active Directory panel.

      On queued tasks and snapins from the previous install: this PR changes only the directory join plans.

      The fix reaches the patches channel after the PR merges. Your hand-written state on test-uefi does no harm.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: FOG 1.6: Can you install agent in each dual- or multiple-boot operating system or just one OS?

      @DBailey635 Not in the current release. The agent identifies the machine by its firmware ID and MACs, so both OSes map to the same FOG host. Today a host holds one agent key. When the second OS enrolls, it waits for approval as a re-bind, and approving it retires the first OS’s key. So for now the agent works in one OS per host, the same as the old client.

      We are adding support for this. Each OS on a host gets its own agent key. Snapins can target an OS, so a Windows snapin waits until Windows boots. The product key and the domain join go only to the Windows install. If you deploy the image with FOG, both OSes enroll on their own within the deploy window. You can follow the work here: https://github.com/FOGProject/fog-agent/issues/53

      I’ll update this thread when it is in a release.

      posted in General
      Tom ElliottT
      Tom Elliott
    • RE: Feature request: a way to handle USB Ethernet adapters shared between many hosts

      @lperoma Thanks for the detail. There are two server fixes and one agent fix.

      Please update instead of copying files this time. This fix changes the database (schema step 465), and the code depends on it. Copied files without that step make enrollment saves fail in a new way. Your server is also now several changes past 1.6.0.158. Run the updater on the patches channel. It installs the files and runs the schema update together. Or wait for the stable release on December 11.

      Server (FOG PRs #2116 and #2118):

      • Agent enrollment now follows the boot rule for a shared adapter. The firmware names one host, and the adapter’s MAC is on another host. If that other host’s stored serial differs from the reported serial, the firmware’s host wins. Your laptop then enrolls as its own host, with the normal “known-host-no-agent” reason.
      • The firmware host must match the serial too. A copied UUID alone never wins over a MAC.
      • Any other disagreement stays an identity conflict. The row is now saved with no host, instead of host 0, so the foreign key no longer refuses it. The agent gets “pending”, not 409, and the row shows in All Pending Agents.
      • For a conflict, All Pending Agents now shows which other host has the MAC. After you remove the cause (for example the stray MAC), the next agent poll binds the request to the right host. Then you approve it. A conflict is never approved automatically, not by a token and not by a recent deploy (#2118 closes this for older agents too).

      Agent (fog-agent PR FOGProject/fog-agent#52): a key whose first request went in without the directory feature cannot add the feature later. That is deliberate on the server. The agent now makes a new key once when the server answers enrollment_upgrade_requires_new_key, and enrolls again. This is in agent v0.1.28. Agents update to it on their own.

      posted in Feature Request
      Tom ElliottT
      Tom Elliott
    • RE: FOG 1.6.0.158 - Multicast error (session has already started with 0 clients)

      @Mikeee89 Good to hear that seconds work. The fix is now merged into dev-branch, so a dev-branch update makes the field take minutes again.

      1.5.10.2518 and 1.5.10.2534 have the same multicast code, so this bug cannot be in one and not the other. 1.5 has no per-session timeout. Its session waits FOG_UDPCAST_MAXWAIT minutes (10 by default).

      Can you post the udp-sender line from /opt/fog/log/multicast.log on the 1.5.10.2534 server? The --max-wait value on the first stream shows what that server waited.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: FOG 1.6.0.158 - Multicast error (session has already started with 0 clients)

      @Mikeee89 Thanks for the log, it shows the cause. The first line of the udp-sender command has --max-wait 10. That value is seconds, not minutes.

      The Session Timeout field on the Multicast page asks for minutes, but FOG stored the number as seconds. So your 10-minute session waited only 10 seconds after it started. After that, the PXE menu treats the session as already started and refuses the join, even with 0 clients connected.

      The fix is in https://github.com/FOGProject/fogproject/pull/2114 and goes to dev-branch.

      Until you update, either of these works on your current install:

      • Enter the timeout in seconds. For 10 minutes, enter 600.
      • Or leave the timeout blank. FOG then uses the global setting FOG_UDPCAST_MAXWAIT (in minutes) and converts it correctly.

      Cancel the stuck session first, then create a new one.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: FOG 1.6 – Dependencies between Software Management and Snapins?

      @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.
      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: FOG 1.6 – Dependencies between Software Management and Snapins?

      @lperoma Thanks for raising this before you hit it. You’re right: with software always first, the Avast package can install before your PowerShell snapin runs.

      Run before software is coming, close to what you asked for. It is a checkbox on the snapin itself, off by default. On a host with both, the agent then works in three steps:

      • snapins marked Run before software, in their queue order;
      • the software set;
      • every other snapin.

      I put the flag on the snapin rather than on each group grant. “This snapin must run before packages” is a fact about the snapin, so you set it once and every group follows it. If a snapin marked this way has not finished, for example a retry, the software waits for it until the next check-in.

      It needs both halves: the next FOG Agent release, and the server change, which reaches stable with the December 11 release. I’ll post here when both are out, and we’d welcome your VM test then.

      One thing to know in the meantime: the old order only protected you when the software and the snapin task arrived in the same check-in. Software is applied as soon as a host joins the group, and a snapin runs only when a task is created. So a host that joined the group earlier already had Avast before the snapin ran.

      Run when a host joins the group is a bigger change. It turns a group’s snapins into something like desired state, so FOG would have to track “this host completed it” and decide when to re-run. That is the job Software Management does for packages, so it needs its own design. I’m not building it now. If you open a GitHub issue with your use case, it has a place to land.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: FOG 1.6 – Dependencies between Software Management and Snapins?

      @Yuuki FOG Agent v0.1.26 is released. It always runs software before snapins, whatever FOG server version you have. So your Sysprep snapin no longer starts before Chocolatey has finished.

      Agents update themselves when FOG Configuration → FOG Agent → update mode is Latest, which is the default from 1.6.0.158. Updates go out in rings (default 0,3,7 days), and a host with no ring uses the last one. So your PCs pick up v0.1.26 on their own within about a week.

      To get it on your build machines now, do one of these on each host:

      • Set Agent Update Ring to 0.
      • Or set Desired Agent Version to 0.1.26.

      If the update mode shows Off, set it to Latest, or use the per-host Desired Agent Version above.

      The server half, the Stop snapins if this fails option on a software entry, is going into dev-branch now. It reaches stable with the next monthly release, on December 11. Until then, the agent gives you the right order, but a failed package does not hold the snapins. So check the host’s Software Status tab before you capture.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott
    • RE: FOG 1.6 – Dependencies between Software Management and Snapins?

      @Yuuki You found a real ordering problem. The FOG Agent runs its modules one at a time, in the order the server sends them, and on 1.6 that order puts snapins before software. So on any check-in that carries both, your Sysprep snapin runs before Chocolatey starts.

      The fix is in progress:

      • Software will always run before snapins. This is fixed in both the server and the agent, so updating either one gets you the order.
      • Each software entry gets a new option, Stop snapins if this fails (off by default). With it on, a failed install holds the host’s snapins. At the next check-in the agent tries the software again, and it runs the snapins only after the install succeeds.
      • Snapins already have Abort snapin sequence on failure on the snapin task. Turn it on when you queue the snapins, so Sysprep does not run after a failed configuration snapin.

      Until the fix reaches you, there are two workarounds:

      • Assign the software first. Wait until the host’s Software Status tab shows every entry as installed or converged. Then queue the snapins.
      • Or install those packages with the Chocolatey snapin templates instead of Software Management. Snapins run in their queue order, so put Sysprep last.

      I will post here when it is in a release.

      posted in FOG Problems
      Tom ElliottT
      Tom Elliott