We had WSUS working until we decided to install Trend Micro Control Manager on it. Soon after we realized it broke WSUS. Since then we've uninstalled all traces of both applications as much as possible. Now WSUS won't complete installation. I've searched many different forums topics and couldn't find a solution that matched my particular issue yet. The error log looks fine except for the last portion that looks like this... 

Can anyone help me pinpoint what the problem might be?

Background:

Server 2008 r2 enterprise

WSUS 3.0 Sp2

KB 2734608

sql server 2008 R2 SP3

Problem: when I click on "Synchronizations" or "All updates" it shows loading 99% takes several minutes and the connections displays "connection error". The following error below is in event viewer. How do I fix this?

I have reinstalled wsus + IIS and restarted multiple times.

The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

System.Net.WebException -- The operation has timed out

Source
System.Web.Services

Stack Trace:
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, Int32 publicationState)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
   at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
   at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
   at Microsoft.UpdateServices.UI.AdminApiAccess.WsusSynchronizationInfo.InitializeDerivedProperties()
   at Microsoft.UpdateServices.UI.AdminApiAccess.WsusSynchronizationInfo.get_NewUpdatesCount()
   at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetSyncInfoRow(WsusSynchronizationInfo syncInfo)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetListRows()

Hi ,

      Is it possible we can start the Windows Updates directly with WSUS Export package..? , Because in our Test Environment we don't have bandwidth to distribute the package through network from Import WSUS server.so we can share the package through USB OR DVD to clients. 

if we can able to install the updates to clients through Export package(Using power shell or some other method) it will be very useful. if you have any idea please share it here .. 

Hi,

So I'm implementing WSUS here at work and I'm working on hub and spoke structure with one USS and multiple DSS. I belive the problems is that the servers running Windows 2008R2 haven't been updated in quite a while so the WUA is most likely outdated, while the clients are updated. I'm running WSUS 3.0 SP2 (7.6.7600.226).

Naturally the majority of the clients in are "Not yet reported". Doing the research it sounds like the clients WUA agent is newer than WSUS. I've tried installing KB2720211 and KB2938066. WSUS is still reporting as 7.6.7600.226 and clients are still not reporting in correctly. Am I missing something? I suppose I bite bullet and update all the servers but I would have to schedule downtime for that in the future.

On a side note, is it good practice to use WSUS to update production servers? 

Thanks,

Hello,

Currently we have our update schema set up like this:

1. Once a month I approve the updates in WSUS (Wednesday)
2. Updates are pushed to the machines and are automatically downloaded
3. Install is scheduled by group policy setting of (4 - Automatically download updates and install them on the schedule specified below) on the next Wednesday morning at 1:00 AM
4. I send out an email saying that the updates are downloaded and that if users want to manually install them they can restart/shutdown any time in the next week.
5. Updates are installed on the following Wednesday at 1:00 AM.

I'm getting complaints (from people who refuse to read their email) that they aren't prompted by Windows update to install their updates.  They'd rather install them on their own time so they can work around tests they are performing.  

If I set the GP to (3 - Download the updates automatically and notify when the are ready to be installed), will they every be installed automatically or will it just continue to prompt them forever?

Essentially what I want to do is keep everything the same but have a prompt popup continually from that initial Wednesday that the updates are ready to install until they are actually installed on the scheduled date which is the following Wednesday.  Is this sort of thing possible?

Thanks for the help in advance!

Hello All,

I have 3 WSUS servers A, B, C.

A is my up stream server, B and C are my down stream servers. Now the clients connected to A are not able to pull the updates from the server. Its says found 0 updates. But the clients connected to B and C are working fine.

-- Its not a new setup, working fine from years

-- I dont see any issues related to IIS/SQL in event logs

-- Clients are reporting to server properly and showing in the wsus console

-- Not showing any errors with solar winds client diagnosis tool

I tried below solution

REG Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId  /f
REG Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIdValidation  /f

gpupdate
net stop wuauserv /y
net stop BITS /y
rd C:\WINDOWS\SoftwareDistribution /s /Q
del "c:\windows\windowsupdate.log"
regsvr32 WUAPI.DLL /s
regsvr32 WUAUENG.DLL /s
regsvr32 WUAUENG1.DLL /s
regsvr32 ATL.DLL /s
regsvr32 WUCLTUI.DLL /s
regsvr32 WUPS.DLL /s
regsvr32 WUPS2.DLL /s
regsvr32 WUWEB.DLL /s
regsvr32 msxml3.dll /s
net start wuauserv /y
wuauclt.exe /resetauthorization /detectnow
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f
REG add HKLM\SYSTEM\CurrentControlSet\services\BITS /v Start /t REG_DWORD /d 2 /f
net start BITS /y
wuauclt /reportnow

Below are the client logs

2015-06-04    07:01:12:345     908    f24    AU    Triggering AU detection through DetectNow API
2015-06-04    07:01:12:345     908    f24    AU    Triggering Online detection (interactive)
2015-06-04    07:01:12:345     908    6c4    AU    #############
2015-06-04    07:01:12:345     908    6c4    AU    ## START ##  AU: Search for updates
2015-06-04    07:01:12:345     908    6c4    AU    #########
2015-06-04    07:01:12:345     908    6c4    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {F2C92C34-C053-417C-953C-DB3F35CEEBE6}]
2015-06-04    07:01:12:345     908    448    Agent    *************
2015-06-04    07:01:12:345     908    448    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-06-04    07:01:12:345     908    448    Agent    *********
2015-06-04    07:01:12:345     908    448    Agent      * Online = Yes; Ignore download priority = No
2015-06-04    07:01:12:345     908    448    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2015-06-04    07:01:12:345     908    448    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-06-04    07:01:12:345     908    448    Agent      * Search Scope = {Machine}
2015-06-04    07:01:12:345     908    448    Setup    Checking for agent SelfUpdate
2015-06-04    07:01:12:345     908    448    Setup    Client version: Core: 7.6.7601.18804  Aux: 7.6.7601.18804
2015-06-04    07:01:12:361     908    448    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2015-06-04    07:01:12:361     908    448    Misc     Microsoft signed: NA
2015-06-04    07:01:12:361     908    448    Misc    WARNING: Cab does not contain correct inner CAB file.
2015-06-04    07:01:12:361     908    448    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2015-06-04    07:01:12:361     908    448    Misc     Microsoft signed: NA
2015-06-04    07:01:12:361     908    448    Setup    Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
2015-06-04    07:01:12:361     908    448    Setup    Skipping SelfUpdate check based on the /SKIP directive in wuident
2015-06-04    07:01:12:361     908    448    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
2015-06-04    07:01:13:376     908    448    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
2015-06-04    07:01:13:376     908    448    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://server.domain.com:8530/ClientWebService/client.asmx
2015-06-04    07:01:29:065     908    448    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
2015-06-04    07:01:29:065     908    448    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://server.domain.com:8530/ClientWebService/client.asmx
2015-06-04    07:01:32:955     908    448    Agent      * Found 0 updates and 79 categories in search; evaluated appl. rules of 1188 out of 2050 deployed entities
2015-06-04    07:01:32:955     908    448    Agent    *********
2015-06-04    07:01:32:955     908    448    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-06-04    07:01:32:955     908    448    Agent    *************
2015-06-04    07:01:32:987     908    978    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {F2C92C34-C053-417C-953C-DB3F35CEEBE6}]
2015-06-04    07:01:32:987     908    978    AU      # 0 updates detected
2015-06-04    07:01:32:987     908    978    AU    #########
2015-06-04    07:01:32:987     908    978    AU    ##  END  ##  AU: Search for updates [CallId = {F2C92C34-C053-417C-953C-DB3F35CEEBE6}]
2015-06-04    07:01:32:987     908    978    AU    #############
2015-06-04    07:01:32:987     908    978    AU    Successfully wrote event for AU health state:0
2015-06-04    07:01:32:987     908    978    AU    Featured notifications is disabled.
2015-06-04    07:01:32:987     908    978    AU    AU setting next detection timeout to 2015-06-05 01:54:24
2015-06-04    07:01:32:987     908    978    AU    Setting AU scheduled install time to 2015-06-05 02:00:00
2015-06-04    07:01:32:987     908    978    AU    Successfully wrote event for AU health state:0
2015-06-04    07:01:33:002     908    978    AU    Successfully wrote event for AU health state:0
2015-06-04    07:01:37:956     908    448    Report    REPORT EVENT: {1BD62347-4CA3-4C27-8976-DFA5CE1A7773}    2015-06-04 07:01:32:955+0100    1   147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
2015-06-04    07:01:37:956     908    448    Report    REPORT EVENT: {DBCBA80E-4A7B-42EE-815A-9748F9A73D11}    2015-06-04 07:01:32:955+0100    1   156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.

Please help me.. Thanks

Hi Technet,

I have a Server 08 R2 installation with process svchost.exe gradually increases memory usage over time until the servers performance suffers.

Using process explorer, in the handles pane, errors in path C:\Windows\SoftwareDistribution\DataStore\datastore.edb
The error:(An error occurred while reading or writing to a file).

Stopping the Windows update service clears the errors, restarting and they appear again.

I have run the Microsoft windows update fixit.

I have renamed the C:\Windows\SoftwareDistribution folder and allowed it to rebuild its contents.

I have used esentutl to both repair and defrag the datastore.edb, both performed successfully.
However the errors persist.

Can anyone assist in what my next troubleshooting steps would be please?

Thanks,

Andrew

HI All,

 I have set all my Domain workstation to above. Time set daily 10 PM.   also i have noticed its install some updates  automatically.

But yesterday one of WSUSADMIN approved 20 plus office updates and today i can see waiting to install?

So why its not install automatically?

Is this install tonight at 10 PM?

Windows Components/Windows Updatehide
Policy Setting Comment
Allow Automatic Updates immediate installation Enabled
Allow non-administrators to receive update notifications Disabled
Allow signed updates from an intranet Microsoft update service location  Disabled
Automatic Updates detection frequency Enabled
Check for updates at the following
interval (hours):  20

Policy Setting Comment
Configure Automatic Updates Enabled
Configure automatic updating: 4 - Auto download and schedule the install
The following settings are only required
and applicable if 4 is selected.
Scheduled install day:  0 - Every day
Scheduled install time: 22:00

Policy Setting Comment
Delay Restart for scheduled installations Enabled
Wait the following period before
proceeding with a scheduled
restart (minutes):  10

Policy Setting Comment
Enable client-side targeting Enabled
Target group name for this computer Windows 7

Policy Setting Comment
Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates Enabled
No auto-restart with logged on users for scheduled automatic updates installations Enabled
Re-prompt for restart with scheduled installations Enabled
Wait the following period before
prompting again with a scheduled
restart (minutes):  60

Policy Setting Comment
Specify intranet Microsoft update service location Enabled
Set the intranet update service for detecting updates: http://enwsus01/
Set the intranet statistics server: http://enwsus01/
(example: http://IntranetUpd01)

Policy Setting Comment
Turn on recommended updates via Automatic Updates Disabled 

Hello All,

All of a sudden i am getting this error on all the clients. I have a internal wsus server, which my clients will connect and get the updates. Its working till Dec 3rd, i didnt made any changes.. but it stopped working.

Please help me

2015-01-05    18:54:13:281    1064    ae8    AU    Triggering AU detection through DetectNow API
2015-01-05    18:54:13:281    1064    ae8    AU    Triggering Online detection (interactive)
2015-01-05    18:54:13:281    1064    15f4    AU    #############
2015-01-05    18:54:13:281    1064    15f4    AU    ## START ##  AU: Search for updates
2015-01-05    18:54:13:281    1064    15f4    AU    #########
2015-01-05    18:54:13:283    1064    15f4    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {8995B9F5-4001-4F07-97E6-3CEFBDC15D6A}]
2015-01-05    18:54:13:283    1064    1430    Agent    *************
2015-01-05    18:54:13:283    1064    1430    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-01-05    18:54:13:283    1064    1430    Agent    *********
2015-01-05    18:54:13:283    1064    1430    Agent      * Online = Yes; Ignore download priority = No
2015-01-05    18:54:13:283    1064    1430    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2015-01-05    18:54:13:283    1064    1430    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-01-05    18:54:13:283    1064    1430    Agent      * Search Scope = {Machine}
2015-01-05    18:54:13:283    1064    1430    Setup    Checking for agent SelfUpdate
2015-01-05    18:54:13:284    1064    1430    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
2015-01-05    18:55:24:178    1064    1430    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2015-01-05    18:55:24:186    1064    1430    Misc     Microsoft signed: Yes
2015-01-05    18:55:24:257    1064    1430    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2015-01-05    18:55:24:261    1064    1430    Misc     Microsoft signed: Yes
2015-01-05    18:55:24:297    1064    1430    Setup    Determining whether a new setup handler needs to be downloaded
2015-01-05    18:55:24:297    1064    1430    Setup    SelfUpdate handler is not found.  It will be downloaded
2015-01-05    18:55:24:297    1064    1430    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2015-01-05    18:55:24:299    1064    1430    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2015-01-05    18:55:24:300    1064    1430    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2015-01-05    18:55:24:314    1064    1430    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2015-01-05    18:55:24:314    1064    1430    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2015-01-05    18:55:24:336    1064    1430    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2015-01-05    18:55:24:336    1064    1430    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
2015-01-05    18:55:25:375    1064    1430    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
2015-01-05    18:55:25:375    1064    1430    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://abcd.mydomain.com:8530/ClientWebService/client.asmx
2015-01-05    18:55:25:417    1064    1430    PT    WARNING: Cached cookie has expired or new PID is available
2015-01-05    18:55:25:417    1064    1430    PT    Initializing simple targeting cookie, clientId = a788c530-2b29-4113-81e6-381a1751ada9, target group = , DNS name = a12300.mydomain.com
2015-01-05    18:55:25:417    1064    1430    PT      Server URL = http://abcd.mydomain.com:8530/SimpleAuthWebService/SimpleAuth.asmx
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SOAP Fault: 0x00012c
2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     faultstring:Fault occurred
2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     ErrorCode:InvalidParameters(7)
2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     Message:parameters.OtherCachedUpdateIDs
2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     ID:fd13335d-34d0-49b6-b065-aefab8b836f8
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: PTError: 0x8024400d
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: Sync of Updates: 0x8024400d
2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncServerUpdatesInternal failed: 0x8024400d
2015-01-05    18:55:28:432    1064    1430    Agent      * WARNING: Failed to synchronize, error = 0x8024400D
2015-01-05    18:55:28:433    1064    1430    Agent      * WARNING: Exit code = 0x8024400D
2015-01-05    18:55:28:433    1064    1430    Agent    *********
2015-01-05    18:55:28:433    1064    1430    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-01-05    18:55:28:433    1064    1430    Agent    *************
2015-01-05    18:55:28:433    1064    1430    Agent    WARNING: WU client failed Searching for update with error 0x8024400d
2015-01-05    18:55:28:496    1064    15cc    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {8995B9F5-4001-4F07-97E6-3CEFBDC15D6A}]
2015-01-05    18:55:28:496    1064    15cc    AU      # WARNING: Search callback failed, result = 0x8024400D
2015-01-05    18:55:28:496    1064    15cc    AU      # WARNING: Failed to find updates with error code 8024400D
2015-01-05    18:55:28:496    1064    15cc    AU    #########
2015-01-05    18:55:28:496    1064    15cc    AU    ##  END  ##  AU: Search for updates [CallId = {8995B9F5-4001-4F07-97E6-3CEFBDC15D6A}]
2015-01-05    18:55:28:496    1064    15cc    AU    #############
2015-01-05    18:55:28:498    1064    15cc    AU    Successfully wrote event for AU health state:0
2015-01-05    18:55:28:500    1064    15cc    AU    AU setting next detection timeout to 2015-01-05 18:25:28
2015-01-05    18:55:28:500    1064    15cc    AU    Setting AU scheduled install time to 2015-01-06 05:30:00
2015-01-05    18:55:28:501    1064    15cc    AU    Successfully wrote event for AU health state:0
2015-01-05    18:55:28:502    1064    15cc    AU    Successfully wrote event for AU health state:0
2015-01-05    18:55:33:432    1064    1430    Report    REPORT EVENT: {633AB594-B0B7-426A-A49F-6F508897E1BA}    2015-01-05 18:55:28:433+0530    1   148    101    {00000000-0000-0000-0000-000000000000}    0    8024400d    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x8024400d.

Hi All- Our existing enterprise has about 200 PCs. We have had a SUS server up for a while, but I think the database is fubar. All of the machines show 99% installed however our Updates overview and Computers overview look like this:

After looking through some forums, it was suggested that the database may be bad. I have already stood up a 2012 R2 server w/ the SUS role. I have a separate GPO pointing to the new test server, and this GPO is applied to my work desktop and work laptop. So far they have checked in OK.

My question is (and I am a desktop support person trying to learn)- do I need to decline any of the superseded updates?

On the brand new SUS server w/ only Windows 7 and Office 2010/2013 configured as Products, there are 1300 security updates and 1197 critical updates to be approved. 

As I said I'm new to SUS so I'm just trying to get a handle on it.

Do you all decline superseded updates or do you approve all, let all the machines report in and sort it out one by one?

I have just installed WSUS 3.0 SP 2 on a Windows 2008 R2 Data Center vm. Our old WSUS server was on a Windows 2003 vm platform and is now retired. I have been successful in synchronizing to Windows Update Services website but when it comes to downloading Windows Malicious Software tool (March, April, and May 2015) I have no luck. This is a clean install, meaning I didn't migrate the DB from the 2003 Server.

I have exhausted all the suggestion that have been posted in regard to this issue but none have worked. The error is a http 403 error saying  Client does not have access.

Tried to Import the rollup in WSUS and although it came back as successful the update still shows and not being download.

I should add that PC's have successfully received the latest updates that I approved; which includes the Windows Malicious Software tool. Except for this tool and the PC's are showing they still need this update.

Any suggestions?

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

We are using the latest available version of WSUS that runs on WIN2008 R2.

We changed the IP address of the WSUS server.

Now, our client computers are failing to download updates from the WSUS server successfully. 

In Fiddler, the sequence of http requests looks like this on the client side:

(1) Targets the correct host using the unchanged WSUS "hostname:port"

HEAD /selfupdate/wuident.cab?1506041722 HTTP/1.1

(2) Targets the correct host using the unchanged WSUS "hostname:port"

POST /ClientWebService/client.asmx HTTP/1.1

(3) & (4) as for (2)

(5) Targets the OLD IP address (not the hostname) and thus fails with a 50x error

HEAD /Content/E1/4631DA8D6454B5680C0159B5254C15D54A8184E1.exe HTTP/1.1

What we are expecting to see is the 5th request pointing to either the unchanged hostname or at the very least, to the correct new IP address.

Things we have checked to try to fix this:

1/ DNS. We are absolutely confident that there is no way the client (or server) could be resolving the hostname to the old IP address. We have scavenged ruthlessly in both the forward and reverse lookup zones; scoured WINS for any stale entries; scoured the Windows HOSTS file; scoured DHCP (just in case).... we have dug as deeply as we think it is possible to go to ensure this is not a name-resolution issue

2/ On the WSUS Server where the IP was changed, we have

(a) triple-checked all IIS bindings and reset IIS, making sure there are no references or bindings to the old IP address

(b) triple-checked all basic network settings and checked the hosts file

(c) Dug into the internal SQL Server WSUS database (using SQL Server Management Studio) and looked through all tables and views to try to identify any stale references to the old IP addresses. In this respect I must admit we have cannot have covered every item of data (because there is so much) but we have dug around as much as we can and concluded that its unlikely the host IP address for these requests is stored therein. 

(d) Checked every setting we can find in the WSUS console

(e) Executed the clean-up wizard a number of times

(f) run NSLOOKUP and network connectivity tests

3/ On the affected client where we see the erroneous requests that point to the OLD ip address we have:

(a) run NS LOOKUP and network connectivity tests; cleared the DNS cache; thoroughly reviewed all Group Policy and Local Security Policies to ensure the Window Update policy settings are all correct and use only the hostname

(b) Cleared out the BITS .dat files and restarted both BITS and WU Services with each test 

(c) Attempted to remove all BITS queued jobs using both the BITSAdmin tool and the Powershell cmdlets (this is on Windows 7 x64) -- however, there is one job owned by SYSTEM that we cannot remove no matter what we do 

4/ We have also tried DECLINING the updates we know trigger the problem; letting the client run; then re-approving the updates on WSUS and then letting the client run again, but the problem persists

5/ We have extensively tested network connectivity between the client and server at various points of the stack (e.g. TCP/IP layer tests, protocol-specific HTTP tests, SOAP tests, etc.) and cannot identify any issues.

At this stage we are considering the possibility of having to either:

1. Entirely trash the Windows Updates folders on the CLIENT side and see what happens

2. Entirely re-install WSUS.

Any suggestions that do not cover the ground we have already covered, would at this time be very gratefully received.

thanks

According to the deployment guide, 30gb is recommended. However, it does not seem to be close to enough. On my WSUS server, I only have 2 products checked: Windows 7 and Office 2013. For classifications, I've checked Security, Critical, Service packs, definitions, and updates. For languages, I've only selected English.

As a result, I have about 2300 updates and I have approved them all. However, the server is downloaded 96gb worth of updates. Does this sound right?

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

Can anyone recommend if its a good idea to set WSUS to auto approve updates? Specifically security and critical updates. 

Thanks

Shane 

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

we have to install Exchange server 2010 on windows 2008 r2 (Enterprise Edition) so Kindly guide me How update my windows 2008 r2 server in offline mode.

Kindly provide me details of windows 2008 r2 (Enterprise Edition) offline update

With warm regards, Kiran Sawant