Jump to content


Using Update Lists when deploying Monthly Updates

Recommended Posts

In Part 1. We created the Update List for Windows XP Security Updates and we created a Deployment Management Task. In this Part we will target the deployment management task to our Test XP collection and then we will verify the updates are deployed.


Step 1. Select our Deployment Management Task


Expand the Deployment Management node and select the Windows XP Security Updates - March 2010 Deployment Management task we created,


march updates properties.jpg


right click and choose Properties.




When the Properties window appears, click on the Collection tab




click on Browse and browse to your XP test collection,


Note: In the screenshot below I have linked to the All Windows XP Systems collection, but in a Production environment you should have a defined set of computers to test patches on in their own separate collection. It is entirely up to you how to set that up.


all windows xp.jpg


We have already set the schedule on the Deployment Management Task so understand that as soon as you click Apply then those updates will be made available to that Collection.






Step 2. Verify that your updates are deploying



Just before the deadline occurs, your XP machines should start receiving the new Update Policy. You can verify this easily in the lab because you'll see it




But to verify/troubleshoot updates being deployed remotely you'll need to familiarise yourself with the following logs on the Clients.


Software Updates Client Computer Log Files


* CAS.log - Provides information about the process of downloading software updates to the local cache and cache management.

* CIAgent.log - Provides information about processing configuration items, including software updates.

* LocationServices.log - Provides information about the location of the WSUS server when a scan is initiated on the client.

* PatchDownloader.log - Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

* PolicyAgent.log - Provides information about the process for downloading, compiling, and deleting policies on client computers.

* PolicyEvaluator - Provides information about the process for evaluating policies on client computers, including policies from software updates.

* RebootCoordinator.log - Provides information about the process for coordinating system restarts on client computers after software update installations.

* ScanAgent.log - Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.

* ScanWrapper - Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.

* SdmAgent.log - Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.

* ServiceWindowManager.log - Provides information about the process for evaluating configured maintenance windows.

* smscliUI.log - Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.

* SmsWusHandler - Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.

* StateMessage.log - Provides information about when software updates state messages are created and sent to the management point.

* UpdatesDeployment.log - Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.

* UpdatesHandler.log - Provides information about software update compliance scanning and about the download and installation of software updates on the client.

* UpdatesStore.log - Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.

* WUAHandler.log - Provides information about when the Windows Update Agent on the client searches for software updates.

* WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.




In Part 3. of this series, we will look at how we can use the reporting function within SCCM by using our Update Lists. This will give us an overview of the Software Update Compliance of our targetted systems.

Share this post

Link to post
Share on other sites

Dear Anyweb,


I followed your article step-by-step but my test computers are not getting the updates. I checked the logs folder and none of the logs that you mentioned are there. The client is isntalled and running on the test comptuers.


Please note that my software update point is installed on another Server since I used an existing WSUS Server. Component Status and Site System Status are green



Share this post

Link to post
Share on other sites

In this printscreen there are collections (Deployment Management) that are greyed out. How can you set them back to green status in order to have them working again?




I'm asking because I do have this and what I do is delete the greyed out updates, do a refresh of the package and it's green again but it's not the way it should be.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...