• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 749
  • Last Modified:

Why won't Server 2008 R2 SP1 show as an available update for some of my servers?

Folks -

I've got a few servers that insist they don't need Server 2008 R2 SP1 even though they do.  I've got a WSUS implementation in my environment with the appropriate approvals and most of my servers are picking up the service pack just fine.  However, some of my Server 2008 R2 boxes insist they need no updates regardless of how many times I run the manual check via Control Panel.

If I inspect the WSUS console, it indicates that the machine does in fact need the SP1 update, however, on the client side, it doesn't seem to think so.

Has anyone run into issues with the detection logic of the Automatic Updates service with regards to Server 2008 R2 SP1?

Again, my WSUS implementation is setup properly.  Group memberships, approvals, etc. are all proper, and most of my servers are picking it up fine, but some insist they need no updates.  <sigh>
0
amendala
Asked:
amendala
  • 5
  • 3
  • 2
1 Solution
 
arnoldCommented:
Check the individual servers to make sure that this update was not hidden.
I.e. another admin may have had to apply an update and erroneously marked these updates such that they will not be offered in the future.
0
 
amendalaAuthor Commented:
There are no hidden updates on any of the servers that believe they don't need it.
0
 
DonNetwork AdministratorCommented:
If there is a pending reboot, a client will not query/install further updates until a reboot has taken place.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
arnoldCommented:
Do these server 2008 R2 in the correct client target to get the updates you approved or are they in a client target where you did not approve those updates.

i.e. you have unassigned computers and these 2008 R2 servers in this group.  When looking at the updates a server needs, it says that the updates are not approved.

Check c:\windows\windowsupdate.log to see what is going on on the server that might be preventing it from reporting/downloading the update.

Is your WSUS setup configured to download both types of updates, complete and express? Do not quote me, but It is possible that the update has to be an express package for windows 2008 R2.
0
 
amendalaAuthor Commented:
No.  No pending reboots.  Even after rebooting, same detection behavior: no updates needed.
0
 
DonNetwork AdministratorCommented:
Check the registry for

HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate.
 
Key value name: DoNotAllowSP
 value of 1 is blocked
0
 
amendalaAuthor Commented:
That value does not exist.
0
 
DonNetwork AdministratorCommented:
Please post the windowsupdate.log
0
 
amendalaAuthor Commented:
After discussing with a Premier engineer, he recommended that I disapprove and reapprove the update in an attempt to fix the problem.  When I did that, my servers picked up on the SP1 update being available after forcing another detection cycle.

Why I needed to do this is under investigation but this appears to be a WSUS-related problem.  So my issue is fixed by this.
0
 
amendalaAuthor Commented:
Discovered solution on own.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 5
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now