• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5181
  • Last Modified:

Event ID: 13032 WSUS Weird error!

Hello all,
I have a Windows 2K3 SBS that function as AD, DHCP, DNS with no WSUS. I added another server few weeks back (Windows 2K3 Std R2). I have install WSUS 3 on it, which works fine ( I think!).

I noticed that the SBS server keep giving me Event ID 13032 even though there is no WSUS on it. Any idea why?

Also, how can I make sure the WSUS 3.0 on the Windows 2K3 Std R2 really works? I looked at reports, but they are too unclear as too if updates are really sent and installed on the XP workstations. I have choose to have the XP get the updates straight from MS. I dont want to store all these updates on the server.

Event Type:      Error
Event Source:      Windows Server Update Services
Event Category:      Clients
Event ID:      13032
Date:            2/14/2009
Time:            7:06:31 AM
User:            N/A
Computer:      XXXXXXXXX
Many client computers have not reported back to the server in the last 30 days. 30 have been detected so far.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any help would be greatly appreicated.

  • 4
  • 2
1 Solution
The best way is to go in and determine if WSUS shows all clients.

WSUS has a snapin that can be put on the MMC console to evaluate what clients are being seen by your WSUS server. The default settings will show yellow under the computers section of WSUS snapin if the computer hasn't checked in for a while.

Most likely this error is caused by not setting up group policy objects the point your clients to the WSUS server. Were these policies set when you brought the new server on line?
SpiderPigAuthor Commented:
I think so, I remember going into the GPO and setting it up. Where and what do I need to change in the GPO again? I will go and check. Also, do I need to enter the name of the group inside WSUS where all the workstations are located? you see I have created two groups. one for servers (shouldnt be updated by WSUS), and one for workstations (should be updated by WSUS).

Thanks for your help.

If you go to this thread, you will see a number of GPOs that you might have to configure for WSUS:

1) pointing clients and servers to the WSUS web site.

2) detection frequency

Let me know if you have questions on the GPOs.

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

SpiderPigAuthor Commented:
In the GPO should I use the WSUS address with the admin port or just the URL (for ex: http://wsus or http://wsus:8530) ?
by default, the port is port 80. If you have any web pages or other items that use port 80 WSUS will default to port 8530.

I see it a lot that wsus reports to 8530. Try port 80 and if clients don't report in, then try port 8530.


http:\\server.domain.name     (this is the port 80 setting)
http:\\server.domain.name:8530  (this setting is for port 8530)

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now