From the Movere Console, scans can be configured to occur at a specific time, on a regular basis, without user intervention, and without having to leave the Movere Console open.
To schedule a scan, select the ‘Scheduled Scan’ option from the ‘Getting Started’ tab:
The ‘Scheduled Scan’ option is essentially identical to the ‘First Scan’ option with the only difference being timing. The ‘First Scan’ option initiates the scan immediately while the ‘Scheduled Scan’ option will start the scan(s) at the scheduled time(s).
Just like a ‘First Scan’, select the desired scanning option then click through each tab to add the necessary pre-requisites. We recommend creating separate tasks for each scanning option.
NOTE: Multiple tasks can be run simultaneously as each task will create its own Log Service file.
The Movere Console can be used to schedule Active Directory, vCenter Appliance, and Office 365 extractions, in addition to Windows Server and Workstation scans. When set to scan Windows devices, Movere will create a targeting file by querying the domain(s) selected for scanning for the object type(s) the user wants to scan i.e. servers, workstations or both.
When creating a ‘Scheduled Scan’ provide the new scheduling task with a unique name, duplicate names are NOT permitted. The frequency of the scan (days, weeks, months) can then be entered followed by the time and day of the week:
Once the desired settings have been entered, saving the task will create a new entry in the ‘Manage scan schedules’ table. NOTE: The Last Run value will be blank until the scheduled scan has completed:
Once a scheduled scan has completed, the ‘Last Run’ timestamp in the ‘Manage scan schedules’ table will update with the appropriate date and time
IMPORTANT: The Movere scheduled scan feature leverages the Windows Task Scheduler. If a scheduled task fails to run, then we recommend reviewing the Windows Task Scheduler log. For example, attempting to run a scheduled scan from a laptop running on batteries will result in a launch condition failure, which can only be diagnosed from the Windows Task Scheduler log: