Modifying a Configuration Manager 2007 service window may cause an unexpected delay in a software update deployment

Consider the following scenario: 

• You create a maintenance window for a Microsoft System Center Configuration Manager 2007 collection.
• You create a new software update deployment with a deadline that is prior to the maintenance window of the System Center Configuration Manager 2007 collection.
• You modify any property of the maintenance window after the software update deployment deadline. 

In this scenario, this may result in a missed opportunity to install updates right after the new service window becomes available. This happens because the Update Deployment Agent (UDA) finds no suitable service window for the installation, thus the new service window targeted to the client is ignored until the next evaluation cycle.

You may also see the following message in updatedeployment.log:

OnServiceWindowAvailable - No pending install assignment

This is by design in System Center Configuration Manager 2007.

We have two workarounds for this issue:

1. Schedule the updates evaluation cycle after service window creation.

2. Deploy updates after service window creation, not before.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Article ID: 2850370 - Last Review: 05/20/2013 19:05:00 - Revision: 1.0

Microsoft System Center Configuration Manager 2007

  • KB2850370