{"id":3950,"date":"2019-02-15T06:08:12","date_gmt":"2019-02-15T06:08:12","guid":{"rendered":"https:\/\/pariswells.com\/blog\/?p=3950"},"modified":"2019-02-15T06:08:12","modified_gmt":"2019-02-15T06:08:12","slug":"wsus-clients-contacting-but-not-reporting","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/research\/wsus-clients-contacting-but-not-reporting","title":{"rendered":"WSUS Clients contacting but not reporting"},"content":{"rendered":"

\"\"<\/p>

These are the steps that definitely fixed the issue for me:<\/p>

Delete the computer from the WSUS console
On the affected client, stop the Windows Update service
On the affected client, rename the folder C:\\Windows\\SoftwareDistribution
Start the Windows Update service
Run the following command in and administrative prompt:<\/p>

wuauclt \/detectnow \/reportnow \/scannow \/resetauthorization<\/p>

After 15 minutes or so the client will reappear in the WSUS console and report correctly<\/p>

 <\/p>

I had a related issue with MDT deployed machines not detecting any updates.<\/p>

I ran this script on the PC.<\/p>

https:\/\/www.tenforums.com\/tutorials\/24742-reset-windows-update-windows-10-a.html<\/a><\/p>","protected":false},"excerpt":{"rendered":"

These are the steps that definitely fixed the issue for me:Delete the computer from the WSUS consoleOn the affected client, stop the Windows Update serviceOn the affected […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[2848,2847,2191,923],"class_list":["post-3950","post","type-post","status-publish","format-standard","hentry","category-research","tag-contacting","tag-not-reporting","tag-windows-update","tag-wsus"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t