none
WSUS Server Cleanup Wizard Removes machines from Downstream servers RRS feed

  • Question

  • Hello All,

    I have a primary(upstream) WSUS server with 3.0 sp2.  It is my central location for approving updates, and I also store updates locally here. 

    I have one downstream server (soon to be more once I work out some kinks) This downstream server has 30 machines. 

    On initial configuration everything worked great.  I was able to see the computer groups setup on my primary from the downstream, added systems to the appropriate group and watched them populate on the primary server.  I could then run reports and approve updates for the downstream, from my primary(upstream).  (hope that all made sense)

    Since then, I ran the server cleanup wizard from the primary server.  I unchecked remove computers that have not reported in 30 days.  Because I have some systems that may be turned off for extended periods. This should not have mattered since my servers have not even been live for 30 days.

    After running the cleanup wizard, even with remove computers after 30 days UNCHECKED,  all systems from my downstream server were removed from the primary. 

    Also, The downstream now reports that all of it's computers are 100%.  Which is not the case. 

    So my question is how can I get the computers from the downstream to re-populate in the upstream so I can run reports from there etc?

    What did I do wrong and how can I avoid this situation in the future?

    How can I ensure that all of my downstream computers get all of the updates that have already been approved and were waiting prior to the server cleanup wizard?

    Thanks Everyone

    Wednesday, May 12, 2010 2:33 PM

Answers

  • Ready to have your mind blown?

    I rebuilt the upstream server from scratch as suggested.  I completely rebuilt the operating system from disc, rather than copying my empty/blank win2k3 virtual machine. 

    Next, I installed IIS.  After installation I right clicked web sites chose properties->services tab and checked compress application, as it is off by default in IIS 6.0.  I did this because it's checked on my downstream, and my downstream's GetConfiguration reports 0 (checked)  ***I did this berfore WSUS installation.

    After completely installing WSUS my reporting roll-up is working all of my downstream computers are reporting their statuses and are available on the upstream! Great right?  Not so fast. 

    I thought well,.. Let's run GetConfiguration tool on the upstream now just for kicks, well and for you Lawrence, by the way thank you so much for all of your help.  IISDynamicCompression still reports a -1 (off, UnChecked!) Not matching the downstreams that are successfully syncronizing. 

    So!?  I have a feeling that my reporting rollup will begin to fail yet again, just like the last time.  I remember reading in one of your other threads, Lawrence, that it takes a few weeks for this problem to begin when the compression settings do not match.  Maybe I'm mistaken, I hope I'm mistaken, I've already put soo much time into this shotty, random result producing, disaster of a solution. That's not yet a confident solution......

    Thanks again everyone, Lawrence.  Let's leave this open so when rollup starts failing again we can um,... ask Mr. Garvin what to do.... ?

     

    Tuesday, July 20, 2010 3:12 PM

All replies

  • I have one downstream server (soon to be more once I work out some kinks) This downstream server has 30 machines.
    Is this downstream server a replica, or autonomous?
    I was able to see the computer groups setup on my primary from the downstream, added systems to the appropriate group and watched them populate on the primary server.  I could then run reports and approve updates for the downstream, from my primary(upstream). (hope that all made sense)

    Sort of... but I think the issue may lie somewhere in this process. Can you please be more specific about exactly what you did on which server at what time, and where things happened automatically and where you did them manually?

    all systems from my downstream server were removed from the primary.

    Assuming the downstream server is a replica . . . Do they re-appear on the upstream server after performing a server synchronization from the downstream server?

    Also, The downstream now reports that all of it's computers are 100%.  Which is not the case. 
    What exactly, on the downstream server, reports that all of the computers are "100%". What exactly is "100%" . . . Installed/Not Applicable? If all computers are reported at 100% Installed/NotApplicable, and you are certain that is not the case, then find one of the updates in the All Updates view that you know is not installed, and review what is reported for the status of that update.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, May 12, 2010 2:56 PM
    Moderator
  • I have one downstream server (soon to be more once I work out some kinks) This downstream server has 30 machines.

    Is this downstream server a replica, or autonomous?

    Replica

    I was able to see the computer groups setup on my primary from the downstream, added systems to the appropriate group and watched them populate on the primary server.  I could then run reports and approve updates for the downstream, from my primary(upstream). (hope that all made sense)

    Sort of... but I think the issue may lie somewhere in this process. Can you please be more specific about exactly what you did on which server at what time, and where things happened automatically and where you did them manually?

    Well, the downstream server already existed with all computers added.  After creation of the upstream, I configured the downstream to pull updates and approvals from the upstream.  (options->update source->from another WSUS->check replica) After synchronization I could manually (server side) move computers from the unassigned computers group to any of my upstream groups (from the downstream).  I did so by right clicking the computer->change membership->check the box for the appropriate group.  I could then go to my upstream and see the pc move from unassigned to the appropriate group.    This was the state the server for about 1 week all was working well, I was approving updates for my test group only, allowing them to install, testing, and then assigning to my production groups (each downstream has it's own group, each downstream is a different client with their own internal WSUS (replica) that updates with mine, there is only one live downstream at this point)  Then, I ran the cleanup Wizard after about 1 week of successful operation

    all systems from my downstream server were removed from the primary.

    Assuming the downstream server is a replica . . . Do they re-appear on the upstream server after performing a server synchronization from the downstream server?

    Yes, it is a replica.  Performing a manual synchronization reports successful, but does not re-populate. (has been a couple days since this happened as well)

    Also, The downstream now reports that all of it's computers are 100%.  Which is not the case. 

    What exactly, on the downstream server, reports that all of the computers are "100%". What exactly is "100%" . . . Installed/Not Applicable? If all computers are reported at 100% Installed/NotApplicable, and you are certain that is not the case, then find one of the updates in the All Updates view that you know is not installed, and review what is reported for the status of that update.

    -Please disregard this portion, I either misread my report the other day, or this has changed since then and the downstream is reporting the correct status of each computer.  Yes, I was referring to installed/notapplicable

    Wednesday, May 12, 2010 4:18 PM
  • >>> Do they re-appear on the upstream server after performing a server synchronization from the downstream server?

    >> Performing a manual synchronization reports successful, but does not re-populate. (has been a couple days since this happened as well)

    Last question: Do you have Reporting Rollup enabled on the upstream server?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, May 12, 2010 8:53 PM
    Moderator
  • Last question: Do you have Reporting Rollup enabled on the upstream server?


    Yes: "roll up status from replica downstream servers" is selected. 

    Thursday, May 13, 2010 2:41 PM
  • Last question: Do you have Reporting Rollup enabled on the upstream server?


    Yes: "roll up status from replica downstream servers" is selected. 


    The next step, then, is to review the Application Event Log and the %ProgramFiles%\Update Services\Logfiles\SoftwareDistribution.log for any entries related to failures that are occuring during synchronization events, that would be preventing the transmission of reporting/status information from the replica server to the upstream server.

    Fundamentally, though, you've reported that running the SCW with "Delete computers..." UNCHECKED, has resulted in the removal of computer objects from the upstream server. This is particularly unusual behavior, and never before reported, so we're treading in somewhat uncharted waters here. This seems complicated, then, by the fact that computer status is not being reported to the upstream server during synchronization.

    This, however, is also dependent on whether the client systems are actually reporting to the replica servers. Just to rule out that possible cause, please post a recent detection event from one of the replica's client systems showing a successful detection/reporting cycle to the replica server.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Thursday, May 13, 2010 5:39 PM
    Moderator
  • This, however, is also dependent on whether the client systems are actually reporting to the replica servers. Just to rule out that possible cause, please post a recent detection event from one of the replica's client systems showing a successful detection/reporting cycle to the replica server.

    Here is a portion of c:\windows\softwaredistribution\reportingevents.log from one of my clients that report to the downstream server in question.  Not sure if this is what you are looking for, please advise. 

    {EF561D9F-7303-4E94-B4D9-08C0397478E1}    2010-05-11 09:54:27:525-0400    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    Windows Internet Explorer 7 Set    Success    Software Synchronization    Windows Update Client successfully detected 3 updates.
    {C73A631C-EFFA-443E-B98B-D082816205CF}    2010-05-11 09:54:27:535-0400    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0    Windows Internet Explorer 7 Set    Success    Pre-Deployment Check    Reporting client status.
    {1E26B31F-EE7A-4BD2-994F-3FFBE1B6572F}    2010-05-11 09:54:36:929-0400    1    162    101    {AB6644CB-015B-4DF7-81AC-34D38C43EA58}    101    0    Windows Internet Explorer 7 Set    Success    Content Download    Download succeeded.
    {1D7A6B12-6038-4338-9D77-D4A87306D59C}    2010-05-11 09:55:41:061-0400    1    162    101    {91CD6585-51A7-4F0F-B48A-7784D52348A3}    102    0    Windows Internet Explorer 7 Set    Success    Content Download    Download succeeded.
    {CBCED5E3-B623-44CF-AA48-4CE24ADE36A4}    2010-05-11 10:00:28:464-0400    1    199    101    {83A56F7C-B154-4269-B665-42BB483C80C2}    102    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Windows Internet Explorer 7 for Windows XP
    {568A9FBD-C33A-417D-8F1F-DAD1D9577487}    2010-05-11 10:00:35:575-0400    1    199    101    {D60E6980-5288-4575-BDE2-D6A593DB9AC1}    101    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Security Update for Windows XP (KB974571)
    {EACB3C4F-6427-4353-89FF-4A2A2F1ADDAD}    2010-05-11 10:00:44:067-0400    1    197    101    {9BF01484-3C26-4B16-B846-54A057162F12}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP Service Pack 2 (KB973540)
    {F884C64D-8312-4C4A-9348-936827D18CC5}    2010-05-11 10:00:50:536-0400    1    197    101    {CBE22D85-CBB3-447E-804F-1835072057C2}    102    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB975025)
    {406F30E7-ADEF-4A7E-9726-99B9BC5629E0}    2010-05-11 10:00:57:326-0400    1    197    101    {03100286-5495-49B2-A4B0-795A73936C35}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB973869)
    {4EC3793C-D975-4D83-B5E5-A9D0D4087578}    2010-05-11 10:01:09:283-0400    1    197    101    {8266A188-8F06-42ED-ABD7-5E467E9AAD81}    102    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update to .NET Framework 3.5 Service Pack 1 for the .NET Framework Assistant 1.0 x86 (KB963707)
    {D0D3C300-7833-4B57-8209-34C3B6654399}    2010-05-11 10:01:18:316-0400    1    197    101    {31E37C89-7C4A-4CE0-85D1-28A8E947CB5F}    104    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB975561)
    {BD05AD20-BE2F-40CE-9A1B-BD5A4BA3D514}    2010-05-11 10:01:24:855-0400    1    197    101    {4A5FC28E-6A13-454F-B4CF-3612C4EB854D}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows Media Format Runtime 9, 9.5 & 11 for Windows XP SP 2 (KB968816)
    {9B82757E-5F59-4E64-9AC4-D657DAA9ABCA}    2010-05-11 10:01:31:986-0400    1    197    101    {38D40594-4A82-41EC-A26A-3297F3940276}    102    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB956844)
    {63154A48-EABF-47AE-AFB2-7B1E62774AE4}    2010-05-11 10:01:54:839-0400    1    197    101    {8FE60694-94C6-4568-8094-17E2E92045EA}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office 2003 (KB953404)
    {63EEA5E2-2A2A-4E0A-A5E2-BAC5550E5A42}    2010-05-11 10:02:02:199-0400    1    197    101    {A7021C99-1C0D-4CA5-BC65-A60A04CF3D79}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB974112)
    {A8BD22AA-95E7-4CA3-B513-C6AD36AF84CF}    2010-05-11 10:02:11:332-0400    1    197    101    {EE69B39F-4DEE-4BD9-8FF2-D01B082E2C4A}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB956744)
    {9E6992EB-2A9A-4118-9D7A-39DBB56AD989}    2010-05-11 10:02:18:713-0400    1    197    101    {3598CCA3-3E11-4314-B46A-6F2C3FFAC421}    105    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB972270)
    {855725DA-7731-49C4-95C6-C4F4CE6280F3}    2010-05-11 10:02:32:332-0400    1    197    101    {123593AA-A4CD-41A4-9630-6FED933B70D9}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update for Windows XP (KB961118)
    {CD530262-22E0-4314-9A33-BDA0ACC55250}    2010-05-11 10:02:39:523-0400    1    199    101    {1B90D9AA-16E1-4A0D-9A42-BC317948E8E7}    101    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Security Update for Windows XP (KB978338)
    {BAFFE6F0-F8D2-4EE2-824C-90FCE4F84A14}    2010-05-11 10:02:46:303-0400    1    199    101    {8A146CAF-F475-45E0-A8C4-0B02DBF6ABC5}    101    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Security Update for Windows XP (KB971657)
    {E4503283-E63E-4D78-8DA5-793F93F4FBE1}    2010-05-11 10:03:02:526-0400    1    197    101    {285601B8-5C07-4856-B4E6-847F053BE4CB}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office Word 2003 (KB954464)
    {5C16B7B5-553F-4670-B599-FB8863E03234}    2010-05-11 10:03:08:795-0400    1    197    101    {6E6CEAB8-B219-45E6-AAB7-C7ED62CB58FA}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB975713)
    {246999C3-E619-40B0-96E5-0EED129970E9}    2010-05-11 10:05:16:278-0400    1    199    101    {491005BA-E78D-410E-B5FA-9E1EC665A6B3}    100    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Microsoft .NET Framework 2.0 Service Pack 2 Update for Windows Server 2003 and Windows XP x86 (KB976569)
    {6A660515-07BE-4283-AEAF-E2BDE9BC4B85}    2010-05-11 10:05:23:899-0400    1    199    101    {9B13D7BB-287C-4341-9473-E1F99F5F2FDA}    101    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Security Update for Windows XP (KB978037)
    {77797C64-B4B6-4EF6-9EB6-A1CE9ED3189D}    2010-05-11 10:05:48:314-0400    1    197    101    {938D8BBF-F928-4DAC-BAEF-B66005583409}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Office 2003 (KB954478)
    {3FDE2F5C-7EEF-47D8-9B89-5E517DC83925}    2010-05-11 10:05:55:445-0400    1    197    101    {7C54B2C5-32E5-467F-B098-26424F4B9932}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB969059)
    {A95359E2-CE25-4DD8-9165-CD18E95843AB}    2010-05-11 10:06:03:176-0400    1    199    101    {9900B4C6-0071-4E02-962E-F6F6B849EAF0}    101    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Security Update for Windows XP (KB974318)
    {E2A5483A-E33E-4F53-87B4-FCCE286BA61D}    2010-05-11 10:06:57:003-0400    1    197    101    {AD955CC9-3A14-4175-9145-171B20230BF9}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office Excel 2003 (KB955466)
    {D49D3F7C-32F3-4852-A8FA-F4D15617045E}    2010-05-11 10:07:53:214-0400    1    197    101    {22BED1C9-04D5-4B79-BD66-4CED8BE61DCF}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Windows Malicious Software Removal Tool - April 2010 (KB890830)
    {EEE323F2-A402-4556-8D57-D150F70C7109}    2010-05-11 10:08:02:968-0400    1    199    101    {6ACD6BCB-A59F-4926-A76E-D07E0C1ECA73}    100    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Update for Windows XP (KB955759)
    {59F30821-A8E6-48FD-AC2F-ACC69242AD09}    2010-05-11 10:08:09:898-0400    1    197    101    {23576BD1-28E5-4E8E-A4DD-71CFE5EFD831}    102    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB981350)
    {026809F2-E8C4-4BE3-9900-F316CCEBDC6E}    2010-05-11 10:08:17:309-0400    1    199    101    {CEF35DD3-298D-4D2A-AE6A-5D9FE7A6A1D6}    102    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Security Update for Windows XP (KB980232)
    {247F052C-451B-43F0-9AB4-8D52D23BDA3F}    2010-05-11 10:08:24:218-0400    1    197    101    {4D3E81D4-540D-4C50-A68A-3C1E91A2AEF9}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update for Microsoft XML Core Services 6.0 Service Pack 2 (KB973686)
    {9E32D72B-DD56-4DA3-94BA-80B5F8F7B80F}    2010-05-11 10:08:29:065-0400    1    197    101    {5CF65ED9-975C-4B52-AFF7-7671E68DD230}    102    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows Media Format Runtime 9, 9.5 & 11 for Windows XP SP 2 (KB954155)
    {3DE96095-23F4-4EC9-82F6-398993839820}    2010-05-11 10:08:34:313-0400    1    199    101    {F98256E0-C539-480F-A942-B30E38B3A697}    102    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Security Update for Windows XP (KB958869)
    {322E05B4-CC88-4FFB-8B1B-FC193C4D5331}    2010-05-11 10:08:56:865-0400    1    199    101    {B0EB6BE9-8C12-492B-9115-A565C7B4BE5A}    102    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Security Update for Windows XP (KB979683)
    {9EFE8A51-0078-41F3-A968-325FDCFE24D2}    2010-05-11 10:09:04:126-0400    1    199    101    {561D99EC-5266-46EF-9BC5-FA1627CC1AAD}    102    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Security Update for Windows XP (KB971468)
    {6BC0115E-FA90-4CEC-BFBC-C054142EA249}    2010-05-11 10:09:13:109-0400    1    197    101    {7A3D3EF0-B671-4E63-8A49-B13A200CA003}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB960859)
    {CBC4334F-263B-4797-A87A-BAFA2FF04A56}    2010-05-11 10:09:19:488-0400    1    197    101    {4E46CAF9-4849-40CC-84FC-20F0FB21C6A5}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Cumulative Security Update for ActiveX Killbits for Windows XP (KB978262)
    {122371BF-360C-41FB-AA54-B8C61AEDE159}    2010-05-11 10:09:20:449-0400    1    197    101    {31B7A8FE-AB69-4C75-8A6A-7074B4A7EC32}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update for Root Certificates [November 2009] (KB931125)
    {1644D12E-7ABA-497B-BBBB-990C8EFCB4C9}    2010-05-11 10:09:38:996-0400    1    197    101    {EDABB0FE-1B6A-478B-806B-7FFFD044B2EE}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Update for Microsoft Office Outlook 2003 (KB953432)
    {258B1E77-2B9F-446B-9E68-37A02942DC4D}    2010-05-11 10:09:39:056-0400    1    193    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Restart Required: To complete the installation of the following updates, the computer must be restarted. Until this computer has been restarted, Windows cannot search for or download new updates:  - Security Update for Windows XP (KB969947) - Update for Windows XP (KB968389) - Update for Windows XP (KB979306) - Update for Microsoft XML Core Services 4.0 Service Pack 2 (KB973688) - Security Update for Windows XP (KB971032) - Security Update for Windows XP (KB973815) - Security Update for Windows XP (KB978706) - Security Update for Windows XP (KB979309) - Security Update for Access Snapshot Viewer 2003 (KB955439) - Security Update for Jscript 5.6 for Windows XP (KB971961) - Security Update for Windows XP (KB977914) - Microsoft .NET Framework 1.1 Service Pack 1 Security Update for Windows 2000, Windows XP, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 (KB953297) - Security Update for Microsoft Office 2003 (KB921598) - Office 2003 Service Pack 3 (SP3) - Security Update for Microsoft Office PowerPoint 2003 (KB948988) - Security Update for Windows XP (KB974392) - Security Update for Windows XP (KB973904) - Security Update for Windows XP (KB973354) - Updat
    {A1010F21-FA00-4FE8-A79C-CF871A3FA21B}    2010-05-12 10:05:40:742-0400    1    202    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Reboot completed.
    {B5EA9D18-00D9-4083-8E11-0DBACE14F9EE}    2010-05-12 10:10:32:692-0400    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 16 updates.
    {7654085D-E4AD-471A-BF4D-5A6FC1696A6A}    2010-05-12 10:10:32:732-0400    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.
    {7F1822CE-0772-4833-9F55-F14071802723}    2010-05-12 10:11:05:780-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469)
    {580E0521-CDC7-486E-BC7F-68629DECEA45}    2010-05-12 10:11:05:780-0400    1    162    101    {5277AD17-D673-4094-9031-EBC74DB0D9A2}    100    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {EA7395F3-5A26-4620-BBBD-5CA20727F381}    2010-05-12 10:11:56:703-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881)
    {D9497110-C5A6-4DA2-A103-BC45AC7EFDF7}    2010-05-12 10:11:56:703-0400    1    162    101    {9D23842D-BD64-481A-8B8A-5BA8CD2A2D7B}    100    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {8909C577-BC95-4535-9ED1-7DE15F42F40F}    2010-05-12 10:12:08:730-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737)
    {EB57ED9C-15B3-4B93-BAEA-F4735802A5DE}    2010-05-12 10:12:08:800-0400    1    162    101    {51C4DF3E-7F6F-4AC4-BD2F-B1F5CF9EB3CD}    101    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {13F44326-5ABD-4F26-A8AD-46BD552EC621}    2010-05-12 10:12:25:444-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580)
    {44EF258F-55BF-4C16-B583-F3A5C4186813}    2010-05-12 10:12:25:454-0400    1    162    101    {B8D94C42-A29A-46CA-B896-BC0A502E64B8}    102    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {3D83A2D7-6D50-451D-849F-CAC1FD1D172E}    2010-05-12 10:12:39:354-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535)
    {D1707D73-FABE-4292-BB23-03F3B8143A38}    2010-05-12 10:12:39:354-0400    1    162    101    {CA67A850-6126-4597-B94B-C17DB71506AC}    100    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {69648538-A14A-4886-99A2-861D01B5B08F}    2010-05-12 10:13:55:053-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474)
    {6EE33108-7D1B-49CE-8193-F9DE25241863}    2010-05-12 10:13:55:053-0400    1    162    101    {5DF5C48F-6F78-4B0C-B56D-5F378313B1BF}    103    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {BC8C1792-C07E-4B80-B9ED-5F27FDB45154}    2010-05-12 10:15:51:741-0400    1    162    101    {66BD9792-6981-44FD-B235-0353CFBC843C}    100    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {2FDB6C3D-DB0C-4330-AC63-77BC9377D8DA}    2010-05-12 10:15:51:741-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443)
    {2823BFE4-CC48-40CF-AFB0-5EBD9E656D75}    2010-05-12 10:17:30:082-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443) - Security Update for Microsoft Office Web Components (KB947319)
    {8E8C8131-09BB-416A-AB2D-F8FF6B87297C}    2010-05-12 10:17:30:082-0400    1    162    101    {8AACF2BF-68AA-4C90-B606-D4CF5770A970}    105    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {4FA581AC-A96A-4743-B64D-75BB36A71A1B}    2010-05-12 10:17:36:882-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443) - Security Update for Microsoft Office Web Components (KB947319) - Security Update for Microsoft Office 2003 (KB974554)
    {20049850-DD8A-461F-8D5B-0D36D34AB415}    2010-05-12 10:17:36:882-0400    1    162    101    {069D43C3-3E28-4BC5-9CE6-489C1F0A57ED}    101    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {5BE8315A-65AD-4624-B7FD-D820065A0261}    2010-05-12 10:17:42:761-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443) - Security Update for Microsoft Office Web Components (KB947319) - Security Update for Microsoft Office 2003 (KB974554) - Security Update for Microsoft Office 2003 (KB975051)
    {6F8D157E-FE5F-464B-99C4-E29D2DC64338}    2010-05-12 10:17:42:771-0400    1    162    101    {C91B2EC4-97FA-4C1C-8C59-F18A091E55E7}    102    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {E4AEE866-34B7-43FD-855D-3C0D91754772}    2010-05-12 10:17:54:768-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443) - Security Update for Microsoft Office Web Components (KB947319) - Security Update for Microsoft Office 2003 (KB974554) - Security Update for Microsoft Office 2003 (KB975051) - Update for Windows XP (KB970430)
    {77BBE46C-A3DD-484E-BDBB-33A7AAD7C943}    2010-05-12 10:17:54:768-0400    1    162    101    {4F8EDCD7-68BF-4AC4-B6DE-9617BFFD0B97}    101    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {6BDD647C-5219-49E1-BB78-712B7E5F106E}    2010-05-12 10:20:03:964-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443) - Security Update for Microsoft Office Web Components (KB947319) - Security Update for Microsoft Office 2003 (KB974554) - Security Update for Microsoft Office 2003 (KB975051) - Update for Windows XP (KB970430) - Security Update for Microsoft Office Outlook 2003 (KB973705)
    {84640E1B-5CF8-46AD-B087-71271BFC1A83}    2010-05-12 10:20:03:974-0400    1    162    101    {D0B67DE5-A5DE-492A-AF7D-827034E628E4}    102    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {018FFF58-1DE4-4451-9E8C-43CE37A8498C}    2010-05-12 10:20:12:326-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Jscript 5.7 for Windows XP (KB971961) - Security Update for Microsoft Office Publisher 2003 (KB980469) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443) - Security Update for Microsoft Office Web Components (KB947319) - Security Update for Microsoft Office 2003 (KB974554) - Security Update for Microsoft Office 2003 (KB975051) - Update for Windows XP (KB970430) - Security Update for Microsoft Office Outlook 2003 (KB973705)
    {6E75AA4B-247B-42DB-90D2-9DC3E9070B51}    2010-05-12 10:20:12:326-0400    1    162    101    {D7089405-0438-4724-882F-6A67D15BA537}    102    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {4C8E490F-45A9-4EB2-ACA3-EA4BCFE34312}    2010-05-12 10:20:20:077-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Jscript 5.7 for Windows XP (KB971961) - Security Update for Microsoft Office Publisher 2003 (KB980469) - Update for Windows XP (KB932823) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443) - Security Update for Microsoft Office Web Components (KB947319) - Security Update for Microsoft Office 2003 (KB974554) - Security Update for Microsoft Office 2003 (KB975051) - Update for Windows XP (KB970430) - Security Update for Microsoft Office Outlook 2003 (KB973705)
    {DF9DAD68-F889-4B9A-BD11-109632EE8494}    2010-05-12 10:20:20:077-0400    1    162    101    {55576129-536E-40AD-921F-4611846199DE}    101    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {E877E92D-D88B-4348-AD15-E189DFBDA699}    2010-05-12 10:20:26:556-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Jscript 5.7 for Windows XP (KB971961) - Security Update for Microsoft Office Publisher 2003 (KB980469) - Update for Windows XP (KB932823) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443) - Security Update for Internet Explorer 7 for Windows XP (KB938127) - Security Update for Microsoft Office Web Components (KB947319) - Security Update for Microsoft Office 2003 (KB974554) - Security Update for Microsoft Office 2003 (KB975051) - Update for Windows XP (KB970430) - Security Update for Microsoft Office Outlook 2003 (KB973705)
    {40795A6B-7C5F-4307-B054-44647479A1B9}    2010-05-12 10:20:26:556-0400    1    162    101    {A2A1D3B3-C228-45AD-9175-566E7DD41DD1}    101    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {66CE421B-8A66-469D-AFEC-ACCAA63E25D0}    2010-05-12 10:20:33:416-0400    1    188    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Wednesday, May 12, 2010 at 11:00 AM:  - Security Update for Jscript 5.7 for Windows XP (KB971961) - Security Update for Microsoft Office Publisher 2003 (KB980469) - Update for Windows XP (KB932823) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443) - Security Update for Internet Explorer 7 for Windows XP (KB938127) - Security Update for Microsoft Office Web Components (KB947319) - Security Update for Microsoft Office 2003 (KB974554) - Security Update for Microsoft Office 2003 (KB975051) - Security Update for Windows XP (KB981349) - Update for Windows XP (KB970430) - Security Update for Microsoft Office Outlook 2003 (KB973705)
    {921EA083-AA1F-4827-8953-A425973FA20E}    2010-05-12 10:20:33:416-0400    1    162    101    {2D7E06C5-3D12-4A9D-A9B5-6A7CB05A2798}    102    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {A77C6843-168B-4AC7-BB35-89C2FC2B8343}    2010-05-12 11:01:08:608-0400    1    190    101    {D7089405-0438-4724-882F-6A67D15BA537}    102    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Jscript 5.7 for Windows XP (KB971961)
    {589E2787-3AF3-4EFA-96C6-2E9E435C9F05}    2010-05-12 11:01:34:535-0400    1    190    101    {5277AD17-D673-4094-9031-EBC74DB0D9A2}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office Publisher 2003 (KB980469)
    {C8ACF1AE-B6A9-4E83-BE84-D979D6D8443B}    2010-05-12 11:01:44:910-0400    1    191    101    {55576129-536E-40AD-921F-4611846199DE}    101    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Update for Windows XP (KB932823)
    {670E752B-50C2-4041-8C18-F347A55C20DA}    2010-05-12 11:02:04:939-0400    1    190    101    {9D23842D-BD64-481A-8B8A-5BA8CD2A2D7B}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office PowerPoint 2003 (KB976881)
    {6E183849-D6F9-4337-A009-6827824870DA}    2010-05-12 11:02:13:591-0400    1    191    101    {51C4DF3E-7F6F-4AC4-BD2F-B1F5CF9EB3CD}    101    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Update for Windows XP (KB971737)
    {F6FDF908-F324-4247-97A3-60C3CE8A2BF9}    2010-05-12 11:02:37:165-0400    1    190    101    {B8D94C42-A29A-46CA-B896-BC0A502E64B8}    102    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office 2003 (KB972580)
    {6CCC6F59-C8F3-4BA3-89AA-885AC8AEEBA7}    2010-05-12 11:02:56:753-0400    1    190    101    {CA67A850-6126-4597-B94B-C17DB71506AC}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office 2003 (KB951535)
    {80EDE4BB-AEF2-453E-93CD-7D37E8E48450}    2010-05-12 11:03:56:759-0400    1    190    101    {5DF5C48F-6F78-4B0C-B56D-5F378313B1BF}    103    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office Excel 2003 (KB978474)
    {60329357-3444-4C1E-89A1-BD8A54DFDD10}    2010-05-12 11:04:13:824-0400    1    190    101    {66BD9792-6981-44FD-B235-0353CFBC843C}    100    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office Word 2003 (KB973443)
    {BB9BF786-487C-4653-AF20-8052454ADC2F}    2010-05-12 11:04:21:445-0400    1    190    101    {A2A1D3B3-C228-45AD-9175-566E7DD41DD1}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Internet Explorer 7 for Windows XP (KB938127)
    {578D481E-04ED-4B0C-BE39-7B88385FA996}    2010-05-12 11:04:44:088-0400    1    190    101    {8AACF2BF-68AA-4C90-B606-D4CF5770A970}    105    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office Web Components (KB947319)
    {9B3C77E4-DF81-416A-9146-FB8A76FD81AA}    2010-05-12 11:05:03:125-0400    1    190    101    {069D43C3-3E28-4BC5-9CE6-489C1F0A57ED}    101    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office 2003 (KB974554)
    {CC9CA4F0-939A-40F6-95B9-6F3DD03FA99B}    2010-05-12 11:05:19:268-0400    1    190    101    {C91B2EC4-97FA-4C1C-8C59-F18A091E55E7}    102    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office 2003 (KB975051)
    {62E63119-65E6-4FC4-A967-6CF3AAB87997}    2010-05-12 11:05:26:509-0400    1    190    101    {2D7E06C5-3D12-4A9D-A9B5-6A7CB05A2798}    102    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows XP (KB981349)
    {1DDCAA94-EB6A-4140-A223-2528F6739B82}    2010-05-12 11:05:47:379-0400    1    191    101    {4F8EDCD7-68BF-4AC4-B6DE-9617BFFD0B97}    101    0    AutomaticUpdates    Success    Content Install    Installation successful and restart required for the following update: Update for Windows XP (KB970430)
    {C4596337-4878-491E-9E9A-3142B6D2EC4D}    2010-05-12 11:06:07:247-0400    1    190    101    {D0B67DE5-A5DE-492A-AF7D-827034E628E4}    102    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Microsoft Office Outlook 2003 (KB973705)
    {078F52CB-F577-4CAF-A484-E123F0DD2540}    2010-05-12 11:06:07:367-0400    1    194    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Restart Required: To complete the installation of the following updates, the computer will be restarted within 5 minutes:  - Security Update for Jscript 5.7 for Windows XP (KB971961) - Security Update for Microsoft Office Publisher 2003 (KB980469) - Update for Windows XP (KB932823) - Security Update for Microsoft Office PowerPoint 2003 (KB976881) - Update for Windows XP (KB971737) - Security Update for Microsoft Office 2003 (KB972580) - Security Update for Microsoft Office 2003 (KB951535) - Security Update for Microsoft Office Excel 2003 (KB978474) - Security Update for Microsoft Office Word 2003 (KB973443) - Security Update for Internet Explorer 7 for Windows XP (KB938127) - Security Update for Microsoft Office Web Components (KB947319) - Security Update for Microsoft Office 2003 (KB974554) - Security Update for Microsoft Office 2003 (KB975051) - Security Update for Windows XP (KB981349) - Update for Windows XP (KB970430) - Security Update for Microsoft Office Outlook 2003 (KB973705)
    {7239CA61-62BF-4381-80F2-70B04D14436B}    2010-05-12 11:16:33:508-0400    1    202    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Reboot completed.
    {C662B3DF-365C-453F-AE0D-EBB6713CF24D}    2010-05-12 11:33:49:698-0400    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    {CB54A23A-9020-481B-8964-D6C6DCD18D9F}    2010-05-12 11:33:49:698-0400    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.
    {45461154-3F94-4D16-AA44-A3A3D61A1D45}    2010-05-12 12:16:05:914-0400    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    {9239F10F-954E-4392-8987-DA764B61665A}    2010-05-12 12:16:05:914-0400    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.
    {8C65397C-D823-41DC-91F1-655826DD2981}    2010-05-13 09:19:59:338-0400    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    {391D5EBB-2D1F-4EAD-B56C-E7A5B814E122}    2010-05-13 09:19:59:338-0400    1

     


    Thursday, May 13, 2010 7:08 PM
  • And here is softwaredistribution.log from my upstream.


    2010-05-11 21:40:42.954 UTC    Warning    WsusService.23    EmailNotificationAgent.WakeUpWorkerThreadProc    Exception occurred when sending email of type NewSync: System.Data.SqlClient.SqlException: A severe error occurred on the current command.  The results, if any, should be discarded.
    A severe error occurred on the current command.  The results, if any, should be discarded.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlDataReader.HasMoreResults()
       at System.Data.SqlClient.SqlDataReader.NextResult()
       at Microsoft.UpdateServices.Internal.MultipleResultSetsSPHandler.ExecuteStoredProcedure(DBConnection connection)
       at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds)
       at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPMultipleResultSets(String spName, DBParameterCollection args, Type[] resultTypes)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPCompleteUpdatesResult(String spName, DBParameterCollection args)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
       at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
       at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdates(UpdateScope searchScope)
       at Microsoft.UpdateServices.Internal.EmailReport.GetNewUpdatesReportEmailHtml(String culture)
       at Microsoft.UpdateServices.Internal.EmailReport.CreateEmailContent(EmailNotificationType type, String culture)
       at Microsoft.UpdateServices.Internal.EmailNotificationAgent.WakeUpWorkerThreadProc()
    2010-05-11 21:40:43.345 UTC    Info    WsusService.23    EmailNotificationAgent.WakeUpWorkerThreadProc    Email Notification Agent Finished
    2010-05-11 21:40:43.360 UTC    Info    WsusService.9    MicrosoftUpdateRollup.ReportEvents    Rolling up 2 events.
    2010-05-11 21:40:44.001 UTC    Info    WsusService.9    SusService.ValidateServerCertificate    CheckValidationResult Succeeds: CertOK
    2010-05-11 21:40:44.267 UTC    Info    WsusService.9    RollupEventReader.SetLastRollupComplete    Finished Rollup.  Setting time anchor in local DB as 5/11/2010 9:40:35 PM
    2010-05-11 21:41:06.970 UTC    Info    w3wp.1    ServerImplementation.UpdateCache    Database change occured; check if we need to update cache.
    2010-05-11 21:41:06.970 UTC    Info    w3wp.1    RevisionIdCache.UpdateCategoryAndRevisionIdCache    Fetching the category and revision id change for cache from database
    2010-05-11 21:41:07.001 UTC    Info    w3wp.1    RevisionIdCache.UpdateCategoryCache    Refreshing the category cache
    2010-05-11 21:41:07.001 UTC    Info    w3wp.1    RevisionIdCache.UpdateRevisionCache    Refreshing the revision cache
    2010-05-11 21:45:36.985 UTC    Info    w3wp.14    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-11 21:45:36.985 UTC    Info    w3wp.14    DependencyCache.RefreshThreadStart    read 20423 UpdateIDs from DB in 15 ms
    2010-05-12 01:48:10.110 UTC    Info    w3wp.1    CabUtilities.CheckCertificateSignature    File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402
    2010-05-12 01:48:10.110 UTC    Info    w3wp.1    WsusTestKeys.AreTestKeysAllowed    Server test key check: test keys are NOT allowed
    2010-05-12 01:48:10.110 UTC    Info    w3wp.1    CabUtilities.CheckCertificateSignature    File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402
    2010-05-12 01:48:10.110 UTC    Info    w3wp.1    WsusTestKeys.AreTestKeysAllowed    Server test key check: test keys are NOT allowed
    2010-05-12 01:48:10.595 UTC    Info    w3wp.1    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-12 01:48:10.595 UTC    Info    w3wp.14    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-12 01:48:10.595 UTC    Info    w3wp.14    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-12 01:48:10.595 UTC    Info    w3wp.12    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-12 01:48:10.595 UTC    Info    w3wp.12    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-12 01:48:10.595 UTC    Info    w3wp.14    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-12 01:48:10.595 UTC    Info    w3wp.14    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2010-05-12 01:48:10.595 UTC    Info    w3wp.14    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2010-05-12 01:48:10.595 UTC    Info    w3wp.14    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2010-05-12 01:48:17.126 UTC    Warning    w3wp.1    DBConnection.OnReceivingInfoMessage     The join order has been enforced because a local join hint is used.
    2010-05-12 01:51:41.985 UTC    Info    WsusService.8    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-12 01:51:41.985 UTC    Warning    WsusService.8    DBConnection.OnReceivingInfoMessage     The join order has been enforced because a local join hint is used.
    2010-05-12 14:00:01.579 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo:
    2010-05-12 14:00:01.579 UTC    Info    WsusService.22    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent
    2010-05-12 14:00:01.579 UTC    Info    WsusService.18    EmailNotificationAgent.WakeUpWorkerThreadProc    Email Notification Agent Starting
    2010-05-12 14:00:01.735 UTC    Warning    WsusService.18    DBConnection.OnReceivingInfoMessage     The join order has been enforced because a local join hint is used.
    2010-05-12 14:00:02.017 UTC    Warning    WsusService.18    DBConnection.OnReceivingInfoMessage     The join order has been enforced because a local join hint is used.
    2010-05-12 14:00:02.251 UTC    Info    WsusService.18    EmailNotificationAgent.WakeUpWorkerThreadProc    Begin sending email of notification type Summary.
    2010-05-12 14:00:02.329 UTC    Info    WsusService.18    EmailNotificationAgent.WakeUpWorkerThreadProc    End of sending email notification of type Summary.
    2010-05-12 14:00:02.329 UTC    Info    WsusService.18    EmailNotificationAgent.WakeUpWorkerThreadProc    Email Notification Agent Finished
    2010-05-12 14:15:50.892 UTC    Info    w3wp.18    ThreadEntry    ISAPIRuntime.ProcessRequest
    2010-05-12 14:15:50.892 UTC    Warning    w3wp.18    DBConnection.OnReceivingInfoMessage     The join order has been enforced because a local join hint is used.
    2010-05-12 21:40:27.798 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo:
    2010-05-12 21:40:27.798 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-12 21:40:27.814 UTC    Info    WsusService.23    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
    2010-05-12 21:40:27.814 UTC    Info    WsusService.23    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-12 21:40:27.814 UTC    Info    WsusService.11    CatalogSyncAgentCore.SyncUpdatesOutsideSubscription    sync'ing 0 updates with catalog site flag
    2010-05-12 21:40:27.814 UTC    Info    WsusService.11    EventLogEventReporter.ReportEvent    EventId=381,Type=Information,Category=Synchronization,Message=A scheduled synchronization was started.
    2010-05-12 21:40:27.829 UTC    Info    WsusService.11    AuthorizationManager.GetUpstreamServerUriHeader    Found config says USS is MU site
    2010-05-12 21:40:27.845 UTC    Info    WsusService.11    ServerSyncLib.GetWebServiceProxyInternal    Found config says USS is MU site
    2010-05-12 21:40:27.845 UTC    Info    WsusService.11    AuthorizationManager.GetUpstreamServerUriHeader    Found config says USS is MU site
    2010-05-12 21:40:27.845 UTC    Info    WsusService.11    CatalogSyncAgentCore.ExecuteSyncProtocol    Server ID is 4c4420eb-3019-43c8-9e9c-fb8aecc4afc1
    2010-05-12 21:40:27.939 UTC    Info    WsusService.11    SusService.ValidateServerCertificate    CheckValidationResult Succeeds: CertOK
    2010-05-12 21:40:28.017 UTC    Info    WsusService.11    CatalogSyncAgentCore.SyncConfigUpdatesFromUSS    Category Sync: Filter: <filter SyncAnchor="12643149,2010-05-11 21:40:34.526" GetConfig="1"></filter>
    2010-05-12 21:40:28.032 UTC    Info    WsusService.11    CatalogSyncAgentCore.SyncConfigUpdatesFromUSS    Need 0 config updates, 0 are new
    2010-05-12 21:40:28.032 UTC    Info    WsusService.11    CatalogSyncAgentCore.SyncConfigUpdatesFromUSS    Category Sync: New Config Anchor: 12646683,2010-05-12 21:40:37.396
    2010-05-12 21:40:28.048 UTC    Info    WsusService.11    CatalogSyncAgentCore.ExecuteSyncProtocol    Catalog Sync: Filter: <filter SyncAnchor="12643149,2010-05-11 21:40:34.557"><CategoryList><category delta="1" value="558f4bc3-4827-49e1-accf-ea79fd72d4c9" /><category delta="1" value="6248b8b1-ffeb-dbd9-887a-2acf53b09dfe" /><category delta="1" value="1403f223-a63f-f572-82ba-c92391218055" /><category delta="1" value="041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591" /><category delta="1" value="5312e4f1-6372-442d-aeb2-15f2132c9bd7" /><category delta="1" value="8508af86-b85e-450f-a518-3b6f8f204eea" /><category delta="1" value="8c3fcc84-7410-4a95-8b89-a166a0190486" /><category delta="1" value="cb263e3f-6c5a-4b71-88fa-1706f9549f51" /><category delta="1" value="e88a19fb-a847-4e3d-9ae2-13c2b84f58a6" /></CategoryList><UCList><updateclassification delta="1" value="e6cf1350-c01b-414d-a61f-263d14d133b4" /><updateclassification delta="1" value="b54e7d24-7add-428f-8b75-90a396fa584f" /><updateclassification delta="1" value="0fa1201d-4330-4fa8-8ae9-b877473b6441" /><updateclassification delta="1" value="68c5b0a3-d1a6-4553-ae49-01d3a7827828" /><updateclassification delta="1" value="b4832bd8-e735-4761-8daf-37f882276dab" /><updateclassification delta="1" value="28bc880e-0592-4cbf-8f95-c79b17911d5f" /><updateclassification delta="1" value="cd5ffd1e-e932-4e3a-bf74-18bf0b1bbd83" /><updateclassification delta="1" value="e0789628-ce08-4437-be74-2495b842f43b" /></UCList><languageList><language delta="1" value="1033" /></languageList></filter>
    2010-05-12 21:40:28.064 UTC    Info    WsusService.11    CatalogSyncAgentCore.ExecuteSyncProtocol    Catalog Sync: New Anchor: 12646683,2010-05-12 21:40:37.442
    2010-05-12 21:40:28.392 UTC    Info    WsusService.11    CatalogSyncAgentCore.ExecuteSyncProtocol    Need 4 updates, 4 are new
    2010-05-12 21:40:28.907 UTC    Change    WsusService.11    DBConnection.OnReceivingInfoMessage    Deleted deployment(Install) of Update for Microsoft Office Outlook 2003 Junk Email Filter (KB981432) by WUS Server UpdateID:4F22B370-1113-4492-98DF-8495A67ECEF3 Revision Number:101 TargetGroup:All Computers
    2010-05-12 21:40:29.142 UTC    Change    WsusService.11    DBConnection.OnReceivingInfoMessage    Deleted deployment(Install) of Update for Microsoft Office Outlook 2007 Junk Email Filter (KB981433) by WUS Server UpdateID:DCC85A06-DEF9-487C-9592-61A921E7E402 Revision Number:101 TargetGroup:All Computers
    2010-05-12 21:40:29.142 UTC    Info    WsusService.11    CatalogSyncAgentCore.ImportMultipleUpdates    Imported 4/4 updates in 1 iterations; 0 will be retried
    2010-05-12 21:40:29.142 UTC    Info    WsusService.11    CatalogSyncAgentCore.GetUpdateDataInChunksAndImport    0 updates to go
    2010-05-12 21:40:29.142 UTC    Info    WsusService.11    CatalogSyncAgentCore.ExecuteSyncProtocol    Total actually inserted updates: 4
    2010-05-12 21:40:29.142 UTC    Change    WsusService.11    AdminDataAccess.ExecuteSPResumeAllDownloads    Downloading retried
    2010-05-12 21:40:29.157 UTC    Info    WsusService.11    CatalogSyncAgentCore.UpdateSyncResultAndGenerateReportingEvent    CatalogSyncThreadProcess: report subscription succeeded
    2010-05-12 21:40:29.157 UTC    Info    WsusService.11    EventLogEventReporter.ReportEvent    EventId=384,Type=Information,Category=Synchronization,Message=Synchronization completed successfully.
    2010-05-12 21:40:29.157 UTC    Info    WsusService.20    CatalogSyncAgent.WaitUntilSyncFinishedOrCancelled    Agent signalled done.
    2010-05-12 21:40:29.157 UTC    Info    WsusService.20    CatalogSyncAgent.SetSubscriptionStateWithRetry    Firing event SyncFinish...
    2010-05-12 21:40:29.157 UTC    Info    WsusService.20    CatalogSyncAgent.WakeUpWorkerThreadProc    Found no more jobs. CatalogSyncAgent quits but will run rollup before terminating ...
    2010-05-12 21:40:29.157 UTC    Info    WsusService.20    CatalogSyncAgent.UpdateServerHealthStatusBasedOnError    ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
    2010-05-12 21:40:31.829 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-12 21:40:31.829 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-12 21:40:31.829 UTC    Info    w3wp.19    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-12 21:40:31.829 UTC    Info    w3wp.19    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-12 21:40:31.829 UTC    Info    w3wp.8    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-12 21:40:31.845 UTC    Info    w3wp.8    AuthorizationManager.GetUpstreamServerUriHeader    Found config says USS is MU site
    2010-05-12 21:40:31.845 UTC    Info    w3wp.8    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-12 21:40:31.845 UTC    Info    w3wp.14    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-12 21:40:31.845 UTC    Info    w3wp.8    AuthorizationManager.GetUpstreamServerUriHeader    Found config says USS is MU site
    2010-05-12 21:40:31.860 UTC    Info    w3wp.14    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-12 21:40:31.860 UTC    Info    w3wp.20    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-12 21:40:31.860 UTC    Info    w3wp.20    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-12 21:40:31.907 UTC    Info    w3wp.5    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-12 21:40:31.923 UTC    Info    w3wp.5    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-12 21:40:31.923 UTC    Info    w3wp.21    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-12 21:40:31.923 UTC    Info    w3wp.21    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-12 21:40:31.923 UTC    Info    w3wp.21    RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler    Get event ConfigurationChange from dispatchmanager
    2010-05-12 21:40:31.923 UTC    Info    w3wp.21    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2010-05-12 21:40:31.923 UTC    Info    w3wp.21    DeploymentChangeNotification.InternalEventHandler    deployment change event received
    2010-05-12 21:40:31.923 UTC    Info    w3wp.21    RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler    Get event DeploymentChange from dispatchmanager
    2010-05-12 21:40:32.814 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: RollupAgent, EventInfo:
    2010-05-12 21:40:32.814 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo:
    2010-05-12 21:40:32.814 UTC    Info    WsusService.22    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
    2010-05-12 21:40:32.814 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-12 21:40:32.814 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-12 21:40:32.814 UTC    Info    WsusService.22    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent
    2010-05-12 21:40:32.829 UTC    Info    WsusService.3    EmailNotificationAgent.WakeUpWorkerThreadProc    Email Notification Agent Starting
    2010-05-12 21:40:32.829 UTC    Info    WsusService.22    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-12 21:40:33.204 UTC    Info    WsusService.3    EmailNotificationAgent.WakeUpWorkerThreadProc    Begin sending email of notification type NewSync.
    2010-05-12 21:40:33.314 UTC    Info    WsusService.3    EmailNotificationAgent.WakeUpWorkerThreadProc    End of sending email notification of type NewSync.
    2010-05-12 21:40:33.314 UTC    Info    WsusService.3    EmailNotificationAgent.WakeUpWorkerThreadProc    Email Notification Agent Finished
    2010-05-12 21:40:34.126 UTC    Info    WsusService.17    RollupEventReporter.BuildReportingServiceUrl    Found config says USS is MU site
    2010-05-12 21:40:34.470 UTC    Info    WsusService.17    MicrosoftUpdateRollup.ReportEvents    Rolling up 2 events.
    2010-05-12 21:40:34.829 UTC    Info    WsusService.17    SusService.ValidateServerCertificate    CheckValidationResult Succeeds: CertOK
    2010-05-12 21:40:34.985 UTC    Info    WsusService.17    RollupEventReader.SetLastRollupComplete    Finished Rollup.  Setting time anchor in local DB as 5/12/2010 9:40:29 PM
    2010-05-12 21:41:01.923 UTC    Info    w3wp.1    ServerImplementation.UpdateCache    Database change occured; check if we need to update cache.
    2010-05-12 21:41:01.923 UTC    Info    w3wp.1    RevisionIdCache.UpdateCategoryAndRevisionIdCache    Fetching the category and revision id change for cache from database
    2010-05-12 21:41:01.954 UTC    Info    w3wp.1    RevisionIdCache.UpdateCategoryCache    Refreshing the category cache
    2010-05-12 21:41:01.954 UTC    Info    w3wp.1    RevisionIdCache.UpdateRevisionCache    Refreshing the revision cache
    2010-05-12 21:45:31.954 UTC    Info    w3wp.22    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-12 21:45:31.954 UTC    Info    w3wp.22    DependencyCache.RefreshThreadStart    read 20423 UpdateIDs from DB in 31 ms
    2010-05-13 00:02:03.845 UTC    Info    w3wp.1    ThreadEntry    ISAPIRuntime.ProcessRequest
    2010-05-13 00:02:03.845 UTC    Info    w3wp.1    WebService..cctor    Initializing Reporting WebService ProcessID = 2408, Process Start Time = 5/12/2010 7:56:43 PM, Product Version = 3.2.7600.226
    2010-05-13 00:02:05.095 UTC    Info    w3wp.1    ThreadEntry    ISAPIRuntime.ProcessRequest
    2010-05-13 00:02:05.095 UTC    Info    w3wp.1    ApiRemoting..cctor    Initializing ApiRemoting WebServiceProcessID = 2408, Process Start Time = 5/12/2010 7:56:43 PM, Product Version = 3.2.7600.226
    2010-05-13 00:02:05.501 UTC    Info    w3wp.1    ThreadEntry    ISAPIRuntime.ProcessRequest
    2010-05-13 00:02:05.501 UTC    Info    w3wp.1    ServerImplementation..ctor    Initializing ServerSyncWebService ProcessID = 2408, Process Start Time = 5/12/2010 7:56:43 PM, Product Version = 3.2.7600.226
    2010-05-13 00:02:05.532 UTC    Info    w3wp.1    RevisionIdCache.UpdateCategoryAndRevisionIdCache    Fetching the category and revision id change for cache from database
    2010-05-13 00:02:06.548 UTC    Info    w3wp.1    RevisionIdCache.UpdateCategoryCache    Refreshing the category cache
    2010-05-13 00:02:06.548 UTC    Info    w3wp.1    RevisionIdCache.UpdateRevisionCache    Refreshing the revision cache
    2010-05-13 00:02:06.595 UTC    Info    w3wp.1    DependencyCache.RefreshThreadStart    read 20423 UpdateIDs from DB in 31 ms
    2010-05-13 00:02:06.595 UTC    Info    w3wp.1    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: DeploymentChange
    2010-05-13 00:02:06.610 UTC    Info    w3wp.1    AuthorizationManager.GetUpstreamServerUriHeader    Found config says USS is MU site
    2010-05-13 00:02:06.642 UTC    Info    w3wp.5    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-13 00:02:06.642 UTC    Info    w3wp.5    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-13 00:02:06.657 UTC    Info    w3wp.5    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-13 00:02:06.720 UTC    Info    w3wp.5    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2010-05-13 00:02:06.720 UTC    Info    w3wp.5    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2010-05-13 00:02:06.720 UTC    Info    w3wp.5    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2010-05-13 00:02:06.751 UTC    Info    w3wp.7    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-13 00:02:06.751 UTC    Info    w3wp.7    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2010-05-13 00:02:06.767 UTC    Info    w3wp.7    DeploymentChangeNotification.InternalEventHandler    deployment change event received
    2010-05-13 00:02:06.923 UTC    Info    w3wp.1    CabUtilities.CheckCertificateSignature    File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402
    2010-05-13 00:02:06.923 UTC    Info    w3wp.1    WsusTestKeys.AreTestKeysAllowed    Server test key check: test keys are NOT allowed
    2010-05-13 00:02:06.923 UTC    Info    w3wp.1    CabUtilities.CheckCertificateSignature    File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402
    2010-05-13 00:02:06.923 UTC    Info    w3wp.1    WsusTestKeys.AreTestKeysAllowed    Server test key check: test keys are NOT allowed
    2010-05-13 00:02:06.939 UTC    Info    w3wp.6    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-13 00:02:06.939 UTC    Info    w3wp.6    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: DeploymentChange
    2010-05-13 00:02:06.939 UTC    Info    w3wp.6    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-13 00:02:06.939 UTC    Info    w3wp.6    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: LanguageChange
    2010-05-13 00:02:06.939 UTC    Info    w3wp.6    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: FileLocationChange
    2010-05-13 00:02:06.939 UTC    Info    w3wp.6    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: HardwareIDChange
    2010-05-13 00:02:07.720 UTC    Info    w3wp.1    ThreadEntry    ISAPIRuntime.ProcessRequest
    2010-05-13 00:02:07.720 UTC    Info    w3wp.1    SimpleAuth..ctor    Initializing SimpleAuth WebService ProcessID = 2408, Process Start Time = 5/12/2010 7:56:43 PM, Product Version = 3.2.7600.226
    2010-05-13 00:02:07.720 UTC    Info    w3wp.1    AuthorizationManager.GetUpstreamServerUriHeader    Found config says USS is MU site
    2010-05-13 00:02:07.970 UTC    Info    w3wp.8    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-13 00:02:07.970 UTC    Info    w3wp.8    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-13 00:02:08.001 UTC    Info    w3wp.8    AuthorizationManager.GetUpstreamServerUriHeader    Found config says USS is MU site
    2010-05-13 00:02:08.032 UTC    Info    w3wp.9    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-13 00:02:08.032 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-13 00:02:08.064 UTC    Info    w3wp.10    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-13 00:02:08.064 UTC    Info    w3wp.10    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-13 00:02:08.064 UTC    Info    w3wp.8    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-13 00:02:08.064 UTC    Info    w3wp.8    AuthorizationManager.GetUpstreamServerUriHeader    Found config says USS is MU site
    2010-05-13 00:02:08.079 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-13 00:02:08.110 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2010-05-13 00:02:08.110 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2010-05-13 00:02:08.110 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2010-05-13 00:02:08.392 UTC    Info    w3wp.1    ThreadEntry    ISAPIRuntime.ProcessRequest
    2010-05-13 00:02:08.392 UTC    Info    w3wp.1    DssAuthWebServiceImplementation..ctor    Initializing DssAuthWebService ProcessID = 2408, Process Start Time = 5/12/2010 7:56:43 PM, Product Version = 3.2.7600.226
    2010-05-13 00:02:08.423 UTC    Info    w3wp.1    AuthorizationManager.GetUpstreamServerUriHeader    Found config says USS is MU site
    2010-05-13 00:07:06.798 UTC    Info    w3wp.12    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-13 00:07:06.798 UTC    Info    w3wp.12    DependencyCache.RefreshThreadStart    read 20423 UpdateIDs from DB in 31 ms
    2010-05-13 01:48:05.017 UTC    Info    w3wp.1    CabUtilities.CheckCertificateSignature    File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402
    2010-05-13 01:48:05.017 UTC    Info    w3wp.1    WsusTestKeys.AreTestKeysAllowed    Server test key check: test keys are NOT allowed
    2010-05-13 01:48:05.017 UTC    Info    w3wp.1    CabUtilities.CheckCertificateSignature    File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402
    2010-05-13 01:48:05.017 UTC    Info    w3wp.1    WsusTestKeys.AreTestKeysAllowed    Server test key check: test keys are NOT allowed
    2010-05-13 01:48:07.392 UTC    Info    w3wp.1    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-13 01:48:07.392 UTC    Info    w3wp.12    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-13 01:48:07.392 UTC    Info    w3wp.12    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-13 01:48:07.392 UTC    Info    w3wp.14    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-13 01:48:07.392 UTC    Info    w3wp.14    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-13 01:48:07.407 UTC    Info    w3wp.12    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-13 01:48:07.407 UTC    Info    w3wp.12    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2010-05-13 01:48:07.407 UTC    Info    w3wp.12    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2010-05-13 01:48:07.407 UTC    Info    w3wp.12    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2010-05-13 14:00:01.814 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo:
    2010-05-13 14:00:01.814 UTC    Info    WsusService.21    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent
    2010-05-13 14:00:01.814 UTC    Info    WsusService.23    EmailNotificationAgent.WakeUpWorkerThreadProc    Email Notification Agent Starting
    2010-05-13 14:00:02.392 UTC    Info    WsusService.23    EmailNotificationAgent.WakeUpWorkerThreadProc    Begin sending email of notification type Summary.
    2010-05-13 14:00:02.407 UTC    Info    WsusService.23    EmailNotificationAgent.WakeUpWorkerThreadProc    End of sending email notification of type Summary.
    2010-05-13 14:00:02.423 UTC    Info    WsusService.23    EmailNotificationAgent.WakeUpWorkerThreadProc    Email Notification Agent Finished

    Thanks again for all your help




    Thursday, May 13, 2010 7:14 PM
  • Hmmm....

    2010-05-13 00:02:08.423 UTC    Info    w3wp.1    AuthorizationManager.GetUpstreamServerUriHeader    Found config says USS is MU site

    Please double check the upstream server configuration for your replica server(s) and confirm that they are actually pointed to the upstream server.

    Pointing the downstream servers at MU (effectively making them autonomous upstream servers), would create the exact symptoms you are observing, namely: successful server synchronizations with no reporting rollup data at the upstream server.

    Also....

    2010-05-13 01:48:05.017 UTC    Info    w3wp.1    CabUtilities.CheckCertificateSignature    File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402

    You'll want to verify that your WSUS Servers have the 'Add/Remove Windows Components' option for "Update Root Certificates" marked as enabled, and that these servers do have Internet access so that those root certificates can be updated automatically by the OS.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, May 14, 2010 4:44 AM
    Moderator
  • Please double check the upstream server configuration for your replica server(s) and confirm that they are actually pointed to the upstream server.

    Pointing the downstream servers at MU (effectively making them autonomous upstream servers), would create the exact symptoms you are observing, namely: successful server synchronizations with no reporting rollup data at the upstream server.

     

    -from my downstream, options->update source and proxy-> Sync from another wsus server-> Servername:my server's fqdn.  port number: 8530. ->box is checked for "this server is a replica of the upstream server."  ->  little info bar at the bottom of this window says "options disabled because this server is a replica server".

    Also, please keep in mind that it was working correctly until I ran the cleanup wizard.  *I litteraly ran the wizard, then refreshed my console, and they were gone. 

    You'll want to verify that your WSUS Servers have the 'Add/Remove Windows Components' option for "Update Root Certificates" marked as enabled, and that these servers do have Internet access so that those root certificates can be updated automatically by the OS.

     

    Yes, control panel->add remove progs -> add remove win comp -> update root certificates is checked.  for both the upstream and downstream. 

     

    Pointing the downstream servers at MU (effectively making them autonomous upstream servers), 

    I have no knowledge of this configuration, nor do I even know what autonomous or MU mean?

     

     

     

    Friday, May 14, 2010 2:26 PM
  • have Internet access so that those root certificates can be updated automatically by the OS.


    yes, both have internet access

    Friday, May 14, 2010 2:28 PM
  • I was reminded today there is one other scenario which can interfere with correct reporting rollup . . .

    From the section Choose a Type of WSUS Deployment in the WSUS Deployment Guide:

     

    Important
    • Confirm that the system time on the upstream and downstream servers is the same. Downstream servers roll up information to their upstream server immediately after they synchronize. If there is difference in the system time between servers that is greater than one minute, the rollup will fail and the downstream server results will not be rolled up to the upstream server.

    You need to confirm that the time zones are correct on all WSUS servers, that the current Daylight Savings Time updates have been properly installed on all WSUS servers, and that the MINUTE value on all servers is the same. If all servers are members of the same domain, they should be getting time synchronization from the Domain Controller(s) and this should not be an issue. If,  however, they're not in the same domain, this is a very likely possibility.

     


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Monday, May 17, 2010 4:28 PM
    Moderator
  • As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.

    If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks!

    Friday, May 21, 2010 9:07 AM
    Moderator
  • Sorry for my delayed response, please do not consider this issue resolved.

     

    The time and time zone matches on both servers.  Can  you point me to the appropriate dls patches? both servers are windows server 2003 standard sp2.

     

    Friday, May 21, 2010 3:19 PM
  • The time and time zone matches on both servers.  Can  you point me to the appropriate dls patches? both servers are windows server 2003 standard sp2.
    Assuming  you have enabled the update classification "Update Rollups", then the necessary Daylight Savings Time patch(es) should already be on your WSUS server. Look for KB979306 -- last updated 2/23/2010 (which included the corrections for the changes in US DST rules which were effective the middle of March).
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, May 21, 2010 5:19 PM
    Moderator
  • Well, any other angles of attack then?

     

    Monday, May 24, 2010 8:32 PM
  • Well, any other angles of attack then?

    Well, I am curious as to how this environment we've been describing here relates to the one you just posted in the new thread that involves an autonomous WSUS v2 server that you need to convert to a replica -- if it even does -- but it would be useful to know whether it does or not.

    I have been assuming all along that your downstream server was WSUS v3, now I'm not so sure.

    Also, I noted an error in a previous question of mine. I assumed that the SoftwareDistribution.log you posted was from the downstream server (it was, after all, the synchronization behavior of the downstream server that we were interested in reviewing), thus my assumption that the DSS was misconfigured when it reported that the USS was MU. Now I see that you've posted the SoftwareDistribution.log from the USS, so that log entry is expected. To that point, however, we still need to review the SoftwareDistribution.log from the downstream server to see what is happening during that server's synchronization events.

    So let's back up, regroup, review that logfile, and then we'll proceed based on what's being logged by the downstream server during the synchronization event(s) initiated by the downstream server. Also, please clarify the specific version of WSUS installed on this downstream server -- and do you have *other* downstream servers in this environment, and if so -- are they working correctly?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Tuesday, May 25, 2010 1:36 AM
    Moderator
  • softwareupdate.log from downstream

    2010-05-28 01:48:13.000 UTC    Info    WsusService.17    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: processing new deployments
    2010-05-28 01:48:13.000 UTC    Info    WsusService.17    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: processing hidden updates
    2010-05-28 01:48:13.156 UTC    Info    WsusService.17    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: completed
    2010-05-28 01:48:13.296 UTC    Change    WsusService.17    AdminDataAccess.ExecuteSPResumeAllDownloads    Downloading retried
    2010-05-28 01:48:13.296 UTC    Info    WsusService.17    CatalogSyncAgentCore.UpdateSyncResultAndGenerateReportingEvent    CatalogSyncThreadProcess: report subscription succeeded
    2010-05-28 01:48:13.312 UTC    Info    WsusService.17    EventLogEventReporter.ReportEvent    EventId=384,Type=Information,Category=Synchronization,Message=Synchronization completed successfully.
    2010-05-28 01:48:13.312 UTC    Info    WsusService.33    CatalogSyncAgent.WaitUntilSyncFinishedOrCancelled    Agent signalled done.
    2010-05-28 01:48:13.312 UTC    Info    WsusService.33    CatalogSyncAgent.SetSubscriptionStateWithRetry    Firing event SyncFinish...
    2010-05-28 01:48:13.312 UTC    Info    WsusService.33    CatalogSyncAgent.WakeUpWorkerThreadProc    Found no more jobs. CatalogSyncAgent quits but will run rollup before terminating ...
    2010-05-28 01:48:13.328 UTC    Info    WsusService.33    CatalogSyncAgent.UpdateServerHealthStatusBasedOnError    ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
    2010-05-28 01:48:14.671 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: RollupAgent, EventInfo:
    2010-05-28 01:48:14.671 UTC    Info    WsusService.25    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
    2010-05-28 01:48:14.671 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 01:48:14.671 UTC    Info    WsusService.20    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 01:48:14.671 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 01:48:15.453 UTC    Info    w3wp.10    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 01:48:15.453 UTC    Info    w3wp.19    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 01:48:15.453 UTC    Info    w3wp.19    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 01:48:15.453 UTC    Info    w3wp.10    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 01:48:15.453 UTC    Info    w3wp.11    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-28 01:48:15.468 UTC    Info    w3wp.22    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 01:48:15.468 UTC    Info    w3wp.26    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 01:48:15.468 UTC    Info    w3wp.16    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 01:48:15.468 UTC    Info    w3wp.15    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 01:48:15.468 UTC    Info    w3wp.15    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 01:48:15.468 UTC    Info    w3wp.16    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 01:48:15.468 UTC    Info    w3wp.26    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 01:48:15.468 UTC    Info    w3wp.22    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 01:48:15.484 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 01:48:15.484 UTC    Info    w3wp.16    ChangeNotificationDispatcher.InternalEventHandler    Get event ConfigurationChange from dispatchmanager
    2010-05-28 01:48:15.484 UTC    Info    w3wp.14    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 01:48:15.484 UTC    Info    w3wp.16    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2010-05-28 01:48:15.484 UTC    Info    w3wp.14    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 01:48:15.484 UTC    Info    w3wp.21    Client.OnConfigurationChange    Creating a new ClientImplementation because the DB configuration changed
    2010-05-28 01:48:15.500 UTC    Info    w3wp.14    RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler    Get event ConfigurationChange from dispatchmanager
    2010-05-28 01:48:15.500 UTC    Info    w3wp.16    ChangeNotificationDispatcher.InternalEventHandler    Get event DeploymentChange from dispatchmanager
    2010-05-28 01:48:15.484 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 01:48:15.500 UTC    Info    w3wp.31    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 01:48:15.500 UTC    Info    w3wp.31    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2010-05-28 01:48:15.500 UTC    Info    w3wp.31    DeploymentChangeNotification.InternalEventHandler    deployment change event received
    2010-05-28 01:48:15.500 UTC    Info    w3wp.31    RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler    Get event DeploymentChange from dispatchmanager
    2010-05-28 01:48:45.515 UTC    Info    w3wp.6    ThreadEntry    _TimerCallback.PerformTimerCallback
    2010-05-28 01:48:45.515 UTC    Info    w3wp.1    DataAccessCache.DeploymentChange    Refreshing the syncUpdates cache
    2010-05-28 01:48:45.515 UTC    Info    w3wp.6    ServerImplementation.UpdateCache    Database change occured; check if we need to update cache.
    2010-05-28 01:48:45.531 UTC    Info    w3wp.6    RevisionIdCache.UpdateCategoryAndRevisionIdCache    Fetching the category and revision id change for cache from database
    2010-05-28 01:48:45.531 UTC    Info    w3wp.6    RevisionIdCache.UpdateCategoryCache    Refreshing the category cache
    2010-05-28 01:48:45.531 UTC    Info    w3wp.6    RevisionIdCache.UpdateRevisionCache    Refreshing the revision cache
    2010-05-28 01:51:27.843 UTC    Info    w3wp.6    ThreadEntry    ISAPIRuntime.ProcessRequest
    2010-05-28 01:51:27.859 UTC    Warning    w3wp.6    DBConnection.OnReceivingInfoMessage     The join order has been enforced because a local join hint is used.
    2010-05-28 01:53:15.953 UTC    Info    w3wp.14    DependencyCache.RefreshThreadStart    read 20241 UpdateIDs from DB in 31 ms
    2010-05-28 02:15:30.968 UTC    Change    w3wp.6    AdminDataAccess.StartSubscriptionManually    Synchronization manually started
    2010-05-28 02:15:31.859 UTC    Info    w3wp.10    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 02:15:31.859 UTC    Info    w3wp.26    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 02:15:31.859 UTC    Info    w3wp.14    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 02:15:31.859 UTC    Info    w3wp.22    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 02:15:31.859 UTC    Info    w3wp.11    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-28 02:15:31.859 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 02:15:31.859 UTC    Info    w3wp.19    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 02:15:31.875 UTC    Info    w3wp.19    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 02:15:31.859 UTC    Info    w3wp.20    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 02:15:31.875 UTC    Info    w3wp.20    ChangeNotificationDispatcher.InternalEventHandler    Get event ConfigurationChange from dispatchmanager
    2010-05-28 02:15:31.875 UTC    Info    w3wp.23    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 02:15:31.875 UTC    Info    w3wp.21    Client.OnConfigurationChange    Creating a new ClientImplementation because the DB configuration changed
    2010-05-28 02:15:31.890 UTC    Info    w3wp.23    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 02:15:31.890 UTC    Info    w3wp.23    RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler    Get event ConfigurationChange from dispatchmanager
    2010-05-28 02:15:31.937 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo:
    2010-05-28 02:15:31.937 UTC    Info    WsusService.21    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
    2010-05-28 02:15:31.937 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 02:15:31.937 UTC    Info    WsusService.38    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 02:15:31.953 UTC    Info    WsusService.24    EventLogEventReporter.ReportEvent    EventId=382,Type=Information,Category=Synchronization,Message=A manual synchronization was started.
    2010-05-28 02:15:31.968 UTC    Info    WsusService.24    CatalogSyncAgentCore.ExecuteSyncProtocol    Server ID is 31adc708-c4f1-4374-a4c3-c19c2da57473
    2010-05-28 02:15:32.640 UTC    Change    WsusService.24    AdminDataAccess.ExecuteSPSetConfiguration    WSUS configuration has been changed
    2010-05-28 02:15:32.640 UTC    Info    WsusService.24    CatalogSyncAgentCore.SyncConfigUpdatesFromUSS    Category Sync: Filter: <filter SyncAnchor="25560,2010-05-28 01:47:40.843" GetConfig="1"></filter>
    2010-05-28 02:15:32.765 UTC    Info    WsusService.24    CatalogSyncAgentCore.SyncConfigUpdatesFromUSS    Need 0 config updates, 0 are new
    2010-05-28 02:15:32.765 UTC    Info    WsusService.24    CatalogSyncAgentCore.SyncConfigUpdatesFromUSS    Category Sync: New Config Anchor: 25571,2010-05-28 02:15:02.656
    2010-05-28 02:15:32.781 UTC    Info    WsusService.24    CatalogSyncAgentCore.ExecuteSyncProtocol    Catalog Sync: Filter: <filter SyncAnchor="25560,2010-05-28 01:47:41.281"><languageList><language delta="1" value="1033" /></languageList></filter>
    2010-05-28 02:15:32.906 UTC    Info    WsusService.24    CatalogSyncAgentCore.ExecuteSyncProtocol    Catalog Sync: New Anchor: 25571,2010-05-28 02:15:02.921
    2010-05-28 02:15:32.906 UTC    Info    WsusService.24    CatalogSyncAgentCore.ExecuteSyncProtocol    Need 0 updates, 0 are new
    2010-05-28 02:15:32.906 UTC    Info    WsusService.24    CatalogSyncAgentCore.ExecuteSyncProtocol    Total actually inserted updates: 0
    2010-05-28 02:15:32.906 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: starting delta sync
    2010-05-28 02:15:32.906 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: anchors: "25560,2010-05-28 01:47:41.281" to "25571,2010-05-28 02:15:02.921"
    2010-05-28 02:15:33.250 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: new anchor: 25571,2010-05-28 02:15:02.921
    2010-05-28 02:15:33.250 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: target groups count: 4
    2010-05-28 02:15:33.250 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: deployments count: 4
    2010-05-28 02:15:33.250 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: deleted deployments count: 1
    2010-05-28 02:15:33.250 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: accepted EULA count: 10
    2010-05-28 02:15:33.250 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: Hidden update count: 869
    2010-05-28 02:15:33.265 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: processing target groups
    2010-05-28 02:15:33.265 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: processing accepted EULAs
    2010-05-28 02:15:33.265 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: processing deleted deployments
    2010-05-28 02:15:33.281 UTC    Change    WsusService.24    DBConnection.OnReceivingInfoMessage    Deleted deployment(Install) of Update for Microsoft Office Outlook 2003 Junk Email Filter (KB981725) UpdateID:F21EF3BC-D2D2-4E19-A3D7-BD4A6FF2E33E Revision Number:102 TargetGroup:DATUS
    2010-05-28 02:15:33.281 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: processing new deployments
    2010-05-28 02:15:36.171 UTC    Change    WsusService.24    DBConnection.OnReceivingInfoMessage    Successfully deployed deployment(Install) of Update for Root Certificates [May 2010] (KB931125) by SERVICESBASE\Administrator UpdateID:3E2FDD7E-529B-4A95-AC50-E6B1B108A33A Revision Number:100 TargetGroup:DATUS
    2010-05-28 02:15:36.250 UTC    Change    WsusService.24    DBConnection.OnReceivingInfoMessage    Successfully deployed deployment(Install) of Update for Windows XP (KB981793) by SERVICESBASE\Administrator UpdateID:B09A9A67-E9F4-4F1E-81E2-115E47E95AB4 Revision Number:100 TargetGroup:DATUS
    2010-05-28 02:15:36.296 UTC    Change    WsusService.24    DBConnection.OnReceivingInfoMessage    Successfully deployed deployment(Install) of Update for Windows XP (KB981793) by SERVICESBASE\Administrator UpdateID:B09A9A67-E9F4-4F1E-81E2-115E47E95AB4 Revision Number:100 TargetGroup:PMSTEEL
    2010-05-28 02:15:36.312 UTC    Change    WsusService.24    DBConnection.OnReceivingInfoMessage    Successfully deployed deployment(Install) of Update for Root Certificates [May 2010] (KB931125) by SERVICESBASE\Administrator UpdateID:3E2FDD7E-529B-4A95-AC50-E6B1B108A33A Revision Number:100 TargetGroup:PMSTEEL
    2010-05-28 02:15:36.312 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: processing hidden updates
    2010-05-28 02:15:36.687 UTC    Info    WsusService.24    CatalogSyncAgentCore.ReplicaSync    DeploymentSync: completed
    2010-05-28 02:15:36.687 UTC    Change    WsusService.24    AdminDataAccess.ExecuteSPResumeAllDownloads    Downloading retried
    2010-05-28 02:15:36.703 UTC    Info    WsusService.24    CatalogSyncAgentCore.UpdateSyncResultAndGenerateReportingEvent    CatalogSyncThreadProcess: report subscription succeeded
    2010-05-28 02:15:36.703 UTC    Info    WsusService.24    EventLogEventReporter.ReportEvent    EventId=384,Type=Information,Category=Synchronization,Message=Synchronization completed successfully.
    2010-05-28 02:15:36.703 UTC    Info    WsusService.26    CatalogSyncAgent.WaitUntilSyncFinishedOrCancelled    Agent signalled done.
    2010-05-28 02:15:36.718 UTC    Info    WsusService.26    CatalogSyncAgent.SetSubscriptionStateWithRetry    Firing event SyncFinish...
    2010-05-28 02:15:36.718 UTC    Info    WsusService.26    CatalogSyncAgent.WakeUpWorkerThreadProc    Found no more jobs. CatalogSyncAgent quits but will run rollup before terminating ...
    2010-05-28 02:15:36.718 UTC    Info    WsusService.26    CatalogSyncAgent.UpdateServerHealthStatusBasedOnError    ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
    2010-05-28 02:15:36.859 UTC    Info    w3wp.10    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 02:15:36.859 UTC    Info    w3wp.26    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 02:15:36.859 UTC    Info    w3wp.10    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 02:15:36.875 UTC    Info    w3wp.26    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 02:15:36.875 UTC    Info    w3wp.22    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 02:15:36.875 UTC    Info    w3wp.33    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 02:15:36.875 UTC    Info    w3wp.22    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 02:15:36.875 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 02:15:36.875 UTC    Info    w3wp.34    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 02:15:36.875 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 02:15:36.875 UTC    Info    w3wp.34    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2010-05-28 02:15:36.875 UTC    Info    w3wp.32    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 02:15:36.890 UTC    Info    w3wp.34    ChangeNotificationDispatcher.InternalEventHandler    Get event DeploymentChange from dispatchmanager
    2010-05-28 02:15:36.890 UTC    Info    w3wp.32    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 02:15:36.890 UTC    Info    w3wp.34    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 02:15:36.890 UTC    Info    w3wp.11    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-28 02:15:36.890 UTC    Info    w3wp.34    ChangeNotificationDispatcher.InternalEventHandler    Get event ConfigurationChange from dispatchmanager
    2010-05-28 02:15:36.875 UTC    Info    w3wp.35    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 02:15:36.890 UTC    Info    w3wp.21    Client.OnConfigurationChange    Creating a new ClientImplementation because the DB configuration changed
    2010-05-28 02:15:36.890 UTC    Info    w3wp.35    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2010-05-28 02:15:36.875 UTC    Info    w3wp.33    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 02:15:36.906 UTC    Info    w3wp.35    DeploymentChangeNotification.InternalEventHandler    deployment change event received
    2010-05-28 02:15:36.906 UTC    Info    w3wp.35    RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler    Get event DeploymentChange from dispatchmanager
    2010-05-28 02:15:36.906 UTC    Info    w3wp.35    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 02:15:36.906 UTC    Info    w3wp.35    RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler    Get event ConfigurationChange from dispatchmanager
    2010-05-28 02:15:36.953 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ContentSyncAgent, EventInfo:
    2010-05-28 02:15:36.953 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: RollupAgent, EventInfo:
    2010-05-28 02:15:36.953 UTC    Info    WsusService.21    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ContentSyncAgent
    2010-05-28 02:15:36.953 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 02:15:36.953 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2010-05-28 02:15:36.953 UTC    Info    WsusService.21    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
    2010-05-28 02:15:36.953 UTC    Info    WsusService.21    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2010-05-28 02:15:36.968 UTC    Info    WsusService.22    SusEventDispatcher.RegisterEventHandler    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2010-05-28 02:15:36.968 UTC    Info    WsusService.22    EventLogEventReporter.ReportEvent    EventId=361,Type=Information,Category=Synchronization,Message=Content synchronization started.
    2010-05-28 02:15:37.000 UTC    Info    WsusService.22    ContentSyncAgent.WakeUpWorkerThreadProc    ServerHealth: Updating Server Health for Component: ContentSyncAgent Running, Marking as Running
    2010-05-28 02:15:37.078 UTC    Info    WsusService.22    ContentSyncAgent.WakeUpWorkerThreadProc    Processing Item: 89c47742-33a6-4c0b-9ac5-a520234f0d6a, State: 10
    2010-05-28 02:15:37.187 UTC    Info    WsusService.22    ContentSyncAgent.Download    Item: 89c47742-33a6-4c0b-9ac5-a520234f0d6a has been submitted to BITS for Download
    2010-05-28 02:15:37.203 UTC    Info    WsusService.22    ContentSyncAgent.WakeUpWorkerThreadProc    Processing Item: 6bb9bebd-8fc3-4638-aecb-dbb596dc980b, State: 10
    2010-05-28 02:15:37.250 UTC    Info    WsusService.22    ContentSyncAgent.Download    Item: 6bb9bebd-8fc3-4638-aecb-dbb596dc980b has been submitted to BITS for Download
    2010-05-28 02:15:37.265 UTC    Info    WsusService.22    ContentSyncAgent.WakeUpWorkerThreadProc    ContentSyncAgent found no more Jobs, going to Sleep for BITS Notifications
    2010-05-28 02:15:37.265 UTC    Info    WsusService.22    ContentSyncAgent.WakeUpWorkerThreadProc    ContentSyncAgent found no more Jobs, going to Sleep for BITS Notifications
    2010-05-28 02:15:57.031 UTC    Info    WsusService.22    ContentSyncAgent.ProcessBITSNotificationQueue    ContentSyncAgent recieved Transferred Event for Item: 6bb9bebd-8fc3-4638-aecb-dbb596dc980b
    2010-05-28 02:15:57.046 UTC    Info    WsusService.22    ContentSyncAgent.ContentSyncSPFireStateMachineEvent    ContentSyncAgent firing Event: FileDownloaded for Item: 6bb9bebd-8fc3-4638-aecb-dbb596dc980b
    2010-05-28 02:15:57.171 UTC    Info    WsusService.22    ContentSyncAgent.ContentSyncSPFireStateMachineEvent    ContentSyncAgent firing Event: FileVerified for Item: 6bb9bebd-8fc3-4638-aecb-dbb596dc980b
    2010-05-28 02:15:57.328 UTC    Info    WsusService.22    EventLogEventReporter.ReportEvent    EventId=366,Type=Information,Category=Synchronization,Message=Content file download succeeded. Digest:  Source File: /Content/4B/E1363FB1D582B860C3E25B2BBFBC0B7F38A8B44B.exe Destination File: c:\Program Files\Update Services\WsusContent\4B\E1363FB1D582B860C3E25B2BBFBC0B7F38A8B44B.exe.
    2010-05-28 02:15:57.343 UTC    Info    WsusService.22    ContentSyncAgent.ProcessBITSNotificationQueue    ContentSyncAgent recieved Transferred Event for Item: 89c47742-33a6-4c0b-9ac5-a520234f0d6a
    2010-05-28 02:15:57.343 UTC    Info    WsusService.22    ContentSyncAgent.ContentSyncSPFireStateMachineEvent    ContentSyncAgent firing Event: FileDownloaded for Item: 89c47742-33a6-4c0b-9ac5-a520234f0d6a
    2010-05-28 02:15:57.375 UTC    Info    WsusService.22    ContentSyncAgent.ContentSyncSPFireStateMachineEvent    ContentSyncAgent firing Event: FileVerified for Item: 89c47742-33a6-4c0b-9ac5-a520234f0d6a
    2010-05-28 02:15:57.390 UTC    Info    WsusService.22    EventLogEventReporter.ReportEvent    EventId=366,Type=Information,Category=Synchronization,Message=Content file download succeeded. Digest:  Source File: /Content/3E/BB77D762C1A99A3B01BBFF8C3C9E2F1150F8E13E.exe Destination File: c:\Program Files\Update Services\WsusContent\3E\BB77D762C1A99A3B01BBFF8C3C9E2F1150F8E13E.exe.
    2010-05-28 02:15:57.390 UTC    Info    WsusService.22    ContentSyncAgent.WakeUpWorkerThreadProc    ContentSyncAgent found no more Jobs, thread exitting
    2010-05-28 02:15:57.390 UTC    Info    WsusService.22    EventLogEventReporter.ReportEvent    EventId=363,Type=Information,Category=Synchronization,Message=Content synchronization succeeded.
    2010-05-28 02:15:57.406 UTC    Info    WsusService.22    ContentSyncAgent.WakeUpWorkerThreadProc    ServerHealth: Updating Server Health for Component: ContentSyncAgent, Marking as Not Running
    2010-05-28 02:16:01.875 UTC    Info    w3wp.10    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 02:16:01.875 UTC    Info    w3wp.26    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 02:16:01.890 UTC    Info    w3wp.22    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 02:16:01.890 UTC    Info    w3wp.38    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 02:16:01.890 UTC    Info    w3wp.38    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2010-05-28 02:16:01.890 UTC    Info    w3wp.38    ChangeNotificationDispatcher.InternalEventHandler    Get event DeploymentChange from dispatchmanager
    2010-05-28 02:16:01.906 UTC    Info    w3wp.9    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 02:16:01.906 UTC    Info    w3wp.39    ThreadEntry    ThreadHelper.ThreadStart
    2010-05-28 02:16:01.906 UTC    Info    w3wp.39    SusEventDispatcher.DispatchManagerWorkerThreadProc    DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2010-05-28 02:16:01.906 UTC    Info    w3wp.39    DeploymentChangeNotification.InternalEventHandler    deployment change event received
    2010-05-28 02:16:01.906 UTC    Info    w3wp.39    RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler    Get event DeploymentChange from dispatchmanager
    2010-05-28 02:16:01.968 UTC    Info    WsusService.7    SusEventDispatcher.TriggerEvent    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2010-05-28 02:16:31.906 UTC    Info    w3wp.7    DataAccessCache.DeploymentChange    Refreshing the syncUpdates cache
    2010-05-28 02:16:31.906 UTC    Info    w3wp.6    ServerImplementation.UpdateCache    Database change occured; check if we need to update cache.
    2010-05-28 02:16:31.906 UTC    Info    w3wp.6    RevisionIdCache.UpdateCategoryAndRevisionIdCache    Fetching the category and revision id change for cache from database
    2010-05-28 02:16:31.906 UTC    Info    w3wp.6    RevisionIdCache.UpdateCategoryCache    Refreshing the category cache
    2010-05-28 02:16:31.921 UTC    Info    w3wp.6    RevisionIdCache.UpdateRevisionCache    Refreshing the revision cache
    2010-05-28 02:21:01.921 UTC    Info    w3wp.35    DependencyCache.RefreshThreadStart    read 20241 UpdateIDs from DB in 16 ms

    Friday, May 28, 2010 2:33 AM
  • No, the other post is not related to this environment.  The upstream, and all downstreams are 3.0 sp2. 

     

    Friday, May 28, 2010 2:35 AM
  • At this point I can see nothing wrong with this environment and I have no particular direction to head .. so paraphrashing Jesse Stone -- when you have no direction to go, go back to the beginning.

    The WSUS Server Debug Tool has a GetConfiguration option. Please download and run that GetConfiguration tool on both of your servers and post the results.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, May 28, 2010 5:31 PM
    Moderator
  • GET CONFIGURATION FROM UPSTREAM PASTED BELOW

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup
        :
        Version:3
        InstallLanguage:ENU
        ProxyPassword:
        SmtpUserPassword:
        VersionString:3.2.7600.226
        ConfigurationSource:0
        ServicePackLevel:2
        TargetDir:C:\Program Files\Update Services\
        InstallType:1
        EnableRemoting:1
        WsusAdministratorsSid:S-1-5-21-1800205652-624429864-1330066389-1012
        WSUSReportersSid:S-1-5-21-1800205652-624429864-1330066389-1011
        SqlServerName:SERVICESBASE\MICROSOFT##SSEE
        SqlAuthenticationMode:WindowsAuthentication
        SqlDatabaseName:SUSDB
        SqlUserName:
        SqlEncryptedPassword:
        SqlInstanceIsRemote:0
        wYukonInstalled:1
        ContentDir:E:\WSUS
        PortNumber:8530
        IISTargetWebSiteIndex:560760012
        IISTargetWebSiteCreated:True
        IISUninstallConfigFilePath:C:\Program Files\Update Services\setup\UninstallSettings.xml
        IISPreviousInstallRevision:
        IISInstallRevision:3.2.7600.226
        IIsDynamicCompression:-1
        EncryptionParam:System.Byte[]
        EncryptionKey:System.Byte[]
    <NewDataSet>
      <Table>
        <ConfigurationID>1</ConfigurationID>
        <LastConfigChange>2010-06-16T17:04:13.8130000-04:00</LastConfigChange>
        <DssAnonymousTargeting>false</DssAnonymousTargeting>
        <IsRegistrationRequired>true</IsRegistrationRequired>
        <MaxDeltaSyncPeriod>30</MaxDeltaSyncPeriod>
        <ReportingServiceUrl>https://stats.update.microsoft.com</ReportingServiceUrl>
        <ServerID>8e7bb621-3736-4d9f-9f0a-8a1f3d3ae949</ServerID>
        <AnonymousCookieExpirationTime>10080</AnonymousCookieExpirationTime>
        <SimpleTargetingCookieExpirationTime>60</SimpleTargetingCookieExpirationTime>
        <MaximumServerCookieExpirationTime>10080</MaximumServerCookieExpirationTime>
        <DssTargetingCookieExpirationTime>240</DssTargetingCookieExpirationTime>
        <EncryptionKey>x4BwpvMhLNHGrhow5A0uMTtTQb/cQPH7</EncryptionKey>
        <ServerTargeting>true</ServerTargeting>
        <SyncToMU>true</SyncToMU>
        <UpstreamServerName />
        <ServerPortNumber>80</ServerPortNumber>
        <UpstreamServerUseSSL>false</UpstreamServerUseSSL>
        <UseProxy>false</UseProxy>
        <ProxyName />
        <ProxyServerPort>80</ProxyServerPort>
        <AnonymousProxyAccess>true</AnonymousProxyAccess>
        <ProxyUserName />
        <HostOnMu>false</HostOnMu>
        <LocalContentCacheLocation>e:\WSUS\WsusContent\</LocalContentCacheLocation>
        <ServerSupportsAllLanguages>false</ServerSupportsAllLanguages>
        <LogLevel>0</LogLevel>
        <LogPath />
        <SubscriptionFailureNumberOfRetries>3</SubscriptionFailureNumberOfRetries>
        <SubscriptionFailureWaitBetweenRetriesTime>15</SubscriptionFailureWaitBetweenRetriesTime>
        <DispatchManagerPollingInterval>5</DispatchManagerPollingInterval>
        <StateMachineTransitionLoggingEnabled>false</StateMachineTransitionLoggingEnabled>
        <StateMachineTransitionErrorCaptureLength>600</StateMachineTransitionErrorCaptureLength>
        <MaxSimultaneousFileDownloads>10</MaxSimultaneousFileDownloads>
        <MUUrl>https://www.update.microsoft.com/v6</MUUrl>
        <EventLogFloodProtectTime>10</EventLogFloodProtectTime>
        <HandshakeAnchor>13619805,2010-06-18 00:36:17.797</HandshakeAnchor>
        <StatsDotNetWebServiceUri>http://localhost</StatsDotNetWebServiceUri>
        <QueueFlushTimeInMS>3000</QueueFlushTimeInMS>
        <QueueFlushCount>100</QueueFlushCount>
        <QueueRejectCount>500</QueueRejectCount>
        <SleepTimeAfterErrorInMS>30000</SleepTimeAfterErrorInMS>
        <LogDestinations>0</LogDestinations>
        <AutoRefreshDeployments>true</AutoRefreshDeployments>
        <RedirectorChangeNumber>0</RedirectorChangeNumber>
        <ImportLocalPath />
        <UseCookieValidation>true</UseCookieValidation>
        <AutoPurgeClientEventAgeThreshold>15</AutoPurgeClientEventAgeThreshold>
        <AutoPurgeServerEventAgeThreshold>90</AutoPurgeServerEventAgeThreshold>
        <AutoPurgeDetectionPeriod>12</AutoPurgeDetectionPeriod>
        <DoReportingDataValidation>true</DoReportingDataValidation>
        <DoReportingSummarization>true</DoReportingSummarization>
        <MaxNumberOfIdsToRequestDataFromUss>100</MaxNumberOfIdsToRequestDataFromUss>
        <MaxCoreUpdatesPerRequest>30</MaxCoreUpdatesPerRequest>
        <MaxExtendedUpdatesPerRequest>50</MaxExtendedUpdatesPerRequest>
        <DownloadRegulationUrl />
        <AllowProxyCredentialsOverNonSsl>false</AllowProxyCredentialsOverNonSsl>
        <LazySync>true</LazySync>
        <DownloadExpressPackages>false</DownloadExpressPackages>
        <DoServerSyncCompression>true</DoServerSyncCompression>
        <ProxyUserDomain />
        <BitsHealthScanningInterval>3600000</BitsHealthScanningInterval>
        <BitsDownloadPriorityForeground>false</BitsDownloadPriorityForeground>
        <MaxXmlPerRequest>5242880</MaxXmlPerRequest>
        <MaxXmlPerRequestInServerSync>2000000</MaxXmlPerRequestInServerSync>
        <MaxTargetComputers>30000</MaxTargetComputers>
        <MaxEventInstances>2000000</MaxEventInstances>
        <LogRolloverFileSizeInBytes>0</LogRolloverFileSizeInBytes>
        <WUSInstallType>0</WUSInstallType>
        <ReplicaMode>false</ReplicaMode>
        <AutoDeployMandatory>true</AutoDeployMandatory>
        <DeploymentChangeDeferral>30</DeploymentChangeDeferral>
        <RevisionDeletionTimeThreshold>30</RevisionDeletionTimeThreshold>
        <RevisionDeletionSizeThreshold>1024</RevisionDeletionSizeThreshold>
        <CollectClientInventory>false</CollectClientInventory>
        <DoDetailedRollup>true</DoDetailedRollup>
        <RollupResetGuid>56af3207-124c-483e-b3da-3b6712569519</RollupResetGuid>
        <UssSupportsAllLanguages>true</UssSupportsAllLanguages>
        <GetContentFromMU>false</GetContentFromMU>
        <HmDetectIntervalInSeconds>600</HmDetectIntervalInSeconds>
        <HmRefreshIntervalInSeconds>21600</HmRefreshIntervalInSeconds>
        <HmCoreDiskSpaceGreenMegabytes>500</HmCoreDiskSpaceGreenMegabytes>
        <HmCoreDiskSpaceRedMegabytes>200</HmCoreDiskSpaceRedMegabytes>
        <HmCoreCatalogSyncIntervalInDays>1</HmCoreCatalogSyncIntervalInDays>
        <HmClientsInstallUpdatesGreenPercent>10</HmClientsInstallUpdatesGreenPercent>
        <HmClientsInstallUpdatesRedPercent>25</HmClientsInstallUpdatesRedPercent>
        <HmClientsInventoryGreenPercent>2</HmClientsInventoryGreenPercent>
        <HmClientsInventoryRedPercent>5</HmClientsInventoryRedPercent>
        <HmClientsInventoryScanDiffInHours>30</HmClientsInventoryScanDiffInHours>
        <HmClientsSilentGreenPercent>10</HmClientsSilentGreenPercent>
        <HmClientsSilentRedPercent>25</HmClientsSilentRedPercent>
        <HmClientsSilentDays>30</HmClientsSilentDays>
        <DssRollupChunkSize>5000</DssRollupChunkSize>
        <MURollupOptin>False</MURollupOptin>
        <AutoRefreshDeploymentsDeclineExpired>true</AutoRefreshDeploymentsDeclineExpired>
        <ServerString>Default</ServerString>
        <HmCoreFlags>-1</HmCoreFlags>
        <HmClientsFlags>-1</HmClientsFlags>
        <HmDatabaseFlags>-1</HmDatabaseFlags>
        <HmWebServicesFlags>-1</HmWebServicesFlags>
        <ClientReportingLevel>2</ClientReportingLevel>
        <LocalPublishingMaxCabSize>384</LocalPublishingMaxCabSize>
        <DownloadRegulationWebServiceUrl />
        <LoadOdfLocally>false</LoadOdfLocally>
        <OdfFilePath />
        <HmClientsTooManyGreenPercent>80</HmClientsTooManyGreenPercent>
        <HmClientsTooManyRedPercent>90</HmClientsTooManyRedPercent>
        <ComputerDeletionTimeThreshold>30</ComputerDeletionTimeThreshold>
        <ConfigurationChangeNumber>7895</ConfigurationChangeNumber>
        <UseSeparateProxyForSsl>false</UseSeparateProxyForSsl>
        <SslProxyName />
        <SslProxyServerPort>443</SslProxyServerPort>
        <ServerSupportsAllAvailableLanguages>false</ServerSupportsAllAvailableLanguages>
      </Table>
    </NewDataSet>

    Friday, June 18, 2010 7:32 PM
  • DOWNSTREEM GETCONFIGURATION PASTED BELOW

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup
        :
        Version:3
        VersionString:3.1.6001.65
        ConfigurationSource:0
        ServicePackLevel:1
        TargetDir:c:\Program Files\Update Services\
        InstallType:1
        EnableRemoting:1
        WsusAdministratorsSid:S-1-5-21-3431154630-3226398976-816794256-1026
        WSUSReportersSid:S-1-5-21-3431154630-3226398976-816794256-1025
        SqlServerName:ADMINISTRATION\MICROSOFT##SSEE
        SqlAuthenticationMode:WindowsAuthentication
        SqlDatabaseName:SUSDB
        SqlUserName:
        SqlEncryptedPassword:
        SqlInstanceIsRemote:0
        wYukonInstalled:1
        IISInstallRevision:3.1.6001.65
        IISPreviousInstallRevision:
        IISUninstallConfigFilePath:c:\Program Files\Update Services\setup\UninstallSettings.xml
        IISTargetWebSiteCreated:True
        IISTargetWebSiteIndex:731626938
        ContentDir:C:\Program Files\Update Services
        SmtpUserPassword:
        ProxyPassword:
        PortNumber:8530
        IIsDynamicCompression:0
        EncryptionParam:System.Byte[]
        EncryptionKey:System.Byte[]
    <NewDataSet>
      <Table>
        <ConfigurationID>1</ConfigurationID>
        <LastConfigChange>2010-06-18T01:48:12.2570000-04:00</LastConfigChange>
        <DssAnonymousTargeting>false</DssAnonymousTargeting>
        <IsRegistrationRequired>true</IsRegistrationRequired>
        <MaxDeltaSyncPeriod>30</MaxDeltaSyncPeriod>
        <ReportingServiceUrl>https://stats.update.microsoft.com</ReportingServiceUrl>
        <ServerID>31adc708-c4f1-4374-a4c3-c19c2da57473</ServerID>
        <AnonymousCookieExpirationTime>10080</AnonymousCookieExpirationTime>
        <SimpleTargetingCookieExpirationTime>60</SimpleTargetingCookieExpirationTime>
        <MaximumServerCookieExpirationTime>10080</MaximumServerCookieExpirationTime>
        <DssTargetingCookieExpirationTime>240</DssTargetingCookieExpirationTime>
        <EncryptionKey>gk+x4l2kDu3eMkwoyNYmVWYXIkDI62bQ</EncryptionKey>
        <ServerTargeting>true</ServerTargeting>
        <SyncToMU>false</SyncToMU>
        <UpstreamServerName>update.dat.us</UpstreamServerName>
        <ServerPortNumber>8530</ServerPortNumber>
        <UpstreamServerUseSSL>false</UpstreamServerUseSSL>
        <UseProxy>false</UseProxy>
        <ProxyName />
        <ProxyServerPort>80</ProxyServerPort>
        <AnonymousProxyAccess>true</AnonymousProxyAccess>
        <ProxyUserName />
        <HostOnMu>false</HostOnMu>
        <LocalContentCacheLocation>c:\Program Files\Update Services\WsusContent\</LocalContentCacheLocation>
        <ServerSupportsAllLanguages>false</ServerSupportsAllLanguages>
        <LogLevel>0</LogLevel>
        <LogPath />
        <SubscriptionFailureNumberOfRetries>3</SubscriptionFailureNumberOfRetries>
        <SubscriptionFailureWaitBetweenRetriesTime>15</SubscriptionFailureWaitBetweenRetriesTime>
        <DispatchManagerPollingInterval>5</DispatchManagerPollingInterval>
        <StateMachineTransitionLoggingEnabled>false</StateMachineTransitionLoggingEnabled>
        <StateMachineTransitionErrorCaptureLength>600</StateMachineTransitionErrorCaptureLength>
        <MaxSimultaneousFileDownloads>10</MaxSimultaneousFileDownloads>
        <MUUrl>https://www.update.microsoft.com/v6</MUUrl>
        <EventLogFloodProtectTime>10</EventLogFloodProtectTime>
        <HandshakeAnchor>7895,2010-06-18 01:49:01.234</HandshakeAnchor>
        <StatsDotNetWebServiceUri>http://localhost</StatsDotNetWebServiceUri>
        <QueueFlushTimeInMS>3000</QueueFlushTimeInMS>
        <QueueFlushCount>100</QueueFlushCount>
        <QueueRejectCount>500</QueueRejectCount>
        <SleepTimeAfterErrorInMS>30000</SleepTimeAfterErrorInMS>
        <LogDestinations>0</LogDestinations>
        <AutoRefreshDeployments>true</AutoRefreshDeployments>
        <RedirectorChangeNumber>0</RedirectorChangeNumber>
        <ImportLocalPath />
        <UseCookieValidation>true</UseCookieValidation>
        <AutoPurgeClientEventAgeThreshold>15</AutoPurgeClientEventAgeThreshold>
        <AutoPurgeServerEventAgeThreshold>90</AutoPurgeServerEventAgeThreshold>
        <AutoPurgeDetectionPeriod>12</AutoPurgeDetectionPeriod>
        <DoReportingDataValidation>true</DoReportingDataValidation>
        <DoReportingSummarization>true</DoReportingSummarization>
        <MaxNumberOfIdsToRequestDataFromUss>100</MaxNumberOfIdsToRequestDataFromUss>
        <MaxCoreUpdatesPerRequest>30</MaxCoreUpdatesPerRequest>
        <MaxExtendedUpdatesPerRequest>50</MaxExtendedUpdatesPerRequest>
        <DownloadRegulationUrl />
        <AllowProxyCredentialsOverNonSsl>false</AllowProxyCredentialsOverNonSsl>
        <LazySync>true</LazySync>
        <DownloadExpressPackages>false</DownloadExpressPackages>
        <DoServerSyncCompression>true</DoServerSyncCompression>
        <ProxyUserDomain />
        <BitsHealthScanningInterval>3600000</BitsHealthScanningInterval>
        <BitsDownloadPriorityForeground>false</BitsDownloadPriorityForeground>
        <MaxXmlPerRequest>200000</MaxXmlPerRequest>
        <MaxXmlPerRequestInServerSync>2000000</MaxXmlPerRequestInServerSync>
        <MaxTargetComputers>30000</MaxTargetComputers>
        <MaxEventInstances>2000000</MaxEventInstances>
        <LogRolloverFileSizeInBytes>0</LogRolloverFileSizeInBytes>
        <WUSInstallType>0</WUSInstallType>
        <ReplicaMode>true</ReplicaMode>
        <AutoDeployMandatory>true</AutoDeployMandatory>
        <DeploymentChangeDeferral>30</DeploymentChangeDeferral>
        <RevisionDeletionTimeThreshold>30</RevisionDeletionTimeThreshold>
        <RevisionDeletionSizeThreshold>1024</RevisionDeletionSizeThreshold>
        <CollectClientInventory>false</CollectClientInventory>
        <DoDetailedRollup>true</DoDetailedRollup>
        <RollupResetGuid>56af3207-124c-483e-b3da-3b6712569519</RollupResetGuid>
        <UssSupportsAllLanguages>false</UssSupportsAllLanguages>
        <GetContentFromMU>false</GetContentFromMU>
        <HmDetectIntervalInSeconds>600</HmDetectIntervalInSeconds>
        <HmRefreshIntervalInSeconds>21600</HmRefreshIntervalInSeconds>
        <HmCoreDiskSpaceGreenMegabytes>500</HmCoreDiskSpaceGreenMegabytes>
        <HmCoreDiskSpaceRedMegabytes>200</HmCoreDiskSpaceRedMegabytes>
        <HmCoreCatalogSyncIntervalInDays>1</HmCoreCatalogSyncIntervalInDays>
        <HmClientsInstallUpdatesGreenPercent>10</HmClientsInstallUpdatesGreenPercent>
        <HmClientsInstallUpdatesRedPercent>25</HmClientsInstallUpdatesRedPercent>
        <HmClientsInventoryGreenPercent>2</HmClientsInventoryGreenPercent>
        <HmClientsInventoryRedPercent>5</HmClientsInventoryRedPercent>
        <HmClientsInventoryScanDiffInHours>30</HmClientsInventoryScanDiffInHours>
        <HmClientsSilentGreenPercent>10</HmClientsSilentGreenPercent>
        <HmClientsSilentRedPercent>25</HmClientsSilentRedPercent>
        <HmClientsSilentDays>30</HmClientsSilentDays>
        <DssRollupChunkSize>5000</DssRollupChunkSize>
        <MURollupOptin>False</MURollupOptin>
        <AutoRefreshDeploymentsDeclineExpired>true</AutoRefreshDeploymentsDeclineExpired>
        <ServerString>Default</ServerString>
        <HmCoreFlags>-1</HmCoreFlags>
        <HmClientsFlags>-1</HmClientsFlags>
        <HmDatabaseFlags>-1</HmDatabaseFlags>
        <HmWebServicesFlags>-1</HmWebServicesFlags>
        <ClientReportingLevel>2</ClientReportingLevel>
        <LocalPublishingMaxCabSize>384</LocalPublishingMaxCabSize>
        <DownloadRegulationWebServiceUrl />
        <LoadOdfLocally>false</LoadOdfLocally>
        <OdfFilePath />
        <HmClientsTooManyGreenPercent>80</HmClientsTooManyGreenPercent>
        <HmClientsTooManyRedPercent>90</HmClientsTooManyRedPercent>
        <ComputerDeletionTimeThreshold>30</ComputerDeletionTimeThreshold>
        <ConfigurationChangeNumber>37954</ConfigurationChangeNumber>
        <UseSeparateProxyForSsl>false</UseSeparateProxyForSsl>
        <SslProxyName />
        <SslProxyServerPort>443</SslProxyServerPort>
      </Table>
    </NewDataSet>

    Friday, June 18, 2010 7:37 PM
  • Well, the very first thing I noticed is that your downstream server is still WSUS v3 Service Pack 1, although this is not a contributing factor --- it does need to be upgraded.

    The second thing I note is that it appears Dynamic Compression is disabled on your upstream server, but enabled on your downstream server:

    UPSTREAM: IIsDynamicCompression:-1 / DOWNSTREAM:   IIsDynamicCompression:0

    And this is known to be problematic. See this thread [WSUS Downstream server not synchronizing - SQL Timeout] for discussion of another issue similar to this one that was traced to this issue as the root cause.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, June 18, 2010 9:30 PM
    Moderator
  • Okay,  I see that by default it should be enable with IIS 6.0.  Which is strange as this machine was built specifically to be an upstream server. 

     

    Can Dynamic Compression simply be enabled within IIS on the upstream server to attempt to resolve the problem?  How?

     

    Thank You!

     

     

    Monday, June 28, 2010 5:24 PM
  • Okay so after making that post I found instructions:

    http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/92f627a8-4ec3-480c-b0be-59a561091597.mspx?mfr=true

     

    I've checked the box for compress static, compress application was already checked, and rebooted the server. 

     

    That still leaves the question, will this work?

    Can Dynamic Compression simply be enabled within IIS on the upstream server to attempt to resolve the problem?

     

    Monday, June 28, 2010 5:32 PM
  • Okay, now that I've looked at my downstream I see that it's compress static is unchecked as well.

     

    From the article you posted above about compression it appears that the upstream needs to be enabled.  How can this issue with mis-matched compression settings be resolved?

     

    Thanks!

    Monday, June 28, 2010 5:37 PM
  • Okay, now that I've looked at my downstream I see that it's compress static is unchecked as well.

    From the article you posted above about compression it appears that the upstream needs to be enabled.  How can this issue with mis-matched compression settings be resolved?

    Since the conversation is about Dynamic Compression the setting of Compress static files is of no immediate interest. The checkbox that controls dynamic compression is Compress application files.

    I think it matters less what they're set to than it does that they are set identically. If one end of a connection attempts to compress content and the other end doesn't allow compressed content, there will not be any successful data transfer.

    The short answer to the question is that the value should be set to whatever the default installation configuration is. Looking at my Win2003/IIS6 WSUS Server, which I know is set to the installation defaults, I see that Compress application files is ENABLED and Compress static files is DISABLED. If Compress application files was checked on both systems, then this would seem to be contradictory to what the WSUSServerDebug tool displayed, and we may be back at square one.

    UPSTREAM: IIsDynamicCompression:-1 / DOWNSTREAM:   IIsDynamicCompression:0

    However, since you have now verified both checkboxes are enabled for Compress application files, I would be interested to see what the WSUSServerDebug tool now reports for this value on each server.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Tuesday, June 29, 2010 3:19 PM
    Moderator
  • the compress application check box does not seem to have any effect on what is reported under dynamiccompression of the get configuration tool. 

    It was already checked on my upstream which reports -1 disabled. switching it does not change the number.

     

    This holds true on the downsream, it reports 0 enabled and is checked.  If I uncheck it, and reboot, it still reports 0 enabled. 

    pasted below is the upstream with compress application checked.

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup
        :
        Version:3
        InstallLanguage:ENU
        ProxyPassword:
        SmtpUserPassword:
        VersionString:3.2.7600.226
        ConfigurationSource:0
        ServicePackLevel:2
        TargetDir:C:\Program Files\Update Services\
        InstallType:1
        EnableRemoting:1
        WsusAdministratorsSid:S-1-5-21-1800205652-624429864-1330066389-1012
        WSUSReportersSid:S-1-5-21-1800205652-624429864-1330066389-1011
        SqlServerName:SERVICESBASE\MICROSOFT##SSEE
        SqlAuthenticationMode:WindowsAuthentication
        SqlDatabaseName:SUSDB
        SqlUserName:
        SqlEncryptedPassword:
        SqlInstanceIsRemote:0
        wYukonInstalled:1
        ContentDir:E:\WSUS
        PortNumber:8530
        IISTargetWebSiteIndex:560760012
        IISTargetWebSiteCreated:True
        IISUninstallConfigFilePath:C:\Program Files\Update Services\setup\UninstallSettings.xml
        IISPreviousInstallRevision:
        IISInstallRevision:3.2.7600.226
        IIsDynamicCompression:-1
        EncryptionParam:System.Byte[]
        EncryptionKey:System.Byte[]
    <NewDataSet>
      <Table>
        <ConfigurationID>1</ConfigurationID>
        <LastConfigChange>2010-06-16T17:04:13.8130000-04:00</LastConfigChange>
        <DssAnonymousTargeting>false</DssAnonymousTargeting>
        <IsRegistrationRequired>true</IsRegistrationRequired>
        <MaxDeltaSyncPeriod>30</MaxDeltaSyncPeriod>
        <ReportingServiceUrl>https://stats.update.microsoft.com</ReportingServiceUrl>
        <ServerID>8e7bb621-3736-4d9f-9f0a-8a1f3d3ae949</ServerID>
        <AnonymousCookieExpirationTime>10080</AnonymousCookieExpirationTime>
        <SimpleTargetingCookieExpirationTime>60</SimpleTargetingCookieExpirationTime>
        <MaximumServerCookieExpirationTime>10080</MaximumServerCookieExpirationTime>
        <DssTargetingCookieExpirationTime>240</DssTargetingCookieExpirationTime>
        <EncryptionKey>x4BwpvMhLNHGrhow5A0uMTtTQb/cQPH7</EncryptionKey>
        <ServerTargeting>true</ServerTargeting>
        <SyncToMU>true</SyncToMU>
        <UpstreamServerName />
        <ServerPortNumber>80</ServerPortNumber>
        <UpstreamServerUseSSL>false</UpstreamServerUseSSL>
        <UseProxy>false</UseProxy>
        <ProxyName />
        <ProxyServerPort>80</ProxyServerPort>
        <AnonymousProxyAccess>true</AnonymousProxyAccess>
        <ProxyUserName />
        <HostOnMu>false</HostOnMu>
        <LocalContentCacheLocation>e:\WSUS\WsusContent\</LocalContentCacheLocation>
        <ServerSupportsAllLanguages>false</ServerSupportsAllLanguages>
        <LogLevel>0</LogLevel>
        <LogPath />
        <SubscriptionFailureNumberOfRetries>3</SubscriptionFailureNumberOfRetries>
        <SubscriptionFailureWaitBetweenRetriesTime>15</SubscriptionFailureWaitBetweenRetriesTime>
        <DispatchManagerPollingInterval>5</DispatchManagerPollingInterval>
        <StateMachineTransitionLoggingEnabled>false</StateMachineTransitionLoggingEnabled>
        <StateMachineTransitionErrorCaptureLength>600</StateMachineTransitionErrorCaptureLength>
        <MaxSimultaneousFileDownloads>10</MaxSimultaneousFileDownloads>
        <MUUrl>https://www.update.microsoft.com/v6</MUUrl>
        <EventLogFloodProtectTime>10</EventLogFloodProtectTime>
        <HandshakeAnchor>13643024,2010-07-01 00:35:46.549</HandshakeAnchor>
        <StatsDotNetWebServiceUri>http://localhost</StatsDotNetWebServiceUri>
        <QueueFlushTimeInMS>3000</QueueFlushTimeInMS>
        <QueueFlushCount>100</QueueFlushCount>
        <QueueRejectCount>500</QueueRejectCount>
        <SleepTimeAfterErrorInMS>30000</SleepTimeAfterErrorInMS>
        <LogDestinations>0</LogDestinations>
        <AutoRefreshDeployments>true</AutoRefreshDeployments>
        <RedirectorChangeNumber>0</RedirectorChangeNumber>
        <ImportLocalPath />
        <UseCookieValidation>true</UseCookieValidation>
        <AutoPurgeClientEventAgeThreshold>15</AutoPurgeClientEventAgeThreshold>
        <AutoPurgeServerEventAgeThreshold>90</AutoPurgeServerEventAgeThreshold>
        <AutoPurgeDetectionPeriod>12</AutoPurgeDetectionPeriod>
        <DoReportingDataValidation>true</DoReportingDataValidation>
        <DoReportingSummarization>true</DoReportingSummarization>
        <MaxNumberOfIdsToRequestDataFromUss>100</MaxNumberOfIdsToRequestDataFromUss>
        <MaxCoreUpdatesPerRequest>30</MaxCoreUpdatesPerRequest>
        <MaxExtendedUpdatesPerRequest>50</MaxExtendedUpdatesPerRequest>
        <DownloadRegulationUrl />
        <AllowProxyCredentialsOverNonSsl>false</AllowProxyCredentialsOverNonSsl>
        <LazySync>true</LazySync>
        <DownloadExpressPackages>false</DownloadExpressPackages>
        <DoServerSyncCompression>true</DoServerSyncCompression>
        <ProxyUserDomain />
        <BitsHealthScanningInterval>3600000</BitsHealthScanningInterval>
        <BitsDownloadPriorityForeground>false</BitsDownloadPriorityForeground>
        <MaxXmlPerRequest>5242880</MaxXmlPerRequest>
        <MaxXmlPerRequestInServerSync>2000000</MaxXmlPerRequestInServerSync>
        <MaxTargetComputers>30000</MaxTargetComputers>
        <MaxEventInstances>2000000</MaxEventInstances>
        <LogRolloverFileSizeInBytes>0</LogRolloverFileSizeInBytes>
        <WUSInstallType>0</WUSInstallType>
        <ReplicaMode>false</ReplicaMode>
        <AutoDeployMandatory>true</AutoDeployMandatory>
        <DeploymentChangeDeferral>30</DeploymentChangeDeferral>
        <RevisionDeletionTimeThreshold>30</RevisionDeletionTimeThreshold>
        <RevisionDeletionSizeThreshold>1024</RevisionDeletionSizeThreshold>
        <CollectClientInventory>false</CollectClientInventory>
        <DoDetailedRollup>true</DoDetailedRollup>
        <RollupResetGuid>56af3207-124c-483e-b3da-3b6712569519</RollupResetGuid>
        <UssSupportsAllLanguages>true</UssSupportsAllLanguages>
        <GetContentFromMU>false</GetContentFromMU>
        <HmDetectIntervalInSeconds>600</HmDetectIntervalInSeconds>
        <HmRefreshIntervalInSeconds>21600</HmRefreshIntervalInSeconds>
        <HmCoreDiskSpaceGreenMegabytes>500</HmCoreDiskSpaceGreenMegabytes>
        <HmCoreDiskSpaceRedMegabytes>200</HmCoreDiskSpaceRedMegabytes>
        <HmCoreCatalogSyncIntervalInDays>1</HmCoreCatalogSyncIntervalInDays>
        <HmClientsInstallUpdatesGreenPercent>10</HmClientsInstallUpdatesGreenPercent>
        <HmClientsInstallUpdatesRedPercent>25</HmClientsInstallUpdatesRedPercent>
        <HmClientsInventoryGreenPercent>2</HmClientsInventoryGreenPercent>
        <HmClientsInventoryRedPercent>5</HmClientsInventoryRedPercent>
        <HmClientsInventoryScanDiffInHours>30</HmClientsInventoryScanDiffInHours>
        <HmClientsSilentGreenPercent>10</HmClientsSilentGreenPercent>
        <HmClientsSilentRedPercent>25</HmClientsSilentRedPercent>
        <HmClientsSilentDays>30</HmClientsSilentDays>
        <DssRollupChunkSize>5000</DssRollupChunkSize>
        <MURollupOptin>False</MURollupOptin>
        <AutoRefreshDeploymentsDeclineExpired>true</AutoRefreshDeploymentsDeclineExpired>
        <ServerString>Default</ServerString>
        <HmCoreFlags>-1</HmCoreFlags>
        <HmClientsFlags>-1</HmClientsFlags>
        <HmDatabaseFlags>-1</HmDatabaseFlags>
        <HmWebServicesFlags>-1</HmWebServicesFlags>
        <ClientReportingLevel>2</ClientReportingLevel>
        <LocalPublishingMaxCabSize>384</LocalPublishingMaxCabSize>
        <DownloadRegulationWebServiceUrl />
        <LoadOdfLocally>false</LoadOdfLocally>
        <OdfFilePath />
        <HmClientsTooManyGreenPercent>80</HmClientsTooManyGreenPercent>
        <HmClientsTooManyRedPercent>90</HmClientsTooManyRedPercent>
        <ComputerDeletionTimeThreshold>30</ComputerDeletionTimeThreshold>
        <ConfigurationChangeNumber>8020</ConfigurationChangeNumber>
        <UseSeparateProxyForSsl>false</UseSeparateProxyForSsl>
        <SslProxyName />
        <SslProxyServerPort>443</SslProxyServerPort>
        <ServerSupportsAllAvailableLanguages>false</ServerSupportsAllAvailableLanguages>
      </Table>
    </NewDataSet>

    Thursday, July 1, 2010 4:21 PM
  • Well . . . shucks! :-/
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Thursday, July 1, 2010 6:22 PM
    Moderator
  • So, Where do we go from here?

     

     

    Thursday, July 15, 2010 1:44 PM
  • So, Where do we go from here?

    Start from scratch? My best educated guess is that the issue exists in some change that's been made to the environment.

    At this point we've already invested exponentially more hours in diagnosing the issue than it would have taken to completely rebuild it from scratch, so that is now my best (and truly, only viable) option for resolving this issue.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Thursday, July 15, 2010 5:05 PM
    Moderator
  • Ready to have your mind blown?

    I rebuilt the upstream server from scratch as suggested.  I completely rebuilt the operating system from disc, rather than copying my empty/blank win2k3 virtual machine. 

    Next, I installed IIS.  After installation I right clicked web sites chose properties->services tab and checked compress application, as it is off by default in IIS 6.0.  I did this because it's checked on my downstream, and my downstream's GetConfiguration reports 0 (checked)  ***I did this berfore WSUS installation.

    After completely installing WSUS my reporting roll-up is working all of my downstream computers are reporting their statuses and are available on the upstream! Great right?  Not so fast. 

    I thought well,.. Let's run GetConfiguration tool on the upstream now just for kicks, well and for you Lawrence, by the way thank you so much for all of your help.  IISDynamicCompression still reports a -1 (off, UnChecked!) Not matching the downstreams that are successfully syncronizing. 

    So!?  I have a feeling that my reporting rollup will begin to fail yet again, just like the last time.  I remember reading in one of your other threads, Lawrence, that it takes a few weeks for this problem to begin when the compression settings do not match.  Maybe I'm mistaken, I hope I'm mistaken, I've already put soo much time into this shotty, random result producing, disaster of a solution. That's not yet a confident solution......

    Thanks again everyone, Lawrence.  Let's leave this open so when rollup starts failing again we can um,... ask Mr. Garvin what to do.... ?

     

    Tuesday, July 20, 2010 3:12 PM
  • After installation I right clicked web sites chose properties->services tab and checked compress application, as it is off by default in IIS 6.0.
    There is nothing documented in anything ever published for the installation of WSUS on Windows Server 2003/IIS6 that I have seen that requires this setting to be enabled. If I were to make a wild guess, I'd think that some of your issues may be caused because this setting IS ENABLED.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, July 21, 2010 12:40 AM
    Moderator
  • The latest problem is that I cannot add computers to groups.  I've created groups and my options have "use update services console to add computers to groups" selected.  If I right click the computer I want, there is no change membership option. 
    Wednesday, July 21, 2010 7:50 PM
  • The latest problem is that I cannot add computers to groups.  I've created groups and my options have "use update services console to add computers to groups" selected.  If I right click the computer I want, there is no change membership option. 

    You have confirmed that you are using WSUS V3 and the account you are using to connect the console session is a member of WSUS Administrators or the local Administrators group?
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, July 21, 2010 8:33 PM
    Moderator
  • yes, 3.2, local administrator,  does the membership have to be changed from the downstream?

     

     

    Saturday, July 24, 2010 8:20 PM
  • does the membership have to be changed from the downstream?
    Well . . . yes. It has to be changed on the machine where the computer is registered.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Monday, July 26, 2010 3:32 AM
    Moderator