Knowledge Base

Scheduler Takes a Long Time To Activate Jobs

Article ID: 153087

Article Last Modified on 10/27/2006


APPLIES TO


This article was previously published under Q153087

SYMPTOMS

When activating a Run Command On Workstation job that has no Run phase (only a Send phase and a Distribute phase) the scheduler updates the JobDetails table one row at a time for each computer in the job target.

For large sites this causes long delays in the job activation. For example, on a site with 3,000 clients the scheduler can take up to 30 minutes to activate a job sent to *|*|*.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server versions 1.0 and 1.1. This problem has been corrected in Systems Management Server version 1.2.

Additional query words: prodsms sms1.2rel machineid nextmachineid smsdata

Keywords: kbnetwork kbscheduler kbsmsadmin KB153087