This is the Windows Server Update Services support team blog. We cover all things relating to WSUS and Windows Update.
As we mentioned yesterday, the Windows Server Update Services (WSUS) team has released Knowledge Base article 2734608. This update lets servers running Windows Server Update Services (WSUS) 3.0 SP2 provide updates to computers that are running Windows 8 or Windows Server 2012.
If you have previously applied this update then there are no additional steps to take. Since this KB was taken offline due to backend issues, there are no changes to the download packages themselves. All customers though should be aware of the following steps described in the “Known Issues” section of this KB:
If you have Windows 8 or Windows Server 2012 clients that synchronized with WSUS 3SP2 before you applied this update, wait for the update to be applied to the WSUS servers, and then follow these steps:
Net stop wuauserv rd /s %windir%\softwaredistribution\ Net start wuauserv
For more details on what is included in this KB, please go to: http://support.microsoft.com/kb/2734608
J.C. Hornbeck | Knowledge Engineer | Management and Security Division
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Here is some PowerShell code, which achieves similar results:
Stop-Service -Name wuauserv;
Remove-Item -Path $env:windir\softwaredistribution -Recurse;
Start-Service -Name wuauserv;
Is it possible to update the WSUS-Console with this update? I always get error 1603. Without it i see all my Windows 8 Clients as Windows XP. On the Console on the WSUS-Server itself they show up correctly as Windows 8
Picked up a virus, Trojan WIN32/sirefef.AB. It has disabled firewall. Although microsoft security essentials identifies it, attempts to remove it is futile. Please look into this problem ASAP.
Two quick things:
1. Jurgen: Yes, you can apply this to console-only workstations (or servers) and it does indeed fix up the XP display issue you've mentioned.
2. J.C.: What do you do when removing the softwaredistribution folder has no effect? Server Core 2012 is still throwing 0x80246003 errors, along with detecting a Silverlight hotfix that doesn't even apply to Server Core 2012.
Is there a file and database version reference anywhere that one can use to determine if KB2734608 was even successfully applied?
Figured I'd answer my own question.
The three commands listed above weren't enough. After the second command (the "rd /q /s"), use regedit to remove HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate, then follow that with the "net start wuauserv". That resolved the 0x80246003 error on multiple Server Core 2012 hosts for us.
Thus, the steps (in our case) were:
1. net stop wuauserv
2. rd /q /s %windir%\softwaredistribution
3. Use regedit to delete HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
4. net start wuauserv
This only applies to Server 2012 (or Windows 8, most likely) hosts that had registered with the WSUS host prior to the KB2734608 patch having been applied.
When will KB2734608 provided in WSUS itself?
I'm having an issue with WSUS 4.0 and Hyper-V Server 2012. Maybe I'm way off base, but it seems like it could be related to this blog post.
I've migrated my clients to WSUS 4.0 and all but two Hyper-V 2012 Servers are working great. These two server core based servers show up in WSUS, but then fail to report or obtain further updates. I've tried all the advice in this blog post and comments regarding stopping the service on the affected server, removing the directory and registry entries. When I start the service back up, it shows up in my WSUS server list, but never reports its list of updates.
I see the following in the log files on the two affected servers:
Windows Update Client failed to detect with error 0x8007000e
I never had this issue running Hyper-V Server 2008 R2. It always obtained updates fine. I also have other full installations of Server 2012 with the GUI that are obtaining updates from the WSUS 4.0 server fine. Why doesn't the windows update function want to work properlly in server core?