For example, if you want remote control to be available on all but a few devices, configure the default client settings to allow remote control and then configure custom client settings that do not allow remote control.
Deploy these custom client settings to a collection that contains the computers that will not use remote control.
Built-in and custom collections appear in the User Collections and Device Collections nodes in the Assets and Compliance workspace in the Configuration Manager console.
For more information about how to use collections with power management, see Power Management in Configuration Manager.
Collections can be used with role-based administration to control which groups of users have access to various functionality in the Configuration Manager console.
Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2 Collections that are based on direct-membership rules need to be manually updated by the Configuration Manager administrator (in the same manner as each resource was originally added to the collection when it was created).
Collections that are query-based, however, can be automatically updated by Configuration Manager.
Most management tasks rely on using one or more collections.
For example, before you can deploy software updates to devices, you must identify a collection for the deployment of software updates.
Although you can use the built-in collection of All Systems, using this collection for management tasks is not a best practice.
In all but a testing environment, you will typically benefit from creating your own custom collections to more specifically identify the devices or users to manage.
For more information about how configure collections for role-based administration, see the Planning for Role-Based Administration section in the Planning for Security in Configuration Manager topic.
Maintenance windows provide a means by which administrative users can define a time period when various Configuration Manager operations can be carried out on members of a device collection.
For example, you could create a collection of all computers that reside in the ‘London Headquarters’ Active Directory Organizational Unit (OU).