Scheduler Takes a Long Time To Activate Jobs

Last reviewed: April 24, 1997
Article ID: Q153087

The information in this article applies to:

Microsoft Systems Management Server versions 1.0 and 1.1

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 : kbbug1.00 kbbug1.10 kbfix1.20 kbnetwork smsadmin smsscheduler
Version : 1.0 1.1
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.