Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

Symptoms

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.

↑ Back to the top


Workaround

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.


↑ Back to the top


Keywords: kb

↑ Back to the top

Article Info
Article ID : 2850370
Revision : 1
Created on : 1/7/2017
Published on : 5/20/2013
Exists online : False
Views : 384