locked
WIndows 10 clients reporting to WSUS RRS feed

  • Question

  • Hello,

    We recently upgraded clients to Windows 10 from 7. Window 7 clients were working fine with WSUS, but now the Windows 10 clients are showing up in WSUS, but not reporting back to WSUS.

    I rebuilt the WSUS to the 4.0 platform and still no luck.

    Any advice for Win10 clients to report/pull updates from WSUS?

    Thanks

    Wednesday, June 29, 2016 9:07 PM

Answers

All replies

  • Hi MTKadmin,

    On WSUS server, please install KB3095113 and KB3159706:

    KB3095113:

    https://support.microsoft.com/en-us/kb/3095113

    KB3159706: (NOTE: after installing KB3159706, we need to do manual steps lists in the KB to finish the installation)

    https://support.microsoft.com/en-us/kb/3159706

    On Win10 clients, also check windows update log, check if there are errors for clients:

    https://support.microsoft.com/en-sg/kb/3036646

    Best Regards,

    Anne


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

    Thursday, June 30, 2016 2:42 AM
  • Hello Anne,

    I completed the steps of the 2 installs. WSUS still showing that the PCs still have yet to report. I did look into the C:\Windows\SoftwareDistribution\Download folder and noticed they started to pull.

    Is it a matter of time?

    I tried to review the logs, but am somewhat confused with them. I will continue to work and learn them.

    Wednesday, July 6, 2016 2:23 PM
  • Hi MTKadmin,

    >Is it a matter of time?

    We can monitor a period of time, if it still doesn't report to WSUS server tomorrow, you may feed back with the recent windows update log on win10.

    Best Regards,

    Anne


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

    Thursday, July 7, 2016 9:40 AM
  • Here is a partial log from a Windows 10 client.

    They look like they are now communicating and downloading updates from WSUS.

    -------------------------------------------------

    {987FCB1D-6FC5-4F38-9EE3-D2B018FB8D22} 2016-07-11 12:28:34:981-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {DD44EBE0-DEEF-4843-B3D7-5E6FF251C720} 2016-07-11 13:09:22:795-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {5B681E4B-C9E1-4F4E-AF61-877E873BFC2E} 2016-07-11 13:14:51:245-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {BB473781-1B18-4F57-9B57-096E54C2A0A7} 2016-07-11 13:18:05:696-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {4A245346-E6A1-4E02-9264-A5100C3989E7} 2016-07-11 14:01:03:964-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {570DB4CF-093C-4D11-9693-AFBE018FD469} 2016-07-11 14:35:08:938-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {6945B61E-2C1F-418E-A053-BAE2E933DCD3} 2016-07-11 14:38:35:045-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {B36228D4-7404-42E3-A364-A2A8BBE187CF} 2016-07-11 14:48:54:288-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {41F4B90B-7803-4ECC-80B2-CD2BBFA7152F} 2016-07-12 09:07:38:611-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 WSAutoUpdate Success Software Synchronization Windows Update Client successfully detected 3 updates.
    {893F51FF-ECD6-43C3-A464-1F27EC69F053} 2016-07-12 09:07:40:595-0500 1 167 [AGENT_DOWNLOAD_STARTED] 101 {99DCADA4-4EE9-4FDD-8D6F-235ADC70A99C} 1 0 WSAutoUpdate Success Content Download Download started.
    {9ADB96B0-402E-4636-8152-2277DB0DF029} 2016-07-12 09:07:42:283-0500 1 167 [AGENT_DOWNLOAD_STARTED] 101 {6C09E3AF-F360-4FC2-9ED7-C7064A7BEB61} 1 0 WSAutoUpdate Success Content Download Download started.
    {1F7A35BC-44DF-450E-9DF8-B8EB3FFB013C} 2016-07-12 09:08:17:157-0500 1 167 [AGENT_DOWNLOAD_STARTED] 101 {CE6D74D7-4B53-4BD5-92C6-DE4A9959CBE1} 1 0 WSAutoUpdate Success Content Download Download started.
    {0205061E-6BA4-4DBF-8DB7-3B04B159EA3B} 2016-07-12 09:08:18:204-0500 1 162 [AGENT_DOWNLOAD_SUCCEEDED] 101 {99DCADA4-4EE9-4FDD-8D6F-235ADC70A99C} 1 0 WSAutoUpdate Success Content Download Download succeeded.
    {6F49A83B-05FB-4189-99A6-695AC0DCBC78} 2016-07-12 09:08:18:235-0500 1 162 [AGENT_DOWNLOAD_SUCCEEDED] 101 {6C09E3AF-F360-4FC2-9ED7-C7064A7BEB61} 1 0 WSAutoUpdate Success Content Download Download succeeded.
    {DF302145-143B-411F-B6D5-1B0099D9FD34} 2016-07-12 09:08:18:563-0500 1 181 [AGENT_INSTALLING_STARTED] 101 {99DCADA4-4EE9-4FDD-8D6F-235ADC70A99C} 1 0 WSAutoUpdate Success Content Install Installation Started: Windows has started installing the following update: Sway
    {F0750866-7ABA-457F-B508-CE4AAEF09AC4} 2016-07-12 09:08:22:610-0500 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 {99DCADA4-4EE9-4FDD-8D6F-235ADC70A99C} 1 0 WSAutoUpdate Success Content Install Installation Successful: Windows successfully installed the following update: Sway
    {6020D993-DD01-40BE-89DB-2F8C1BB4771A} 2016-07-12 09:08:53:922-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {E7B9C5D2-4E9A-4675-84E5-DD372D40CAFC} 2016-07-12 09:08:56:266-0500 1 162 [AGENT_DOWNLOAD_SUCCEEDED] 101 {CE6D74D7-4B53-4BD5-92C6-DE4A9959CBE1} 1 0 WSAutoUpdate Success Content Download Download succeeded.
    {DC1F9E47-19DA-430E-9FEB-AFEEFC34708F} 2016-07-12 09:08:57:704-0500 1 181 [AGENT_INSTALLING_STARTED] 101 {6C09E3AF-F360-4FC2-9ED7-C7064A7BEB61} 1 0 WSAutoUpdate Success Content Install Installation Started: Windows has started installing the following update: Microsoft Advertising SDK for XAML
    {16B517C6-FEC1-42CC-A4A3-47E271D76299} 2016-07-12 09:09:01:750-0500 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 {6C09E3AF-F360-4FC2-9ED7-C7064A7BEB61} 1 0 WSAutoUpdate Success Content Install Installation Successful: Windows successfully installed the following update: Microsoft Advertising SDK for XAML
    {A558696E-0295-46ED-A593-776F922D45CA} 2016-07-12 09:09:01:766-0500 1 181 [AGENT_INSTALLING_STARTED] 101 {CE6D74D7-4B53-4BD5-92C6-DE4A9959CBE1} 1 0 WSAutoUpdate Success Content Install Installation Started: Windows has started installing the following update: Microsoft Solitaire Collection
    {016D4952-BDE9-454F-99ED-77FFBC80DDA5} 2016-07-12 09:09:12:375-0500 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 {CE6D74D7-4B53-4BD5-92C6-DE4A9959CBE1} 1 0 WSAutoUpdate Success Content Install Installation Successful: Windows successfully installed the following update: Microsoft Solitaire Collection
    {EDFCE907-6D19-4113-8FDA-9581F345B5EF} 2016-07-12 09:13:42:013-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {B0425C84-0BEC-434D-B766-2EBAAD781CF1} 2016-07-12 09:25:29:030-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {49D30311-DCF4-44DB-A29C-3D0E1D8B8C70} 2016-07-12 09:33:06:639-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {B813137E-C744-4A10-918D-847CDE72E697} 2016-07-12 09:36:09:309-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.
    {52C25926-6DAF-4D75-A45F-B63634AE2F36} 2016-07-12 09:43:10:179-0500 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 1 updates.

    ----------------------------------------------------------------

    BUT the WSUS server is still reporting that the clients "Not yet reported" ..

    I do have a 2008R2 server reporting and updating correctly. It is looking like an issue with the console on the WSUS.

    How can I get the clients to show correctly on the WSUS Update Services Agent / Console?

    Thanks


    • Edited by MTKadmin Tuesday, July 12, 2016 8:17 PM
    Tuesday, July 12, 2016 3:16 PM
  • I had same problem. Finaly is necessary put Workstation out of domain, restart and put back to domain.

    Now its reporting fine.

    Tuesday, August 9, 2016 3:43 PM