---------- Forwarded message ---------- From: Michael Leone <[email protected]> Date: Tue, Sep 15, 2015 at 8:54 AM Subject: Re: [wsus] Some Win2012 R2 WSUS clients slow to check in To: WSUS Mailing List <[email protected]>
Another interesting data point ... today I have 4 servers that say last check in was prior to me approving some updates yesterday. So theoretically, none of these 4 should be showing any of those newly approved updates, since they haven't checked in to WSUS and been told about them, right? This turns out not to be the case ... Example: this server (different than the one I manually forced yesterday) shows that it is waiting to install an update I only approved yesterday. Yet the WSUS server shows last check-in was Sunday at midnight - well before me approving the update Monday morning at 9AM. So how can this client know that it needs this update? This now leads me to suspect my WSUS server, or at least the "Last Status Report" entries. Maybe there's something goofy in the reporting on the server. Because all 4 clients who show a last status date of prior to patch approval time, all are showing that they are waiting to install one of the patches approved yesterday morning. And if they haven't checked in, how could they know about these patches? And they are all Win2012 R2 machines .. Not sure where to go, but it looks like I might actually have a direction ...
