none
SCCM 1702 Client can not install updates

    Question

  • SCCM Client can not install updates.

    Configuration console--Monitoring--Deployments

    Updates Group show unkonwn

    UpdatesStore.log

    Initialization of UpdatesStore completed, 0 update status(es) were loaded. UpdatesStore 2017/12/29 9:49:42 5580 (0x15CC)
    Message received to refresh all update status, processing... UpdatesStore 2017/12/29 9:49:42 5580 (0x15CC)
    Failed to refresh Resync state message. Error = 0x87d00310. UpdatesStore 2017/12/29 9:49:57 5580 (0x15CC)
    Failed to refresh sync message. Error = 0x87d00310. UpdatesStore 2017/12/29 9:49:57 5580 (0x15CC)

    windowsupdates.log

    2018-01-02 15:42:50:505 620 a64 Agent ***********  Agent: Refreshing global settings cache  ***********
    2018-01-02 15:42:50:505 620 a64 Agent  * WSUS server: <NULL> (Changed)
    2018-01-02 15:42:50:505 620 a64 Agent  * WSUS status server: <NULL> (Changed)
    2018-01-02 15:42:50:505 620 a64 Agent  * Target group: (Unassigned Computers) (Unchanged)
    2018-01-02 15:42:50:505 620 a64 Agent  * Windows Update access disabled: No (Unchanged)
    2018-01-02 15:42:50:505 620 a64 AU AU received policy change subscription event
    2018-01-02 15:42:50:506 620 a64 AU Sus server changed through policy.
    2018-01-02 15:42:50:530 620 a64 AU AU Refresh required....
    2018-01-02 15:42:50:531 620 a64 AU AU setting next featured software notification timeout to 2018-01-02 07:42:50
    2018-01-02 15:42:50:532 620 a64 AU Successfully wrote event for AU health state:0
    2018-01-02 15:42:50:532 620 a64 AU Can not perform non-interactive scan if AU is interactive-only

    WUAHandler.log

    CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles WUAHandler 2017/12/14 18:22:29 12792 (0x31F8)
    CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles WUAHandler 2017/12/14 18:24:20 15952 (0x3E50)
    CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles WUAHandler 2017/12/16 8:45:15 7420 (0x1CFC)
    CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles WUAHandler 2017/12/28 16:03:02 8328 (0x2088)
    CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles WUAHandler 2018/1/2 9:42:17 6248 (0x1868)
    CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles WUAHandler 2018/1/2 11:17:29 3240 (0x0CA8)

    Thanks!

    Thursday, January 04, 2018 2:58 AM

All replies

  • SCCM Client can not install updates.

    Configuration console--Monitoring--Deployments

    Updates Group show unkonwn

    UpdatesStore.log

    Initialization of UpdatesStore completed, 0 update status(es) were loaded. UpdatesStore 2017/12/29 9:49:42 5580 (0x15CC)
    Message received to refresh all update status, processing... UpdatesStore 2017/12/29 9:49:42 5580 (0x15CC)
    Failed to refresh Resync state message. Error = 0x87d00310. UpdatesStore 2017/12/29 9:49:57 5580 (0x15CC)
    Failed to refresh sync message. Error = 0x87d00310. UpdatesStore 2017/12/29 9:49:57 5580 (0x15CC)

    windowsupdates.log

    2018-01-02 15:42:50:505 620 a64 Agent ***********  Agent: Refreshing global settings cache  ***********
    2018-01-02 15:42:50:505 620 a64 Agent  * WSUS server: <NULL> (Changed)
    2018-01-02 15:42:50:505 620 a64 Agent  * WSUS status server: <NULL> (Changed)
    2018-01-02 15:42:50:505 620 a64 Agent  * Target group: (Unassigned Computers) (Unchanged)
    2018-01-02 15:42:50:505 620 a64 Agent  * Windows Update access disabled: No (Unchanged)
    2018-01-02 15:42:50:505 620 a64 AU AU received policy change subscription event
    2018-01-02 15:42:50:506 620 a64 AU Sus server changed through policy.
    2018-01-02 15:42:50:530 620 a64 AU AU Refresh required....
    2018-01-02 15:42:50:531 620 a64 AU AU setting next featured software notification timeout to 2018-01-02 07:42:50
    2018-01-02 15:42:50:532 620 a64 AU Successfully wrote event for AU health state:0
    2018-01-02 15:42:50:532 620 a64 AU Can not perform non-interactive scan if AU is interactive-only

    Wednesday, January 03, 2018 6:20 AM
  • There's no WSUS server defined.

    What does WUAHandler.log on the client(s) say?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, January 03, 2018 2:20 PM
  • Thursday, January 04, 2018 12:15 AM
  • Based on that, you haven't associated any site systems hosting the SUP role with the proper boundary groups which is required since CB 1702 (also note this is a 2012 forum and not a CB forum).

    Also, copying and pasting from a text log file is almost always better than posting a screenshot of CMTrace in a forum thread.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, January 04, 2018 1:42 AM
  • OK.I have changed to CB froum.

    Thursday, January 04, 2018 3:04 AM
  • Hi,

    Were this working before? Have you verified that your clients are reporting to the correct WSUS server? You can verify this by checking client local registry to be sure that it's pointing to the SUP.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, January 04, 2018 7:06 AM
    Moderator
  • I will merge this into the new thread.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, January 04, 2018 8:58 AM
    Moderator