I see it a lot that wsus reports to 8530. At last, the better place to diagnose a "not reporting" issue is the WindowsUpdate.log.Check whether there are some tips for the cause. If the above is not the cause, Run the Client Diagnostic Tool ,inspect the results andverify WUStatusServer registry values are correct. http://technet.microsoft.com/en-us/library/dd939818(v=ws.10).aspx share|improve this answer answered Dec 10 '12 at 19:05 NeerPatel 2291517 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google have a peek at this web-site
For example: Vista Application Error 1001. TechNet Products IT Resources Downloads Training Support Products Windows Windows Server System Center Browser Office Office 365 Exchange Server SQL Server If you have any web pages or other items that use port 80 WSUS will default to port 8530. About Us Windows Vista advice forums, providing free technical support for the operating system to all. This will automatically happen if you've linked your GPOs to the =SITE=.
To protect against > real communication issues, you should monitor the "Last Contacted Date" in > your console at least once a week and investigate immediately any system > that has Fino a ora ne sono stati rilevati 6 con tale comportamento.Oct 29, 2012 Many client computers have not reported back to the server in the last 30 days. 23 have Marked as answer by Clarence ZhangModerator Wednesday, February 29, 2012 1:25 AM Thursday, February 23, 2012 6:47 AM Reply | Quote Moderator All replies 0 Sign in to vote Hi, Please
Was the London Blitz accidentally started by lost pilots? However, sometimes these messages may also indicate a real communication issue -- though I suspect that is not the case here. have been detected so far. Any known fix?
I was unable to reinstall or uninstall WSUS 3.0 SP1 (both actions failed). Try port 80 and if clients don't Go to Solution 4 2 2 Participants ChiefIT(4 comments) LVL 38 Windows Server 200333 SBS9 SpiderPig(2 comments) 6 Comments LVL 38 Overall: Level What would be your next deduction in this game of Minesweeper? Many client computers have not reported back to the server in the last 30 days.
In fact, in this scenario, you can use Options | Personalization To-Do List to completely Turn Off those notifications. -- Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA Principal/CTO, Onsite Technology Solutions, Houston, SP. 0 LVL 38 Overall: Level 38 Windows Server 2003 33 SBS 9 Message Expert Comment by:ChiefIT ID: 236657712009-02-17 If you go to this thread, you will see a number Log Name: Application Source: Windows Server Update Services Date: 10/3/2013 4:53:26 AM Event ID: 12042 Task Category: 9 Level: Error Description: The SimpleAuth Web Service is not working. Log Name: Application Source: Windows Server Update Services Date: 10/3/2013 4:53:26 AM Event ID: 12002 Task Category: 9 Level: Error Description: The Reporting Web Service is not working.
asked 4 years ago viewed 1810 times active 4 years ago Related 0WSUS not working on clients - deployed via GPO1WSUS : Client use old server for downloading instead of server Join the IT Network or Login. one for servers (shouldnt be updated by WSUS), and one for workstations (should be updated by WSUS). Thanks for your help.
It's just going to think that nothing is checking in. Check This Out Another symptom is the computer will receive updates, but not report into the server properly. It takes just 2 minutes to sign up (and it's free!). Join the community Back I agree Powerful tools you need, all for free.
I tried reinstalling again and indicated that WSUS should create a new database. Any help would be greatly appreicated. Comments: Mark S.
If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? Do they "alive" ? No, create an account now. Log Name: Application Source: Windows Server Update Services Date: 10/3/2013 4:53:26 AM Event ID: 13042 Task Category: 6 Level: Error Description: Self-update is not working.
thanks for posting it Reply ↓ Jimmy Wang January 12, 2016 at 10:54 pm Thanks, it has been fixed. Please try the remediation described in KB903262 for duplicate SusClientIDs. To protect against these false positives, you should run the Server Cleanup Wizard on a weekly basis and delete any computers that have not reported in over 30 days. How to make use of Devel debugging functions on large or complex objects Interview for postdoc position via Skype What's the male version of "hottie"?
Reply ↓ Horstworst January 26, 2016 at 7:17 am Thanks, this fixed the errors for me! These articles are provided as-is and should be used at your own discretion. Event ID: 13032 Source: Windows Server Update Services Source: Windows Server Update Services Type: Error Description:Many client computers have not reported back to the server in the last 30 days.
If the event originated on another computer, the display information had to be saved with the event. Please try the remediation described in KB903262 for duplicate SusClientIDs.