Auto select correct collector(s)

I agree - alternatively could the new host inherit the Collector assigned to the group as it does with properties.rnSo if you move the host from one group to another the collector will change as will the properties.

I could see an issue with inheritance, if you have hosts that are associated with multiple groups.rnThink of it this way, lets say that you monitor two customers, each with two servers, one production and one test. So you build four groups for organizational purposes, one for each customer, and one for the production servers and one for the test servers. You use this production/test grouping because you set daily SDT on the test servers to not alert after hours.rnIn this case, lets use customer 1 production server. It would be in the customer 1 group and also the production group. So when you have a server that appears in two groups, how do you assign the collector? It makes sense for the customer 1 folder, but not the production folder, which has two servers being monitored by two completely independent collectors.rnSo while I like the idea of recommending a collector when you add a host, I dont think that you could force collectors based upon group membership.rnLastly, in large environments with multiple sets of primary/secondary collectors, I would expect those hosts to all appear in a single group at some point, yet youd never cross those collectors up.rnHope these exceptions makes some sense.

I agree with the original poster. There are other issues with exposing collectors that contain names of our other MSP customers. If the Collector or Collectors is associated with a group, then only those Collectors should be visible when adding Devices to that Group.

I agree with the original poster. There are other issues with exposing collectors that contain names of our other MSP customers. If the Collector or Collectors is associated with a group, then only those Collectors should be visible when adding Devices to that Group.