Windows update using WSUS high CPU at 10 minute intervals

Answered Windows update using WSUS high CPU at 10 minute intervals

  • Donnerstag, 31. Januar 2013 09:06
     
     

    Hi,

    I have an issue where servers check for updates every 10 minutes although detection frequency is set for 6 hours via group policy. When the update starts CPU goes to 100% until the process completes. Please help its driving me insane.

    WSUS Version: 3.2.7600.226

    Windows version : Windows 2003 SP2

    Please see the windowupdate.log contents below

    2013-01-31    08:39:50:772    10092    21f0    Misc    ===========  Logging initialized (build: 7.4.7600.226, tz: -0000)  ===========
    2013-01-31    08:39:50:772    10092    21f0    Misc      = Process: C:\WINDOWS\system32\cscript.exe
    2013-01-31    08:39:50:772    10092    21f0    Misc      = Module: C:\WINDOWS\system32\wuapi.dll
    2013-01-31    08:39:50:772    10092    21f0    COMAPI    -------------
    2013-01-31    08:39:50:772    10092    21f0    COMAPI    -- START --  COMAPI: Search [ClientId = <NULL>]
    2013-01-31    08:39:50:772    10092    21f0    COMAPI    ---------
    2013-01-31    08:39:50:787     936    11dc    Agent    *************
    2013-01-31    08:39:50:787     936    11dc    Agent    ** START **  Agent: Finding updates [CallerId = ]
    2013-01-31    08:39:50:787     936    11dc    Agent    *********
    2013-01-31    08:39:50:787     936    11dc    Agent      * Online = Yes; Ignore download priority = No
    2013-01-31    08:39:50:787     936    11dc    Agent      * Criteria = "IsInstalled=0 and Type='Software'"
    2013-01-31    08:39:50:787     936    11dc    Agent      * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
    2013-01-31    08:39:50:787     936    11dc    Agent      * Search Scope = {Machine}
    2013-01-31    08:39:50:787    10092    21f0    COMAPI    <<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
    2013-01-31    08:39:54:959     936    11dc    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-01-31    08:39:54:959     936    11dc    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus/ClientWebService/client.asmx
    2013-01-31    08:39:58:834     936    11dc    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2013-01-31    08:39:58:834     936    11dc    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus/ClientWebService/client.asmx
    2013-01-31    08:40:01:819     936    11dc    Agent      * Found 0 updates and 63 categories in search; evaluated appl. rules of 667 out of 1327 deployed entities
    2013-01-31    08:40:01:835     936    11dc    Agent    *********
    2013-01-31    08:40:01:835     936    11dc    Agent    **  END  **  Agent: Finding updates [CallerId = ]
    2013-01-31    08:40:01:835     936    11dc    Agent    *************
    2013-01-31    08:40:01:866    10092    2730    COMAPI    >>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
    2013-01-31    08:40:01:866    10092    2730    COMAPI      - Updates found = 0
    2013-01-31    08:40:01:866    10092    2730    COMAPI    ---------
    2013-01-31    08:40:01:866    10092    2730    COMAPI    --  END  --  COMAPI: Search [ClientId = <NULL>]
    2013-01-31    08:40:01:866    10092    2730    COMAPI    -------------
    2013-01-31    08:40:06:835     936    11dc    Report    REPORT EVENT: {E9E411F2-D036-4411-884C-F49775E5783F}    2013-01-31 08:40:01:835-0000    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0        Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    2013-01-31    08:40:06:835     936    11dc    Report    REPORT EVENT: {554670D5-56C2-4381-9D6D-948AD34E2115}    2013-01-31 08:40:01:835-0000    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0        Success    Pre-Deployment Check    Reporting client status.
    2013-01-31    08:44:07:889     936    11dc    Report    Uploading 2 events using cached cookie, reporting URL = http://wsus/ReportingWebService/ReportingWebService.asmx
    2013-01-31    08:44:07:889     936    11dc    Report    Reporter successfully uploaded 2 events.
    2013-01-31    08:49:50:228    9568    2658    Misc    ===========  Logging initialized (build: 7.4.7600.226, tz: -0000)  ===========
    2013-01-31    08:49:50:228    9568    2658    Misc      = Process: C:\WINDOWS\system32\cscript.exe
    2013-01-31    08:49:50:228    9568    2658    Misc      = Module: C:\WINDOWS\system32\wuapi.dll
    2013-01-31    08:49:50:228    9568    2658    COMAPI    -------------
    2013-01-31    08:49:50:228    9568    2658    COMAPI    -- START --  COMAPI: Search [ClientId = <NULL>]
    2013-01-31    08:49:50:228    9568    2658    COMAPI    ---------
    2013-01-31    08:49:50:260     936    11dc    Agent    *************
    2013-01-31    08:49:50:260     936    11dc    Agent    ** START **  Agent: Finding updates [CallerId = ]
    2013-01-31    08:49:50:260     936    11dc    Agent    *********
    2013-01-31    08:49:50:260     936    11dc    Agent      * Online = Yes; Ignore download priority = No
    2013-01-31    08:49:50:260     936    11dc    Agent      * Criteria = "IsInstalled=0 and Type='Software'"
    2013-01-31    08:49:50:260     936    11dc    Agent      * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
    2013-01-31    08:49:50:260     936    11dc    Agent      * Search Scope = {Machine}
    2013-01-31    08:49:50:260    9568    2658    COMAPI    <<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
    2013-01-31    08:49:53:588     936    11dc    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-01-31    08:49:53:588     936    11dc    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus/ClientWebService/client.asmx
    2013-01-31    08:49:57:338     936    11dc    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2013-01-31    08:49:57:338     936    11dc    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus/ClientWebService/client.asmx
    2013-01-31    08:50:00:572     936    11dc    Agent      * Found 0 updates and 63 categories in search; evaluated appl. rules of 667 out of 1327 deployed entities
    2013-01-31    08:50:00:588     936    11dc    Agent    *********
    2013-01-31    08:50:00:588     936    11dc    Agent    **  END  **  Agent: Finding updates [CallerId = ]
    2013-01-31    08:50:00:588     936    11dc    Agent    *************
    2013-01-31    08:50:00:619    9568    25c4    COMAPI    >>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
    2013-01-31    08:50:00:619    9568    25c4    COMAPI      - Updates found = 0
    2013-01-31    08:50:00:619    9568    25c4    COMAPI    ---------
    2013-01-31    08:50:00:619    9568    25c4    COMAPI    --  END  --  COMAPI: Search [ClientId = <NULL>]
    2013-01-31    08:50:00:619    9568    25c4    COMAPI    -------------
    2013-01-31    08:50:05:588     936    11dc    Report    REPORT EVENT: {B9795BF3-0F14-460A-A7CD-9C33C633FB83}    2013-01-31 08:50:00:588-0000    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0        Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    2013-01-31    08:50:05:588     936    11dc    Report    REPORT EVENT: {97CB56B1-E715-422D-8636-66FE7A5CBF19}    2013-01-31 08:50:00:588-0000    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0        Success    Pre-Deployment Check    Reporting client status.
    2013-01-31    08:54:06:643     936    11dc    Report    Uploading 2 events using cached cookie, reporting URL = http://wsus/ReportingWebService/ReportingWebService.asmx

Alle Antworten

  • Freitag, 1. Februar 2013 03:15
    Moderator
     
     

    Hi,

    Why are you setting the detection frequencyfor 6 hours via group policy?It can only lead to performance issue.Pls try to change back to the default value to see whether the performance can be mitigated.

    regards

    Clarence


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Sonntag, 3. Februar 2013 01:24
    Moderator
     
     Beantwortet

    Why are you setting the detection frequencyfor 6 hours via group policy?It can only lead to performance issue.Pls try to change back to the default value to see whether the performance can be mitigated.

    A 6-hour detection frequency is perfectly acceptable and will not cause performance issues. In fact, the test scenario documented in the WSUS Deployment Guide was based on 100k clients with a 7-hour detection.

    More likely the scenario here is one of external influence... a script calling the WUAgent API.

    2013-01-31    08:39:50:772    10092    21f0    Misc      = Process: C:\WINDOWS\system32\cscript.exe
    2013-01-31    08:39:50:772    10092    21f0    Misc      = Module: C:\WINDOWS\system32\wuapi.dll
    2013-01-31    08:39:50:772    10092    21f0    COMAPI    -------------
    2013-01-31    08:39:50:772    10092    21f0    COMAPI    -- START --  COMAPI: Search [ClientId = <NULL>]

    Also, based on the connection to the WSUS Server, it also seems that the WSUS server is missing some patches.

    2013-01-31    08:39:50:772    10092    21f0    Misc    ===========  Logging initialized (build: 7.4.7600.226, tz: -0000)  ===========


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.