Client showing "Windows is up to date"
- I had a WSUS 3.0 sp1 setup, and all was working perfectly for my little network. Then I approved the update for WSUS 3.0 SP2. It appeared to install fine, but following the install, I could not complete the config, as the synch would not complete. After researching and trying to figure it out. I finally got synchronization to complete. But then I found that all of my clients were reporting that they were up to date, but none of them had installed any updates, since I upgraded. So I decided to try again, I uninstalled letting it remove everything (database, etc.). I then reinstalled. (it is on a SQL 2005 server and the database is on this server). The install appeared flawless and synch went without issue, restocked my update folder, etc. So I brought a new computer online (no updates) Windows 7, added it to my network, applied my GPO to give it my intranet location and times to update and install. Then from my client, I ran windows update. It immedately responded that I needed to update my windows update on the client and it performed this update, then reopened the windows update window. But it then states that the computer is up to date. It is far from up to date. What am I missing, it worked perfectly in sp1, what changed?
I have been researching and tweaking for 2 days, now I am worried about my forefront definitions on my network computers - they are not being updated.
I look forward to your assistance. The WSUS server is Windows 2003 sp2 running Sql 2005 sp2, my clients are windows xp, vista, and win 7.
Fred Zilz
Answers
- > (the synchronization I was referring to not completed was a manually started synch - attempted
> serveral times - and it is not that it completed with 0 results but rather it would hang at 0% complete
> - eventually timing out and my synch history showed no completed synchs after the SP2 update
Then I submit that if you were able to initiate a manual sychronization in the WSUS3SP2 environment, that your upgrade was 100% successful and you have a *different* issue to evaluate, not a failed upgrade.
> But from the client it states windows is up to date last checked - an hour ago, updates installed - never.
So, there are a number of scenarios that could cause this and I could continue to speculate, but let's look at some real data and just cut to the chase.
Perform the following diagnostic procedure, please:
1. Record the system time on that Windows 7 computer.
2. Restart the Automatic Updates service.
3. From a command line, run the command: wuauclt /resetauthorization /detectnow.
4. Wait 30 minutes.
5. Post all of the entries from the WindowsUpdate.log starting at the time recorded in Step #1.
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 byFredZilz Monday, November 02, 2009 5:16 PM
All Replies
- Windows =7= is probably the wrong client to be using to test functionality of update currency in your environment. I think I can count on one hand the number of updates in the WSUS catalog that are applicable to a Windows 7 client. (I actually checked -- it'll take two hands -- there are nine updates released since 10/13/09, and one from 9/22/09. Four security updates, one critical update, four standard updates, and an update rollup.) What build of Windows 7 did you install? (There are =zero= updates that will detect as needed on the Win7RC.)
So, the first question I have about your "upgrade" is this statement:
> It appeared to install fine, but following the install, I could not complete the config, as the synch would not complete.
Because an =upgrade= from WSUS3SP1 to WSUS3SP2 does not require any configuration tasks nor would it initiate a synchronization beyond what was regularly scheduled on the original WSUS3SP1 environment.
Second, blindly approving WSUS3SP2 (KB972455), as was blindly approving WSUS3SP1 in early 2008, as was blindly upgrading WSUS2 to WSUS3 in early 2007 -- a sure-fire invitation for something to go wrong. Review the WSUS3SP1 Release Notes and the WSUS3SP2 Release Notes and verify that there is nothing in those documents that was applicable to your WSUS3SP1 environment. It's all pretty much water under the bridge though, since you subsequently installed WSUS3SP2 as a fresh system.
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 - Yes, thank you for your response - in hindsite allowing the sp2 update to occur without extended research was a mistake, and as you stated is now water under the bridge. (the synchronization I was referring to not completed was a manually started synch - attempted serveral times - and it is not that it completed with 0 results but rather it would hang at 0% complete - eventually timing out and my synch history showed no completed synchs after the SP2 update - but that is another thing that is water under the bridge since I completely uninstalled and reinstalled).
When I look in WSUS the new Windows 7 client shows as having last status report as of yesterday - so the computer is reporting into the update service, it show 18 updates needed. But from the client it states windows is up to date last checked - an hour ago, updates installed - never.
I have now checked several other clients and they do appear to be updating, so I will have to look into this installation and see why this one client (new win 7 install) is not updating. I have other win 7 clients to that do appear to be updating.
Fred Zilz - > (the synchronization I was referring to not completed was a manually started synch - attempted
> serveral times - and it is not that it completed with 0 results but rather it would hang at 0% complete
> - eventually timing out and my synch history showed no completed synchs after the SP2 update
Then I submit that if you were able to initiate a manual sychronization in the WSUS3SP2 environment, that your upgrade was 100% successful and you have a *different* issue to evaluate, not a failed upgrade.
> But from the client it states windows is up to date last checked - an hour ago, updates installed - never.
So, there are a number of scenarios that could cause this and I could continue to speculate, but let's look at some real data and just cut to the chase.
Perform the following diagnostic procedure, please:
1. Record the system time on that Windows 7 computer.
2. Restart the Automatic Updates service.
3. From a command line, run the command: wuauclt /resetauthorization /detectnow.
4. Wait 30 minutes.
5. Post all of the entries from the WindowsUpdate.log starting at the time recorded in Step #1.
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 byFredZilz Monday, November 02, 2009 5:16 PM
- Thank very much for your time. It appears that the client is slowly getting its updates. I must be taking the WSUS server a very long time (days) to get all the updates downloaded, but it looks like we are getting there. Your advice to reset the update service and run wuauclt /resetauthorization /detectnow was very helpful as the log showed that the client was in fact connecting to the server, and when an approved update is available it did show in the log as 1 update needed.
I did see a Soap error in the log related to "uploading 2 events", soap fault : 0x00012c, faultstring:Fault occurred, Errorcode: ConfigChanged(2), Message: (null), Method: http://www.microsoft.com/SoftwareDistibution/ReportEventBatch, ID:bd18f231-c6ad-4b2d-9d72-bd6dc2724c29, Reporter failed to upload events with hr=8024400d
If I see this repeated, I will research this one.
Thank you again for your time and assistance.
Fred Zilz I did see a Soap error in the log related to "uploading 2 events", soap fault : 0x00012c, faultstring:Fault occurred, Errorcode: ConfigChanged(2), Message: (null), Method: http://www.microsoft.com/SoftwareDistibution/ReportEventBatch, ID:bd18f231-c6ad-4b2d-9d72-bd6dc2724c29, Reporter failed to upload events with hr=8024400d
This issue has been sometimes associated with duplicate SusClientID values. Check to be sure that all of your client systems are displayed in the All Computers node of your WSUS Admin Console.
This is also a known issue when improperly configured load balancing solutions are deployed.
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
