• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. SquidgyHobo
    3. Topics
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 9
    • Groups 0

    Topics

    • S

      Join Domain after deploy is not checked on newly registered hosts

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      2
      0 Votes
      2 Posts
      383 Views
      george1421G

      Can you tell me (sorry a bit too lazy to look) when you quick register a host, does it ask you for a group assignment? If so you could use the persistent group (hack) to create a host template with all of the settings you want by default for new hosts, then when you add the system to a template group, those settings will be copied to the newly registered host.

      The other way I can think how to do this is create a mysql database trigger, to when a new host is added to the hosts table in mysql, the check box is checked in the database. I’m not really in favor of the second part, but it will work if all other choices fail. The template host/persistent group plugin it a bit cleaner approach.

    • S

      FOG 1.4.4 Capone problme

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      12
      0 Votes
      12 Posts
      2k Views
      Tom ElliottT

      @SquidgyHobo where the wiki shows git checkout dev-branch you would do git checkout working.

      Master branch is current stable version 1.4.4
      Dev-branch is latest trunk, sometimes it’s the same as master but typically containing rc versions.
      Working branch is where I’m almost always “working” on the latest stuff whatever that might entail.

    • S

      Blank management page and no fog database created on Red Hat

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      4
      0 Votes
      4 Posts
      1k Views
      george1421G

      @SquidgyHobo RHEL 5.3 isn’t supported by FOG.

      RHEL 5.3 also it went EOL from Redhat Jan 2011. I would not even use that in my environment since it is susceptible to a handful of nasty and well publicized vulnerabilities.

      RHEL / Centos 6.5+ and 7.x are currently supported, as well as the Debian variants.

    • 1 / 1