• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Global Services after upgrade?

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    5
    1.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      Jarett LeBlang
      last edited by

      Have been trying to get my Fog server to do the domain join but i noticed that anything that got grandfathered over from .33 doesn’t seem to follow the Global Service settings. I had to go in and check services that are already in the Global Service settings area on a per-machine basis. I’m assuming this isn’t intentional?

      1 Reply Last reply Reply Quote 0
      • N
        naeren
        last edited by

        I’ve noticed this as well, and actually with new hosts added through the web interface too (haven’t tried through pxe).

        1 Reply Last reply Reply Quote 0
        • Tom ElliottT
          Tom Elliott
          last edited by

          [quote=“Jarett LeBlang, post: 27897, member: 4208”]Have been trying to get my Fog server to do the domain join but i noticed that anything that got grandfathered over from .33 doesn’t seem to follow the Global Service settings. I had to go in and check services that are already in the Global Service settings area on a per-machine basis. I’m assuming this isn’t intentional?[/quote]

          This is intentional, sort of, though a freshly registered machine defaults to have all of the services enabled.

          The reason for this is two part.

          First, the global services need to be running for any service category to operate. This we all understand I think.

          Second, the host services need to be enabled on the individual host as well. The reason is for granular control over what systems do what. There may be specific systems that you may NOT want to allow snapins to be installed to.

          In your scenario, if the global option is active, it wouldn’t matter what the individual host was set to. And all hosts that are registered would have all the same level of services enabled. There’d be no way to tell only one or two systems NOT to use those services.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 0
          • J
            Jarett LeBlang
            last edited by

            Ah i thought Global Settings were a general setting for newly registered hosts, so you didn’t have to manually go in and turn settings on. So basically Global Settings turns the module on and then you check what’s needed per host. You might want to think about putting a mechanism in place that lets you turn on the flags when the server is registered by pxe, rather than having to register the machine and then go into the GUI to turn on flags.

            1 Reply Last reply Reply Quote 0
            • Tom ElliottT
              Tom Elliott
              last edited by

              [quote=“Jarett LeBlang, post: 27937, member: 4208”]Ah i thought Global Settings were a general setting for newly registered hosts, so you didn’t have to manually go in and turn settings on. So basically Global Settings turns the module on and then you check what’s needed per host. You might want to think about putting a mechanism in place that lets you turn on the flags when the server is registered by pxe, rather than having to register the machine and then go into the GUI to turn on flags.[/quote]

              That’s already the default action. When a host is registered, it turns on all the flags.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post

              179

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project