At the moment I am test benching SCCM/WSUS/SCUP integration and I am having a problem with update deployments that is more of an annoyance than anything. I am able to get an update package created and deployed, even have WoL working but the deployment status of the updates stays "Unknown" until the next morning. I would like to be able to track the current state of the dpeloyment without having to wait 24 hours. I know the stations are reporting properly, because if I run the report "management 2- Updates in a deployment" the information is current. Is there a way to get the deployment status of the updates to be a little more responsive? Jim

How often do you refresh the client status messages? It's a setting on the computer client agent. Is it a multi tier hierarchy?Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

At the moment the policy poling on the site is set to 480 minutes and the state message cycle is set to 15 minutes. I have changed the Policy polling on the colelction of test boxes to 5 minutes fro testing though. The test boxes are in the primary site JIm EDIT: only answered half the question

You'll always have to wait for the client state messages to return from the clients. No getting around that one. Note that this has nothing to do with policy polling interval. Also, ConfigMgr doesn't display any new update info until it "summarizes" the data which by default happens every four hours. You can right-click on the Software Updates node and choose Summarize Homepage data (or something similar) to force it to summarize the data now and get you data in closer to real-time.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I was pretty sure the policy interval had nothing to do with it, but I threw it in there for the sake of completeness. I have tried the homepage summarization a few times and it is still not showing up to date information. :(

I have from time to time forced the status message cycle to start by running a script on the client: Option Explicit On Error Resume Next Call RefreshServerComplianceState ' WScript.Echo "Finished" Sub RefreshServerComplianceState() ' Initialize the UpdatesStore variable. dim newCCMUpdatesStore ' Create the COM object. set newCCMUpdatesStore = CreateObject ("Microsoft.CCM.UpdatesStore") ' Refresh the server compliance state by running the RefreshServerComplianceState method. newCCMUpdatesStore.RefreshServerComplianceState ' Output success message. ' wscript.echo "Ran RefreshServerComplianceState." End SubKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Ran the script still no luck. I guess if it becomes an issue I will just have to get better at writing my own reports.