locked
Collection Client Settings RRS feed

  • Question

  • Since the default client settings can be changed at the collection level what happens when a client is in 2 collections which have different settings applied?

    Say the client is in one collection where software inventory is run once a day and in another collection where it is run once a month.  what happens?

    Friday, May 25, 2012 4:18 PM

Answers

  • All Configuration Manager clients in the hierarchy use the Default Client Settings that are automatically created when you install Configuration Manager. However, you can modify the default client settings and you can create custom client settings to override the default client settings for specific users or devices.

    When you create a set of custom client settings, you must assign it to one or more collections for the settings to be applied to the collection members. If you apply multiple sets of custom client settings to the same user or device, you can control the order in which these settings are applied according to the order that you specify. Custom device or user settings with an Order value of 1 are always processed last and will override any other configurations. The Default Client Settings has a permanent order of 10,000, which ensures it is always applied before any custom settings are applied. When there is a conflict of settings, the client setting that was applied last (with the lower order value) overrides any previous settings. You can view the resultant client settings for a user or a device by using the System Center 2012 Configuration Manager reports.


    Nicolai

    • Marked as answer by willbar Friday, May 25, 2012 4:49 PM
    Friday, May 25, 2012 4:43 PM
  • hey Willbar,

    Under client agent settings, each client setting has a priority. So in case of the client being in 2 collections with conflicting settings, the one with the higher priority will take effect.

    Thanks,

    Moiz

    Friday, May 25, 2012 4:44 PM

All replies

  • All Configuration Manager clients in the hierarchy use the Default Client Settings that are automatically created when you install Configuration Manager. However, you can modify the default client settings and you can create custom client settings to override the default client settings for specific users or devices.

    When you create a set of custom client settings, you must assign it to one or more collections for the settings to be applied to the collection members. If you apply multiple sets of custom client settings to the same user or device, you can control the order in which these settings are applied according to the order that you specify. Custom device or user settings with an Order value of 1 are always processed last and will override any other configurations. The Default Client Settings has a permanent order of 10,000, which ensures it is always applied before any custom settings are applied. When there is a conflict of settings, the client setting that was applied last (with the lower order value) overrides any previous settings. You can view the resultant client settings for a user or a device by using the System Center 2012 Configuration Manager reports.


    Nicolai

    • Marked as answer by willbar Friday, May 25, 2012 4:49 PM
    Friday, May 25, 2012 4:43 PM
  • hey Willbar,

    Under client agent settings, each client setting has a priority. So in case of the client being in 2 collections with conflicting settings, the one with the higher priority will take effect.

    Thanks,

    Moiz

    Friday, May 25, 2012 4:44 PM