Global Services after upgrade?



  • 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?


  • Senior Developer

    [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.



  • 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.


  • Senior Developer

    [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.



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


Log in to reply
 

468
Online

39.3k
Users

11.0k
Topics

104.6k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.