WSUS Server Showing Error Event 13031 and 13032

[Victor Asuquo]

I have my AD domain organised as a single domain win2k3 sp2 forest in two
sites. My WSUS is organized as a Upstream server in the main site and a
downstream server in the branch site. A few users move from the main office
to the branch. No folder redirection or roaming profile is currently
configured. Both sites are linked to a 10Mbps WAN link.

Recently the WSUS server with Sp2 has started showing event id 130031 and
13032 stating that for example 45 clients can not contact the server in the
past thirty days on both of the WSUS servers. I have researched the topic
and inplemented everything here
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=.NET+Framework&ProdVer=2.0.50727&EvtID=13031&EvtSrc=Windows+Server+Update+Services&LCID=1033

but so far have been unsuccessful. Please any help will be appreciated

Thanks

[Lawrence Garvin [MVP]]

"Victor Asuquo" <abasi...@yahoo.com> wrote in message
news:23C6945B-5144-4420...@microsoft.com...

> Recently the WSUS server with Sp2 has started showing event id 130031 and
> 13032 stating that for example 45 clients can not contact the server in
> the past thirty days on both of the WSUS servers.

This is a natural occurrence if your clients are registered with both
servers as a result of their roaming activities. This will automatically
happen if you've linked your GPOs to the =SITE=. As a mobile computer
connects to one site or the other it gets the URL of the local WSUS server
and registers with that server. If it doesn't come back to the site for 30
days, it gets reported as "not contacting" by that server.

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.

You can also manually delete computers from the "other" WSUS server once
you've determined that the computer is communicating correctly with it's
home server.

The typical configuration involving roaming systems and site policies (with
or without the use of DNS Round-Robin) involves clients registering with
*replica* servers, and then those replica servers uploading information to
an upstream (reporting) server using Reporting Rollup. In this way only the
latest information is retained at the upstream server (which then means "not
contacting" really does mean Not Contacting), and weekly runs of the SCW on
the replica servers keeps the old records cleaned out of those servers.

However, sometimes these messages may also indicate a real communication
issue -- though I suspect that is not the case here. 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
a Last Contacted Date older than 24 hours at its home site. If you're doing
this, then the "not contacted in 30 days" messages become benign, and you
can simply ignore them. 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, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

[Victor Asuquo]

Thanks for your prompt reply; I have ranm SCW as advised and will keep an
eye on things

Thanks again
"Lawrence Garvin [MVP]" <lawr...@news.postalias> wrote in message
news:F00E68F2-D4D3-473A...@microsoft.com...