I'm relatively new to WSUS 3.0, so bear with me as I try to describe my problem.
I have a single upstream server, with 30 replica downstream servers. If I log into any of the downstream servers and view the synchronizations, they are running successfully every morning. However, If I view the 'Downstream Servers' container in my Upstream Server, I'm seeing servers that 'have not synchronized in x days where x is between 10 and 15.
As such, when I view the top level 'Computers' container under the Upstream server, the rollup statistics do not match the 'Computers' container on each of the downstream servers.
In fact, one of my Downstream servers has never reported in to the Upstream server, according to the Upstream server, yet looking at the downstream server, it indicates that it's synchronizing daily.
I've attached 3 BMP files that show one such example. Diagram 1 shows the upstream server with downstream8 highlighted. hasn't synched in 12 days.
Diagram 2 shows the computers bucket from downstream8. a completely different set of numbers with regard to the computers reported in.
Diagram 3 shows the computers bucket from the upstream server, with downstream 8 visible.
One final note... if i log into the actual wsus server and look at the console, it is identical to Diagram 2, from my local pc console.
Apologies for the ramblings, and thank you in advance for any assistance you can provide. I will do my best to provide answers to questions you may have for me.
> I have a single upstream server, with 30 replica downstream servers. > If I log into any of the downstream servers and view the > synchronizations, they are running successfully every morning. However, > If I view the 'Downstream Servers' container in my Upstream Server, I'm > seeing servers that 'have not synchronized in x days where x is between > 10 and 15. > In fact, one of my Downstream servers has never reported in to the > Upstream server, according to the Upstream server, yet looking at the > downstream server, it indicates that it's synchronizing daily.
The key here is to understand the difference between what happens between synchronization and reporting. The reason your upstream server shows that replicas have not synchronized is because the *reporting* is failing. The replica server cannot report a successful synchronization until *after* that synchronization has actually completed successfully. This is a function of reporting.
> As such, when I view the top level 'Computers' container under the > Upstream server, the rollup statistics do not match the 'Computers' > container on each of the downstream servers.
This is generally a normal condition, and is a function of the time delay between when the client computer reports to the replica computer, and when the replica computer reports to the upstream server, and when the upstream server actually processed that queued reporting data into the database.
Of course, if the replica server is not reporting correctly, then this information will also be compromised, but in an of itself, it's not indicative or conclusive of anything specific.
The thing to do is review the %ProgramFiles%\Update Services\Logfiles\SoftwareDistribution.log for issues encountered by the replica servers during the reporting events.
Also review the IIS logs on the upstream server for the same time block to determine how IIS is handling the reporting connection requests coming from the replica servers.
Finally, also review the Application Event Log on the replica servers.
-- Lawrence Garvin, M.S., MCITP:EA, MCDBA Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2009)
Thank you for all your help. I sifted through the logs and located the problem.
Due to last month's Patch Cycle from Microsoft, we had to re-install WSUS on half our servers. Apparently, I did not repermission the folders correctly, as such, the Rollup couldn't report correctly.
> I have a single upstream server, with 30 replica downstream servers. > If I log into any of the downstream servers and view the > synchronizations, they are running successfully every morning. However, > If I view the 'Downstream Servers' container in my Upstream Server, I'm > seeing servers that 'have not synchronized in x days where x is between > 10 and 15. > In fact, one of my Downstream servers has never reported in to the > Upstream server, according to the Upstream server, yet looking at the > downstream server, it indicates that it's synchronizing daily.
The key here is to understand the difference between what happens between synchronization and reporting. The reason your upstream server shows that replicas have not synchronized is because the *reporting* is failing. The replica server cannot report a successful synchronization until *after* that synchronization has actually completed successfully. This is a function of reporting.
> As such, when I view the top level 'Computers' container under the > Upstream server, the rollup statistics do not match the 'Computers' > container on each of the downstream servers.
This is generally a normal condition, and is a function of the time delay between when the client computer reports to the replica computer, and when the replica computer reports to the upstream server, and when the upstream server actually processed that queued reporting data into the database.
Of course, if the replica server is not reporting correctly, then this information will also be compromised, but in an of itself, it's not indicative or conclusive of anything specific.
The thing to do is review the %ProgramFiles%\Update Services\Logfiles\SoftwareDistribution.log for issues encountered by the replica servers during the reporting events.
Also review the IIS logs on the upstream server for the same time block to determine how IIS is handling the reporting connection requests coming from the replica servers.
Finally, also review the Application Event Log on the replica servers.
-- Lawrence Garvin, M.S., MCITP:EA, MCDBA Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2009)
|
