Hello Experts !!!

We have configured WSUS on W2012R2.  Synchronization is showing as successful, however 0 updates are downloaded.

Our Setup: We are connecting the WSUS server to Microsoft updates through Proxy Port#8530.

We found a Hotfix : https://support.microsoft.com/en-us/kb/2838998, but it's applicable to 2012 and not 2012R2, so is this Hotfix applicable for 2012R2 as well?

Please help...

testmonials

Hello,

I can't seem to get SP2 for Office 2010 pushed out to a selection of Win 7 PCs, they get this error code:

WARNING: Install failed, error = 0x80070663

Has anyone seen this before?

Thanks

We have a couple of servers our of 250 which did not receive updates since we approve them

All other servers installed the updates fine.

The logs on both of these server state different things,. It seems that they did not even detect any updates were apoproved for them

Log 1

2014-12-0220:53:11:2038762560Setup***********  Setup: Checking whether self-update is required  ***********
2014-12-0220:53:11:2038762560Setup * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560SetupUpdate NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
2014-12-0220:53:11:2198762560Setup * IsUpdateRequired = No
2014-12-0220:53:14:5008762560PT+++++++++++  PT: Synchronizing server updates  +++++++++++
2014-12-0220:53:15:6418762560AgentWARNING: Failed to evaluate Installed rule, updateId = {07AEE973-703C-4F27-83F1-3E764D9ED2C7}.202, hr = 80041010
2014-12-0220:54:14:9078762560PT+++++++++++  PT: Synchronizing extended update info  +++++++++++
2014-12-0220:54:14:9078762560PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus.domain.com/ClientWebService/client.asmx
2014-12-0222:17:26:767876c04AUAU received policy change subscription event
2014-12-0223:47:30:975876c04AUAU received policy change subscription event
2014-12-0301:37:35:274876c04AUAU received policy change subscription event
2014-12-0303:33:39:241876c04AUAU received policy change subscription event
2014-12-0313:37:20:215876c04AUAU received policy change subscription event
2014-12-0313:53:13:300876c04AUAU received policy change subscription event
2014-12-0314:22:04:014876c04AUAU received policy change subscription event
2014-12-0314:53:07:948876c04AUAU received policy change subscription event
2014-12-0315:06:09:718876c04AUAU received policy change subscription event
2014-12-0315:59:00:942876c04AUAU received policy change subscription event
2014-12-0317:02:49:185876c04AUAU received policy change subscription event
2014-12-0318:26:07:141876c04AUAU received policy change subscription event
2014-12-0319:00:10:014876c04AUForced install timer expired for scheduled install
2014-12-0319:00:10:014876c04AUUpdateDownloadProperties: 0 download(s) are still in progress.
2014-12-0319:00:10:014876c04AUSetting AU scheduled install time to 2014-12-04 16:00:00
2014-12-0319:36:07:168876c04AUAU received policy change subscription event
2014-12-0319:51:06:0338762074AUTriggering AU detection through DetectNow API
2014-12-0319:51:06:0338762074AUPiggybacking on an AU detection already in progress
2014-12-0321:00:56:482876c04AUAU received policy change subscription event

Log 2

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Hi Everyone,

Looked about for this answer but can't find one so hoping someone can help me. I've just configured my first WSUS server and going through the updates. I was curious as to how WSUS picks them up? I currently have over 9000 to go through to approve or deny. 

I've been told you only get updates to Operating Systems that are actually on your network. Is this true? I was under the impression that WSUS picked up every update pushed out by Microsoft and you only approved those that applied to your network. 

Any help on this would be much appreciated!

Liam 

We've been using WSUS on Windows 2008 R2 for a long time.  I setup WSUS on a new Windows 2012 R2 server and I checked the list of products I want it to download patches for.  This is list does not include XP and Windows 2003, etc, that were downloaded onto our older WSUS server and I don't want those things brought down to the new WSUS server.

I know there is a migration method you can follow, but that requires that you copy over all the content and then copy over the database.  I don't want to bring old junk over that isn't necessary and takes up space.  What are the consequences of just pointing clients to the new WSUS server and not migrating everything over?  Or is there a way to migrate settings over, but let the content download fresh from MS and only the newer stuff we need?

Hello,

I was wondering if Windows Server 2012 R2 is backwards compatible with Windows Server 2003. Even though Server 2003 is on its way out it's currently acting as the WSUS. Is it possible to connect Windows Server 2012 R2 to the WSUS (Server 2003) to get it's security updates? 

-Thanks

Hi WSUS experts

we got some clients cannot get windows updates from internal WSUS server, it get the error id 0x8024400d when check updates.

i tried many ways but no luck

1. i tried to delete the distribution folder as below, but no luck. 

Stop the "Windows Updates" service

Rename the \Windows\SoftwareDistribution folder

Restart the "Windows Updates" service

Open a Command Prompt and enter wuauclt /resetauthorization followed by wuauclt /detectnow

2. i used "windows update troubleshooter" on microsoft, it said "Thank you for running an automated troubleshooter from Microsoft, we did not detect any problems and ...."

http://windows.microsoft.com/en-us/windows/troubleshoot-problems-installing-updates#1TC=windows-7

3. Tired to re-create user profile, no luck.

4. some update logs i found, see below

2015-06-18  14:37:54:566      1184  1aec  PT    +++++++++++  PT: Synchronizing server updates  +++++++++++

2015-06-18  14:37:54:566      1184  1aec  PT      + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx

2015-06-18  14:37:54:566      1184  1aec  PT    WARNING: Cached cookie has expired or new PID is available

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING: SOAP Fault: 0x00012c

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING:     faultstring:Fault occurred

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING:     ErrorCode:InvalidParameters(7)

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING:     Message:parameters.OtherCachedUpdateIDs

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING:     ID:6bbf5af7-b7d6-4e92-8824-98fc8d122999

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING: PTError: 0x8024400d

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING: Sync of Updates: 0x8024400d

2015-06-18  14:50:36:574      1184  1aec  PT    WARNING: SyncServerUpdatesInternal failed: 0x8024400d

2015-06-18  14:50:36:574      1184  1aec  Agent   * WARNING: Failed to synchronize, error = 0x8024400D

2015-06-18  14:50:36:605      1184  1aec  Agent   * WARNING: Exit code = 0x8024400D

2015-06-18  14:50:36:605      1184  1aec  Agent *********

2015-06-18  14:50:36:605      1184  1aec  Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]

2015-06-18  14:50:36:605      1184  1aec  Agent *************

2015-06-18  14:50:36:605      1184  1aec  Agent WARNING: WU client failed Searching for update with error 0x8024400d

2015-06-18  14:50:36:824      1184  19e8  AU    >>##  RESUMED  ## AU: Search for updates [CallId = {525A2A26-09CA-44B0-B820-F02EC51D513F}]

2015-06-18  14:50:36:824      1184  19e8  AU      # WARNING: Search callback failed, result = 0x8024400D

2015-06-18  14:50:36:824      1184  19e8  AU      # WARNING: Failed to find updates with error code 8024400D

2015-06-18  14:50:36:824      1184  19e8  AU    #########

2015-06-18  14:50:36:824      1184  19e8  AU    ##  END  ##  AU: Search for updates [CallId = {525A2A26-09CA-44B0-B820-F02EC51D513F}]

2015-06-18  14:50:36:824      1184  19e8  AU    #############

Any ideas?

thanks in advance

Bruce chen

Hi,

I am having a problem since 3 days. we have a WSUS Server 3.0 SP2 on windows server 2008 r2. it was working fine till last week but i was trying to install Windows Server Update Services 3.0 MOM 2005 Management Pack. then running this setup asked me to download dotnet framework 1.1 so I downloaded and installed the both setup. after that I am not able even open the console of wsus. it crashes every time when i tried to open. i suspect that this was happen due to dotnet framework 1.1 because 4.x version was already there. i uninstalled the both .net 1.1 & Windows Server Update Services 3.0 MOM 2005 Management Pack using winodows installer & repaired .Net Framework 4.x version. I also tried to deleting the MMC from users profile which is default path form MMC. but still getting the same error.  also attaching the snapshot of the error.

Any help on this is highly appreciated.

Thanks

Dev

Hi all

I recently noticed that the content store of our primary WSUS server increased from about 20 GB to 90 GB. A colleague of mine set up a secondary WSUS server as a downstream server, at first in autonomous mode, then in replica mode. The upstream server’s content store grew excessively ever since.

I used bitsadmin to look at the queue on the upstream server and to my surprise it was downloading updates for products which are not even selected there (e.g. Exchange 2007). I would like to understand why. Assuming the downstream server is in autonomous mode and requires updates which the upstream server does not have, does the upstream server download these updates on behalf of the downstream server?

I would like to clean up the content store on the upstream server. I deleted the downstream servers, ran the cleanup tool and declined all superseded updates which are no longer needed. Unfortunately this did not make much difference. The upstream content store is still 87 GB. I am aware of the wsusutil /reset command, however, I would like to avoid downloading all updates from scratch. Is there a way to clean up this mess?

I would appreciate if someone could shed some light on this.

Thanks, Stefan

The message "The service master key could not be force regenerated as requested by the -F startup option. The error number is 33094." appears in the Application log on the Windows 2012 R2 server that runs WSUS on our network.

For example:

9:40:59pm The service master key could not be force regenerated as requested by the -F startup option. The error number is 33094.
9:41:00pm The Windows Internal Database service entered the running state.

Nothing bad seems to happen as a result of this message popping up in the event logs, but I'd like to get to the bottom of it anyway.

I've Googled for a solution, but so far I haven't found one.

Matty Brown<br/> Computer Programmer (VBA 7.0/MS Access 2010, VB.Net 2005, ColdFusion 8)

Hi,

I have a WSUS server (the only one in the network) ver.3.2.7600.226 running on Server 2008 Standard.

I have set up a group policy which has been pushed out to all client machines and they are all reporting back. Some are with updates to install, a few updates failed (which we trouble shoot at source) and some lovely green ticks meaning everything is up to date. IIS is set up and the relevant ports are open and communicating.

However, I have a list of old machine in an OU in active directory where the new group policy is not linked to. There machinesdon't exist anymore (most are just hard drives in a draw!). There is no way they can be contacting WSUS so I delete them from WSUS server (not from Active directory). I carry on happily for about 30 minutes then they pop back. What do you think is happening?

I have admin rights on the server, I've emptied/deleted the WSUS cache files, restarted the WSUS server services and reset IIS. My last thought is that there is some sort of MOF file that is bringing the machines back. They only ones I can find are IIS related. This system was set up before my time here as I'm trying to be a mind reader at well!

Any help gratefully recieved.

All the best,

Simon

MMC cannot initialize the snap-in.

Name: Update Services

CLSID: FX:{8b6499ed-0241-e032-6508-da4b1c879d7e}

WinSvr 2008 R2 Std x64 SP1

any ideas??

I've got a main WSUS server and two downstream replicas, and the replicas are no longer syncing - they'll reach 99%, then sit for a while and timeout with some database timeout error:

SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
   at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteReader()
   at Microsoft.UpdateServices.Internal.DataAccess.HideUpdatesForReplicaSync(String xmlUpdateIds)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ProcessHiddenUpdates(Guid[] hiddenUpdates)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ReplicaSync()
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

This started happening a while back after what I can only assume was running the Server Cleanup Wizard on the main/ upstream server, since the timing of the sync failures coincidedes.  Upstream WSUS was out of disk space so I ran the cleanup wizard with every available option selected, one at a time (because cleanup would fail if I tried them all at once, but I eventually got them all run). 

I've tried a wsusutil /reset on one of the replicas, and when that didn't fix it (reset completed per the logs but still sync fails), I uninstalled/reinstalled the WSUS role.  Now the sync history says it completed sucessfully the first time when it was manually run with the install of the role (35k updates pulled down), but now it won't sync again.

What would happen it I replaced the upstream server?  There is another WSUS server provisioned that was never put into production (someone left us and never completed what they were working on) - would I have to go through and re-approve every update going back to the beginning of time (or rather, Windows 7 and Office 2010 for us)?

I inherited this setup from someone who quit and I really don't know much about WSUS so I apologize if these are dumb questions. 

 I have windows 2012 r2. We are using WSUS to push out updates (non domain).

I have several computers that I have removed from WSUS, that re-appear on the WSUS server a few hrs later.. but have no status.

I have tried stopping the wuauserv and running

wuauclt.exe /resetauthorization

wuauclt.exe /detectnow 
wuauclt.exe /reportnow    

This does not make the PC report a status.

I have also tried resetting the SUSClientID. This also does not make the PC's report a correct status.

The computers are getting updates through the WSUS server - which is good!

Any help would be great. Thanks

Hello Team,

Windows 2012 with WSUS.

I have created two GPO policies with client-side targeting and applied to different computer groups (Group1 and Group2).

But i have very specific patch requirements and would like to apply:

patch1 to Group1

patch2 to Group2

Is it possible on WSUS ?

Could you provide any documentation/example ?

Thanks,

Michal