TaskSets can be assigned to users and computers by specifying a Scope for these objects.
The contents of the scope, the criteria, will determine whether or not the Taskset should be invoked for the current situation at runtime.
As TaskSets are also the runtime objects for Applications and Printers, these Scopes will determine whether or not a Printer or an Application will be available.
Next to TaskSets some other objects use Scopes as well:
- Configuration Settings
As the Criteria in the Scope are evaluated in real-time these Scopes are dynamic, which means that a user might be assigned an application here and now, but not necessarily somewhere else tomorrow.
A Scope can therefore be considered a dynamic group definition of which a user or computer will be a member (or not) based on the evaluation of its Criteria.
Scopes are automatically created when adding Criteria to an object.
Such a Scope is dedicated to this object and only exists for this object.
Changes made to Criteria in Local Scopes will not affect other objects.
Rather than specifying a certain Scope over and over again for several Scense objects, the administrator can create Global Scopes which are managed globally in the ‘Scopes’ system folder.
The administrator can create ‘stand-alone’ Scopes with Criteria that can be assigned to more than one object. Changes to a Global Scope will immediately affect all objects that use them.
The administrator can link an object to a Global Scope using the ‘Advanced’ button on the Scope property page.