We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now


Event ID:      13032 WSUS Weird error!

SpiderPig asked
Medium Priority
Last Modified: 2012-05-06
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.

Watch Question

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?


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.


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)

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.