Updates Installed Not Applicable Wsus Updates

I'm seeing an issue on two of the servers in my WSUS environment. I have one parent server with two 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 one of the replicas. Huawei E1550 Firmware Update 11.608 Download. 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. My other replica server properly displays the number for installed/not applicable.

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 three servers have them.

Viewing and Managing Updates.. Installed/not applicable percentage. Select Updates are WSUS updates to filter on WSUS updates. I have one parent server with two replicas which are all running WSUS 3.0 SP2. When I click on Updates. Installed/not applicable. Updates installed/not.

Any ideas on how I can get these two other servers which appear to work perfectly fine otherwise, to report the proper count for installed/not applicable? Thanks in advance! After taking another quick look, it appears that the two affected servers are indicating higher 'updates with no status' probably due to the fact that they are not identifying the 'updates installed/not applicable' status. Nitro Pdf Color To Black And White more.

For instance, my parent server is currently showing updates with no status: 2298 and 0 installed/not applicable while the normally functioning replica is showing updates with no status: 937 and 1577 installed/not applicable. I failed to mention that all three servers were upgraded from WSUS 2.0 a long while back and they all use the Windows Internal Database.

After taking another quick look, it appears that the two affected servers are indicating higher 'updates with no status' probably due to the fact that they are not identifying the 'updates installed/not applicable' status. For instance, my parent server is currently showing updates with no status: 2298 and 0 installed/not applicable while the normally functioning replica is showing updates with no status: 937 and 1577 installed/not applicable. To be honest, the high number of updates with 'No Status' is symptomatic that your *CLIENTS* are not detecting/reporting to these servers. I would suggest starting by confrming that the clients are able to connect/detect/report to their assigned WSUS Servers.

Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2010) My MVP Profile: My Blog: http://onsitechsolutions.spaces.live.com. After taking another quick look, it appears that the two affected servers are indicating higher 'updates with no status' probably due to the fact that they are not identifying the 'updates installed/not applicable' status. For instance, my parent server is currently showing updates with no status: 2298 and 0 installed/not applicable while the normally functioning replica is showing updates with no status: 937 and 1577 installed/not applicable. To be honest, the high number of updates with 'No Status' is symptomatic that your *CLIENTS* are not detecting/reporting to these servers.