Refer to JOBS in Security Level Details - Permissions
Jobs > New Job
Site lists > select one or more sites > Schedule a job
Device lists > select one or more devices > Schedule a job
Device Summary > Actions > Schedule a job
Device Audit > Actions > Schedule a job
Account > Monitor > Monitor Alerts radio button > select one or more alerts > Schedule a job
Sites > select a site > Monitor > select one or more alerts > Schedule a job
Components > select a component > Schedule a job
Schedule and Run Jobs
Learn how to run jobs at a scheduled time, immediately through a quick job, or as a user task directly from the Agent Browser.
About the job scheduler
A scheduled job allows you to run multiple components immediately or at a scheduled time. When a job is scheduled, the Web Portal signals the targeted devices that a job needs to be run. The Agent will download the job to the local hard drive, unpack the package into its component parts, and run the script. This process takes place in the system session where the Datto RMM Agent runs. If you want a job to run in the user session (for example to copy a shortcut to the desktop), you can set it up when scheduling the job. Refer to Execution.
Jobs can be scheduled for individual devices, sites, filters or groups. You cannot run a job at the Account level.
A quick job allows you to immediately deploy one component without having to schedule the job. Refer to Quick jobs.
- Go to Jobs > New Job.
Alternatively, you can access the same page from any of the site, device, or alert paths listed above, and the selected sites or devices will be added as job targets. For more information, refer to Job Targets.
When the page is accessed from a component list, the selected components will be added as components but no job target will be defined.
- Configure the following sections:
- Job Targets
- Advanced Options
- Automatically Email StdOut/StdErr Options
- Job Recipients
See below for further details on each section.
|Name||Enter a name for the job schedule.
You can identify your active and completed jobs by this name. Refer to Active and completed jobs.
||By default, the job is executed immediately. To schedule the job for later or for recurring instances, click Click to change...
Select one of the following options:
Immediately - The job will run as soon as it is saved.
At selected date and time - The job will run once at the selected date and time.
Daily - The job will run every day at the time indicated in the Start field.
Weekly - The job will run every week on all selected days at the time indicated in the Start field.
Monthly - The job will run in the selected months on the selected days, at the time indicated in the Start field.
Monthly day of week - The job will run in the selected months on the specified occurrence of the selected days of the week, at the time indicated in the Start field.
Yearly - The job will run on the selected day (1 - 365) each year, at the time indicated in the Start field.
On Connect - On-connect jobs can only be scheduled by following one of these paths:
• Sites > select one or more sites > click Schedule a job
• Sites > click a site name > Devices > select ALL devices > click Schedule a job
The job will run once on each device in the selected site(s) as soon as they connect to the platform. This happens only once the next time the Agent connects following the scheduling of the job. For example, if the Agent is already online, the job will run immediately. If the Agent is offline, the job will run the next time the device comes online (provided that the job has not expired).
Initial Audit - New devices with audit data matching the target filter will run the job once the initial audit has completed. Jobs will automatically retire on devices that do not meet the target.
Once the job schedule has been configured, click OK.
By default, offline devices will queue until they come online or the job expires.
If it's a recurring job, any new devices added to the sites will pick up the job at the next run time.
Jobs use the time zone configured on the Setup > My Info tab. Refer to Your user account.
|Running as Security Level||This field is not editable, however, when you edit a job after it's been saved, the field will show the security level used when the job got scheduled.|
- Click Add targets.
- Select one of the following Target types and select any number of items within it.
- Site Groups
- Default Device Filters - When selected, the sites that you have access to will be listed below the list of filters. You can select any number of Default Device Filters and any number of sites to target the selected filters at. If you have access to all sites in the account, you will see an All Sites option as well.
- Custom Device Filters
- Device Groups
- Site Device Groups
- Site Device Filters
You can only target sites, devices, groups, and filters that you have access to.
The page lets you:
- Search - As you type, the search results are narrowed to match your search string.
- Show entries - Select to show 10 / 25 / 50 / 100 entries per page. 10 is selected by default.
- Select pages - Click a page number or click Previous / Next to jump to the previous / next page of results.
- Once you have selected the items, click Add.
Your selection is now added to the Job Targets section.
- To add more items from other target types, repeat the steps. You can add any number of items and target types to the job targets.
- To remove a target from the list, click the Delete icon .
For details on how jobs target devices, refer to A note on job targets.
Add components to the job. Multiple components will run sequentially in the order in which they are defined.
|Add a Component
||Click Add a Component and select one or multiple components from the list. You will see all components your component level allows you to see. Refer to Users.
To find the components more easily, you can:
• Search - As you type, the search results are narrowed to match your search string.
• Select a group - Click to select a component group to only display components of that group. For information on component groups, refer to Manage component groups.
Once your components are selected, click Save.
You can control the order in which components are deployed. To reorder the components, click the green up and down arrows on the right. To remove a component from the job, click the delete icon .
If the components have variables, you can configure them under the Variables column.
|Alert me if||You can choose to create an alert when the job:
• has warnings
You must select at least one of the Alerts options to be able to receive StdOut or StdErr files via email. See below.
Job alerts appear on the Account > Monitor page when you toggle to Job Alerts. Refer to Job alerts.
You can configure to receive an StdOut or StdErr file via email after the job has run.
You can download the job output file from within the email notification. The link expires after 7 days, however, you can also access and download the file in the Web Portal. Refer to The job view.
|Select output choices||
You must select at least one of the Alerts options above to receive files.Select any of the following options:
• Stdout - Check this check box to receive an email when the job is complete.
• Stderr - Check this check box to receive an email when an error occurs.
|Select the file format||Select one of the following options:
• Plain text
Choosing Plain text lets you select two additional options:
• Output Only - Check this check box to omit job summary information from the message (such as number of devices the job was run on, etc.).
• Use custom file extension - Check this check box to present the output in a certain format (for example, output tab-delimited text as .csv).
|Send alert to||
You must select at least one of the Alerts options or the Automatically Email StdOut/StdErr Options to be able to configure this section.Select any of the following options:
• Default recipients - An email will be sent to the user who scheduled the job, and to the default email recipients set in Account Settings and/or Site Settings.
• Additional recipients - Add any additional email recipients.
The email field only accepts the following characters:
- Click Save. The job schedule is now created and you are directed to the Jobs > Active Jobs page.
Jobs scheduled for a one-time or recurring delivery in the future are listed on the Jobs > Active Jobs page. Completed jobs are listed on the Jobs > Completed Jobs page. For more information, refer to Active and completed jobs.
A job can only be edited, deleted, or retired by an Administrator or a user with the same security level as the one that was used when the job was created. For example, if a job was created by a user with Administrator security level, non-Administrator users will be unable to edit, delete, or retire that job.
Active and completed jobs can be edited or deleted on the Jobs > Active Jobs or Jobs > Completed Jobs page, respectively. For more information, refer to Active and completed jobs.
To speed up the deployment process and minimize the bandwidth needed to distribute components to devices in the same site, we recommend that you use a local component cache. For further information, refer to Designate a local cache.
When a job is about to fire, it performs a scan to build a list of devices that are part of the job targets (e.g. filters or groups) at that time.
To better understand this, let's see a few scenarios when a job targets your devices via a filter:
- If you change the criteria of a filter after you scheduled a job with that filter, you do not need to redefine the job because the job will fire against all devices that hit the filter criteria defined at fire time.
- If a job has been fired (that is, the scheduled time has passed) but it has not run on certain devices, and the job is set to never expire and has no duration setting, it will run on those devices the next time they come online. This is irrespective of any changes you subsequently make to the filter because the job is already queued up to hit those device. Therefore, if, at this point, you delete the filter, the devices will still be targeted. However, if the job is set to expire or has a duration timestamp, and the devices come online after that time, the job will not fire due to the expiry and/or duration setting.
- If a job has been scheduled but the scheduled time has not yet passed, and you delete the filter before the scheduled timestamp, the devices in the filter will not be targeted because there is no filter to target against.
|Need to troubleshoot this? Open the Datto Knowledge Base.|
|Want to talk about it? Head on over to our Community Forum!|
|Forward this topic to others.|
|Provide feedback for the Documentation team.|