Export (0) Print
Expand All

Software Updates State Messages

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

Software updates in Configuration Manager 2007 provide state messages that can be used to report on the state of deployments, software updates, and the scan for software updates compliance.

Specifically, software updates state messages are created and sent by Configuration Manager 2007 client computers for the following:

  • States for deployments

  • States for software updates

  • Scan states for an update source

States for Deployments

Client computers create state messages when evaluating software update deployments, for the compliance of deployment (whether or not the client requires one or more software updates in the deployment), and for the enforcement of a mandatory deployment.

Unlike other software updates state messages that are replicated up the hierarchy to the central site, state messages for deployments are replicated up the hierarchy to the site where the deployment was created. Software update deployment enforcement, evaluation, and compliance information will be missing from reports when they are run from a site higher in the hierarchy than where the deployment was created.

Evaluation States for a Deployment

When a new deployment is created and the client computer evaluates the assignment policy for the deployment and during the deployment reevaluation cycle, one of the following state messages is created:

  • Evaluation state unknown

  • Evaluation activated

  • Evaluation succeeded

  • Evaluation failed

Enforcement States for a Mandatory Deployment

When the deadline is reached for a mandatory deployment, client computers create state messages for the following:

  • Enforcement state unknown

  • Installing update(s)

  • Waiting for restart

  • Waiting for another installation to complete

  • Successfully installed update(s)

  • Pending system restart

  • Failed to install update(s)

  • Downloading update(s)

  • Downloaded update(s)

  • Failed to download update(s)

  • Waiting for maintenance window before installing

By segregating update enforcement state messages and deployment enforcement state messages, administrators can create detailed, precise, near-real-time reports for management that were previously difficult, if not impossible, to create.

Compliance States for a Deployment

Client computers report the compliance for a software update deployment by using the following state messages:

  • Compliance state unknown

  • Compliant

  • Non-compliant

  • Conflict detected

States for Software Updates

Client computers create state messages for the compliance of software updates and the enforcement of software updates in a mandatory deployment.

Compliance States for a Software Update

When client computers scan for software updates compliance, a state message with one of the following compliance states is created for each software update:

  • Detection state unknown

  • Update is not required

  • Update is required

  • Update is installed

Enforcement States for a Software Update

When the deadline is reached for a mandatory deployment, client computers create a state message for each software update in the deployment. The following software update enforcement states provide information about the software update installation:

  • Enforcement state unknown

  • Enforcement started

  • Enforcement waiting for content

  • Waiting for another installation to complete

  • Waiting for maintenance window before installing

  • Restart required before installing

  • General failure

  • Pending installation

  • Installing update

  • Pending system restart

  • Successfully installed update

  • Failed to install update

  • Downloading update

  • Downloaded update

  • Failed to download update

Scan States for an Update Source

When a scan is run on a client computer, a state message is created for each update source—for example, Microsoft Update or the Inventory Tool for Microsoft Updates. One of the following scan states is created:

  • Scan state unknown

  • Scan is waiting for content

  • Scan is running

  • Scan completed

  • Scan is pending retry

  • Scan failed

  • Scan completed with errors

  • SMS 2003 client

See Also

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft