Windows Server TechCenter >
Windows Server Forums
>
WSUS
>
WSUS 3.0 SP1 - Email Reports only show Upstream server, not downstream server stats
WSUS 3.0 SP1 - Email Reports only show Upstream server, not downstream server stats
- Hi Everyone,
I am sure this has been asked before, but can't seem to find it through the searches.
We have 1 Upstream server, and 2 downstream servers (Regional Sites)
The 2 downstream servers report back into the Upstream server (no issues there)
All workstations are configured in the following way (via group policy)
Corp:
Update Service for Detecting Updates: Upstream Server
Stats Server: Upstream Server
Regional 1:
Update Service for Detecting Updates: Downstream 1
Stats Server: Upsteam Server
Regional 2:
Update Service for Detecting Updates: Downstream 2
Stats Server: Upsteam Server
Now stats work fine in the console, but in the daily status report from the upstream server, only corporate workstation stats show up, the workstations in other computer groups from the downstream servers shows 0.
Is this a bug? Or have we done something wrong? If it's a bug, has SP2 addressed this issue?
Any help would be greatly appreciated.
Regards,
Stefano
Answers
Hi Lawrence,
Hmmm... fire that engineer -- or teach him to read product documentation before messing with product configurations! :-/
Interesting... We had a Engineer change it from the original configuration of:
Regional 1:
Update Service: Downstream 1
Stats Server: Downstream 1
Regional 2:
Update Service: Downstream 2
Stats Server: Downstream 2
... To what is it configured now.
He did this because the email reports were not showing the regionals. So to us, nothing had changed. Looks like our configuration was correct in the first place. Can you shed any light as to why it was not working when the configuration was set correctly in the past?
From the section Set Up E-Mail Notifications in the WSUS v3 SP2 Deployment Guide:
E-mail notifications do not include rolled-up computer status from replica downstream servers.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com- Marked As Answer byStefano Belluomini Sunday, November 15, 2009 10:08 PM
All Replies
Regional 1:
Update Service for Detecting Updates: Downstream 1
Stats Server: Upsteam Server
Regional 2:
Update Service for Detecting Updates: Downstream 2
Stats Server: Upsteam Server
This doesnt't work because this is an incorrect configuration.
1. The WUServer and WUStatusServer values (i.e. the two URLs on the "Specify intranet Microsoft update server location" policy), must be identical. If they're not identical, the WUAgent won't even execute detections against the WSUS server.
2. The replica servers automatically report stats to the upstream server during synchronization based on the upstream server URL configured in Options | Update Source, combined with the enabling of Reporting Rollup on the upstream server in Options | Reporting Rollup.
Most likely your workstations are not appearing on the upstream server, not because reporting rollup is failing, but because those clients aren't even detecting/reporting to the replica WSUS Server.
From Configure Clients Using Group Policy in the WSUS v3 SP2 Deployment Guide:
Specify intranet Microsoft Update service location
The settings for this policy enable you to specify a WSUS server that Automatic Updates will contact for updates. You must enable this policy in order for Automatic Updates to download updates from the WSUS server.
Enter the WSUS server HTTP(S) URL twice, so that the server specified for updates is also used for reporting client events. For example, type http(s)://servername in both boxes, where servername is the name of the server. Both URLs are required.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com- Hi Lawrence,
Interesting... We had a Engineer change it from the original configuration of:
Regional 1:
Update Service: Downstream 1
Stats Server: Downstream 1
Regional 2:
Update Service: Downstream 2
Stats Server: Downstream 2
... To what is it configured now. He did this because the email reports were not showing the regionals. So to us, nothing had changed. Looks like our configuration was correct in the first place. Can you shed any light as to why it was not working when the configuration was set correctly in the past?
Regards,
Stefano Hi Lawrence,
Hmmm... fire that engineer -- or teach him to read product documentation before messing with product configurations! :-/
Interesting... We had a Engineer change it from the original configuration of:
Regional 1:
Update Service: Downstream 1
Stats Server: Downstream 1
Regional 2:
Update Service: Downstream 2
Stats Server: Downstream 2
... To what is it configured now.
He did this because the email reports were not showing the regionals. So to us, nothing had changed. Looks like our configuration was correct in the first place. Can you shed any light as to why it was not working when the configuration was set correctly in the past?
From the section Set Up E-Mail Notifications in the WSUS v3 SP2 Deployment Guide:
E-mail notifications do not include rolled-up computer status from replica downstream servers.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com- Marked As Answer byStefano Belluomini Sunday, November 15, 2009 10:08 PM
- Lawrence,
Hahaha! Thanks for that, we did get rid of him. ;P
Thank you for clearing that up for me regarding reporting. It's a bummer you cannot get rolled up computer stats from the email... Is this added to SP2? Or just by design?
Regards,
Stefano - Stefano, I suspect this is just a manifestation of the history of the functionality.
The "reporting rollup" functionality and the "email notification" functionality were all part of the unsupported API Samples and Tools Kit for WSUS v2.0. Because they were so popular, the Product Team rolled them up into WSUS v3 as part of the feature set. My suspicion, though, is there wasn't a lot of planning effort, if any, in evaluating the "feature set" of the tools.
Because the reporting rollup and email notifications were developed as independent "samples" in the WSUS v2 timeframe, the email notification utility would have been oblivious to the possibilty of replica-based computer status information, thus it probably just doesn't have the architecture to get the information.
The source code for the original tools is available in the WSUS v2 API Samples and Tools Kit (and maybe, still, in the v3 API Samples), and the information is in the upstream server's database, so I imagine it wouldn't take but a bit of 'enhancement' of the code on the part of a good VC# programmer to expand that capability in the form of an add-on tool.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com
