Use the Client Task Catalog to create client task objects you can reuse to help manage systems in your network.
The Client Tasks Catalog applies the concept of logical objects to ePO - On-prem client tasks. You can create client task objects for various purposes without the need to assign them immediately. As a result, you can treat these objects as reusable components when assigning and scheduling client tasks.
You create client task assignments to:
Link System Tree groups or tagged systems to a client task.
Schedule the client task to run.
Set stop tasks, randomization, and rerun delays for the client task.
Client tasks can be assigned at any level in the System Tree. Groups and systems lower in the tree inherit client tasks. As with policies and policy assignments, you can break the inheritance for an assigned client task.
Client task objects can be shared across multiple registered ePO - On-prem servers in your environment. When client task objects are set to be shared, each registered server receives a copy after your Share Client Task server task runs. Any changes made to the task are updated each time it runs. When a client task object is shared, only the owner of the object can modify its settings.
Note
Administrators on the target server that receives a shared task is not an owner for that shared task. None of the users on the target server is owner for any shared task objects the target receives.