Clients are not updating, but are checking in to the wsus 3 server Wes Render 6/20/2007 9:18:39 PM A while back we were using WSUS 2.0, and the updates were all going through smoothly. One day our clients stopped updating, but continued to check into the server. I haven't had a chance to check into the issue for a few months, but I finally got around to upgrading to WSUS 3.0. The clients are still checking in, but are not updating. Would someone be able to point me in the right direction for troubleshooting this? I can't seem to find any documentation on the WSUS site about this. Thank you, Wes

Re: Clients are not updating, but are checking in to the wsus 3 server "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/22/2007 3:12:13 AM "Wes Render" <WesRender[ at ]discussions.microsoft.com> wrote in message news:F09BBB67-8B19-4CC3-9551-F5716C5AD147[ at ]microsoft.com... [Quoted Text] >A while back we were using WSUS 2.0, and the updates were all going through > smoothly. One day our clients stopped updating, but continued to check > into > the server. I haven't had a chance to check into the issue for a few > months, > but I finally got around to upgrading to WSUS 3.0. The clients are still > checking in, but are not updating. > > Would someone be able to point me in the right direction for > troubleshooting > this? I can't seem to find any documentation on the WSUS site about this. Hmmmm..... interesting. First step is to download and run the Client Diagnostic Tool to confirm that the client is properly communicating with the server. Second step is to inspect the WindowsUpdate.log for error entries. However, given the symptom that the client continues to 'contact' the server, but does not detect/download/install/report updates, the list is fairly short: [a] No updates are approved for installation. [b] The client does not have accurate information about its assigned target group, thus is not getting accurate approval information. [c] The client has lost access to a critical component of the WSUS server, thus preventing a successful detection, etc. event, but not preventing a basic selfupdate event, which would cause "Last Contacted" to be refreshed. [d] The server is having issues downloading content, which will prevent a successful detection of an approved update, since the client cannot ack an approval until after the WSUS server has successfully downloaded the needed content files. Any of the above possibilities will be fairly easily determined from either or both the CDT and the WindowsUpdate.log. The fact that *all* of your clients failed on or about the same time strongly suggests an issue with the server and/or network infrastructure affecting all systems. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....