?
Solved

WSUS not reporting correctly with Windows Server 2012

Posted on 2014-02-14
3
Medium Priority
?
868 Views
Last Modified: 2014-05-07
All windows server 2012 servers and windows 8 clients don't correctly report to WSUS that they are pending a reboot as there status after installing an update that needs one.  If you log into them they will show they are pending a reboot.  They will report there status of installed and updates needed correctly just not if they are pending a reboot.  Server 2008 R2, Server 2012 R2, windows 7, and windows 8.1 will report they are pending a reboot in the status.  


Looking in the registry of those servers they do have the Reboot Required registry key under HKLM\software\microsft\windows\currentversion\windowsupdate\auto update.
0
Comment
Question by:bnussbaum
  • 2
3 Comments
 
LVL 48

Expert Comment

by:Don
ID: 39860480
The correct location to determine whether there is a pending reboot is found here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations
0
 

Accepted Solution

by:
bnussbaum earned 0 total points
ID: 39861486
That registry key does not exist on either the Server 2012 or Server 2012 R2 servers.  When you log in they show they have a pending reboot but still don't have that key.
0
 

Author Closing Comment

by:bnussbaum
ID: 40046613
The other solutions weren't the solution.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

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

What to do when Windows Update is not working correctly? What tools can I use to detect the cause of the malfunction problem? What does this numeric error code mean? These and other questions that you have been asking in the past are answered here (…
Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

585 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question