Routine Active Directory management often requires performing same administrative tasks at regular intervals. Using Scheduled Tasks you can schedule periodic Active Directory operations to run automatically in the unattended mode. With their help you can automate such tasks as notifying users about their password or account expiration, handling inactive user or computer accounts, managing AD group membership and OU maintenance, synchronizing Active Directory with external data sources, and many others.
A Scheduled Task is executed on all objects of the relevant type included in its activity scope. The activity scope can include whole domains, members of specific groups and Business Units, children of Organizational Units, or individual objects. For example, if the activity scope of a Scheduled Task for users includes the OU 'Sales Staff' only, this Task will be executed on every user under this OU.
Objects can be included or excluded from the activity scope. This is useful, when you need a Scheduled Task to be executed on a specific OU, but for some objects under this OU. In this case, you just need to include the OU in the activity scope and exclude the objects, on which the Scheduled Task must not be executed.
Every Scheduled Task contains the actions it will execute and conditions that must be met for actions execution. For example, a Scheduled Task can contain such actions as move object, add object to group, update object, etc. And the conditions for their execution can be: if the object is located in a specific location, if the account is enabled or disabled, if the user's department is Sales, etc. For the complete list of possible actions and conditions, see Actions and Conditions.
To control the execution of Scheduled Tasks, approval requests can be sent for any action. When an action that requires approval is initiated, an approval request is sent to the users specified as approvers for this action. The action is not executed until an approver allows its execution. For more information on approval requests, see Approvals and Requests.
| To avoid sending repeating approval requests for objects not relevant for the Scheduled Task actions, you can exclude specific objects from the activity scope of the Scheduled Task. |
All operations performed by a Scheduled Task are displayed in its Activity History. With its help, you can check how a Scheduled Task is executed, when, on what objects, ect.
If you do not want a Scheduled Task to be effective for a certain period of time, you can disable it. The 
icon indicates disabled
Scheduled Tasks.
When you create a Scheduled Task, it runs on the service where you create it. To avoid situations when multiple Scheduled Tasks are executed on one Adaxes service at the same time and balance the load, you can assign Scheduled Tasks to different services manually.