Wsus Downstream Server Installed Not Applicable Percentage 0

The Installed/Not Applicable% status I am referring to is a column shown when you click on the 'Downstream Servers' node within the WSUS admiistration console on the upstream server (and expand the upstream server node shown at the top of the list).

I'm seeing an issue on two of the servers in my WSUS environment. I have one parent server with 21 replicas which are all running WSUS 3.0 SP2.

When I click on Updates to view the status summary, the Updates installed/not applicable is greyed out and shows 0 on both my parent server and all replicas except 1. What's odd is that the information appears to be there because when I look at the status report of an individual update, I do get that information. All the servers have no issues with synchronization, and clients have been able to update from the parent and replica servers without any problems.

I checked the sofwaredistribution.log file on all the servers. I do see some thrownexception and reporteventbatch errors but I'm not certain that these would be related to my issue because all servers have them.

Any ideas on how I can get these other servers which appear to work perfectly fine otherwise, to report the proper count for installed/not applicable? Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need. What it does: 1. Shrink your WSUSContent folder's size by declining superseded updates.

It will clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs). Remove all Drivers from the WSUS Database. Remove declined updates from the WSUS Database 5.

Run the server cleanup wizard. Lastly, but most important, it will run the recommended maintenance script on the actual SQL database. It will email the report out to you or save it to a file, or both. Follow the instructions at the top of the script, but essentially run. Clean-WSUS.ps1 -FirstRun and then set a scheduled task to run the script with the -ScheduledRun daily at a time you want. You may want to run afterwards:. Clean-WSUS.ps1 -RemoveDeclinedWSUSUpdates -WSUSDBMaintenance -WSUSServerCleanupWizard -SaveReport TXT.

Hi, I am getting the following error on a downstream server. Any suggestion please? PS D: WSUS Tools>. Welcome to the show rainbow rocks.

WSUSClean -WSUSServerCleanupWizard -SaveReport TXT -MailRepo rt HTML Connected to the WSUS server TWEE-DC1.sd36.bc.ca Executing WSUSServerCleanupWizard Exception calling 'PerformCleanup' with '1' argument(s): 'Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.' At D: WSUS Tools WSUSClean.ps1:1440 char:5 + $AdamjCleanupResults = $CleanupManager.PerformCleanup($CleanupScope) + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo: NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId: Exception Remove-Variable: Cannot find a variable with the name 'AdamjCleanupResults'. At D: WSUS Tools WSUSClean.ps1:1524 char:5 + Remove-Variable AdamjCleanupResults + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo: ObjectNotFound: (AdamjCleanupResults:String) [Re move-Variable], ItemNotFoundException + FullyQualifiedErrorId: VariableNotFound,Microsoft.PowerShell.Commands.RemoveVariableCommand. Hi, Thanks for your help and wonderful script. For re-indexing and sync log clearance run fine.