General Options - Scheduling

 

The General > Scheduling dialog enables you to specify which scheduler service you prefer to use when deploying patches and remediating spyware. The scheduler is used to initiate the deployment or remediation task at the specified time, whether immediately or at some specified time.

 

The scheduler service you choose is the scheduler you prefer to use in situations where more than one scheduler will work. If your preferred scheduler will not work in a particular circumstance, the other scheduler will be automatically invoked. For example, scheduling deployments or remediations from a Windows XP or Windows 2003 console to remote machines will not work using the Microsoft Scheduler because of new security features in those systems. In this case the Shavlik scheduling method will be used.

 

 

 

Microsoft Scheduler

Use this scheduler service in those circumstances where it provides the needed functionality.

 

Alternate scheduling method

This pushes a copy of the Microsoft Scheduler to each target machine where it is used to initiate the scan, patch, and remediation tasks. After the scheduler service is finished with its tasks it is removed from the service control manager.

 

Shavlik Scheduler

The Shavlik Scheduler service is faster and more secure than the Microsoft Scheduler service. A copy of the Shavlik Scheduler service is pushed to each target machine where it is used to initiate the scan, patch, and remediation tasks. With the Shavlik Scheduler service you can specify what should happen to the service after it is finished performing its tasks.

 

The Shavlik Scheduler is the default scheduler service.

 

Default Scheduler Port

Specifies the port used by Shavlik Scheduler service. By default the Shavlik Scheduler service listens on TCP port 5120.

 

Scheduler Lifetime

 

This specifies what to do with the Shavlik Scheduler service after it completes its scan, patch deployment, or spyware remediation tasks on the target machine.

 

  • Leave the service running: Leaves the service running so it is instantly available for future scans, deployments, or remediations.

  • Stop the service and leave it installed in service control manager: Doesn't use CPU time on the target machine but keeps the service available for future use.

  • Stop the service and remove it from service control manager: Stops and removes the service but leaves certain files on the system for easy reuse.