Quantcast
Channel: WSUS Forum
Viewing all 12331 articles
Browse latest View live

WSUS Synchronization Failed with the error "The upstream server experienced an unexpected error. Please try again at a later time."

$
0
0

We have one WSUS Upstream Server (Central) configured to stream with Microsoft Updates Server and 2 Downstream Servers (Primary Servers) connected to the Upstream Server.

The Upstream Server Synchronization succeeded with Microsoft Updates Server, but both the downstream Servers getting synchronization failed with the below error message.

WSUS Synchronization Failed with the error "The upstream server experienced an unexpected error. Please try again at a later time."

Details:

InvalidOperationException:    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

   at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()

   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)

   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)

   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()

   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

We tried the below but no luck,

1) Restarted WSUS, IIS services in Upstream Server.

2) Verified the credentials and WSUS folders access settings and found fine.

Can someone support on this to fix this WSUS downstream server sync failed issue ?

Thanks,

Sridhar L



Is Windows 2019 WSUS viable?

$
0
0

I'm still in the process to replace my well working (more or less) Windows 2008 R2 WSUS with new installation of Windows 2019 WSUS and still not able to get a viable system. I'm running from error to error and sometimes the mmc suddenly stops working. It takes hours to get a new client noticed by WSUS. And even after some days none of the client have reported yet.

Does anybody have a satisfying WSUS running?

 

WsusContent

$
0
0
Hi experts

I am running out of Disk Space on C drive, Wsus Content folder(C:\Program Files (x86)\WSUS\WsusContent) is occupying space,
How do i clear some of the space

AGENT_DOWNLOAD_FAILED - _AutomaticUpdates_Failure_Content Download_Error: Download failed.

$
0
0

2 Windows 2012R2 server in a test group within WSUS.  Client side targeting is working via GPO. 

I selected 10 updates and approved it and targeted this test group.  I can see on the server side in the Report Approval shows to Install  but they never install.

I go to the servers and I can see the updates are there but the server is not installing them been two days now.

 On both servers > C:\Windows\WindowsUpdate.log file shows these errors:

WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
AGENT_DOWNLOAD_FAILED]101 {5297C254-5D17-4844-AEA7-4BC07FE8D155}20080244017AutomaticUpdatesFailureContent DownloadError: Download failed.



Thoughts - Thank you

EventID: 12072 - 401 Unauthorized - Agent Download Failed 200 80244017

$
0
0

WSUS and SCCM is on the same server

2 Windows 2012R2 server in a test group within WSUS.  Client side targeting is working via GPO. 

I selected 10 updates and approved it and targeted this test group.  I can see on the server side in the Report Approval shows to Install  but they never install.

I go to the servers and I can see the updates are there but the server is not installing them been two days now.

 On both servers > C:\Windows\WindowsUpdate.log file shows these errors:

WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
AGENT_DOWNLOAD_FAILED]101 {5297C254-5D17-4844-AEA7-4BC07FE8D155}20080244017AutomaticUpdatesFailureContent DownloadError: Download failed.



Thoughts - Thank you



Best Practice to clean up WSUS content no longer needed

$
0
0

I have been researching this for days and probably have about 10 hours invested in trying to come to a conclusion and now want some feedback from this group. Below you will find everything I think you might need about my current configuration. I originally installed my first WSUS server in 2006.Over the years I added new products as needed, changed to express files (seems to have been a bad decision), unselected products no longer needed, and when version 3 came out began running the cleanup wizard monthly. I have never declined any updates myself and only approved those showing as needed. I watched my content grow to about 65 GB then decided to migrate to a new server. I followed this procedure which worked very well:

http://exchangeserverpro.com/how-to-move-wsus-30-to-a-new-server

After the migration I tested a round of updates and everything was working fine. Then I added Windows Server 2008 (only have one server with this OS) and SQL Server 2008 R2 (only have one server with this OS) products and was amazed when my content went up to over 100 GB. I decided to remove those two products since only one server needs them and I could update it direct from MS instead thinking it would be easy to recover the space. Was I in for a surprise. No real easy way to do that. From my research these seem to be the options to do a good clean up on all unneeded content. What do you suggest as the best way for me to proceed?

Option 1: uninstall and re-install fresh

Option 2: reset the content following this procedure:

http://blogs.technet.com/b/gborger/archive/2009/02/27/what-to-do-when-your-wsuscontent-folder-grows-too-large.aspx

Option 3: reset the content following this procedure: (I tested this on my old server and steps 1-4 took about 90 minutes)

1. Decline all previously approved updates. (Yes, all of them. Even the ones you want.)
2. Run the cleanup wizard -- this will remove files in the WsusContent folder.
3. Change the approval of all DECLINED updates from declined to "Not Approved" (and apply inheritance).
4. Run the cleanup wizard again -- this will decline all expired updates.
5. Re-approve needed updates. Content will be re-downloaded.

I do plan to remove the express files option first to reduce the amount of space needed for storage. If you see anything else in my config that should be tweaked please let me know. Thanks for any and all feedback. I appreciate you taking the time to read this and respond.

My configuration follows:

1 Gbps switched network infrastructure with 10/10 fiber internet access

WSUS – current environment – 1 physical server also used as a file share server for user files

Windows Server 2008 Enterprise (x86)

Dual Intel Xeon 2.8 Ghz

2 GB Ram

1 Gbps Nic

136 GB hard drive for DB and WSUS Content files (currently DB=1.5 GB, Content = 108 GB)

WSUS Server version: 3.2.7600.226

Using the Windows Internal Database (I do have a SQL Server 2008 R2 server available now)

128 Computers in 13 groups manually assigned but computers are directed to this server via GP

(all Servers and 90% of workstations are current on updates through last month)

3189 Updates installed/NA

139 Updates needed

919 Updates with no status

Configuration options:

Update source – Microsoft

Products – Office 2003, Office 2010, Windows 7, Windows Defender, Windows Server 2003, Windows Server 2008 R2, Windows XP (previously selected but no longer needed: Office 2002/XP, SQL Server 2008 R2, Windows 2000, Windows Server 2008)

Classifications – critical, definition, security, service packs, update rollups, updates

Update files and languages – store locally, download only when approved, download express installation files, English

Automatic approvals – above classifications for test group which includes one computer with each of the following OS’s: Windows 7, Windows Server 2003, Windows Server 2008 R2, Windows XP

After those machines are tested then I approve and install needed updates for the server group (8 machines total) which include Windows Server 2003, Windows Server 2003 R2, Windows Server 2008 R2, Windows XP

After those machines are tested then I approve needed updates for all computers and let the users install them


WSUS and Driver updated - Windows DCH

$
0
0

I am noticing that Intel and other manufacturer's are now recommending you get all of your driver updates via Windows updates.

I am reading that this can cause some issues on WSUS and client machines.

Most of the articles I am reading are a year old or older.

Does anyone have any experience with approving driver updates on WSUS and setting them to automatic approval.

I currently have over 30 different model machines and all different manufacturer's.

Thanks

Server 2019, WSUS MMC Snap-in: Increase timeout?

$
0
0

I have a brand new Windows 2019 running a basic WSUS install in a virtual machine with two Xeon 3.5 ghz vCPUs, 8 gig of memory.

It is a fully default WSUS install using the Windows Internal Database SQL server, and the default language and product options. I ran the synchronization. Nothing has been approved, no computers are joined. Everything is working normally.

I am unable to view the synchronization status because the Windows Internal Database SQL engine is taking too long to respond to the MMC snap-in.

How can the snap-in timeout be increased? I have thoroughly searched C:\Program Files\Update Services and I can not find any MMC configuration files where there is a timeout option that can be adjusted.

WSUS for Windows Server 2019 appears to be broken as designed.

,

Steps to reproduce:

1. Open WSUS MMC management snap-in. Open Task Manager, says 0-5% CPU load.

2. Click on Synchronizations in WSUS MMC.

3. It says at bottom "Loading synchronization history, 0% complete"

4. Windows task manager suddenly shows 50% CPU usage across the two vCPU's (really, just 100% load for 1 CPU).

5. After about 5 minutes pass, the MMC snap-in is unhappy and claims it can't reach WSUS. Task manager continues to show 50% CPU usage across the two vCPU's for several more minutes by SQLServr.exe.

6. WID-SQL server eventually finishes whatever it was doing, and Task Manager drops to about 0-5% system load.

7. Can't do anything with the MMC after the internal database has stopped chugging along for 7-10 minutes now. The only option available is to "Reset Server Node," which discards anything that has been retrieved so far. 

8. Go back to Step 2 and do this all over again several more times. No change.

9. Stop VM, increase memory from 8 gb to 16 gb, start VM. This memory increase has no effect. The WSUS MMC still times out trying to load the synchronization history.

,

Is there any way to increase the Server 2019 WSUS MMC snap-in timeout, or am I being indirectly forced by Microsoft to buy a full license for Microsoft SQL Server, because the Windows internal database is too slow and low performance, to respond to the MMC snap-in within 5 minutes?



Windows 10 Business edition update now in WSUS!!!!

$
0
0

Today I noticed that I have a new update "Feature update to Windows 10 (business editions), version 1809 x64 2019-03B, en-us 

trying to be installed on my machines.

Previously, I had approved the "Feature update to Windows 10 (consumer edition), verson 1809, en-us x64.

Can anyone tell me what is going on here? and why MS sneaks these updates in.

My machines are windows 10 pro.

Please advise asap.

Get-WsusUpdate fails with 'There is an error in the XML document (1,3988350)'

$
0
0

Has anyone else seen this error. I am hoping to automate declining updates I don't care about, but I keep getting errors like the below one.  This is running on Windows Server 2012 R2, and it is the WSUS instance used as my SUP for SCCM CB 1710.

PS C:\> Get-WsusUpdate -UpdateId '4c2de636-0bc7-4dfe-9d4e-299ea50e3ffc'
Get-WsusUpdate : There is an error in XML document (1, 3988361).
At line:1 char:1
+ Get-WsusUpdate -UpdateId '4c2de636-0bc7-4dfe-9d4e-299ea50e3ffc'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Updat...usUpdateCommand:GetWsusUpdateCommand) [Get-WsusUpdate],
   InvalidOperationException
    + FullyQualifiedErrorId : UnexpectedError,Microsoft.UpdateServices.Commands.GetWsusUpdateCommand



Levi Stevens

EventID: 12072 - 401 Unauthorized - Agent Download Failed 80244017

$
0
0

WSUS and SCCM is on the same server

2 Windows 2012R2 server in a test group within WSUS.  Client side targeting is working via GPO. 

I selected 10 updates and approved it and targeted this test group.  I can see on the server side in the Report Approval shows to Install  but they never install.

I go to the servers and I can see the updates are there but the server is not installing them been two days now.

 On both servers > C:\Windows\WindowsUpdate.log file shows these errors:

WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
AGENT_DOWNLOAD_FAILED]101 {5297C254-5D17-4844-AEA7-4BC07FE8D155}20080244017AutomaticUpdatesFailureContent DownloadError: Download failed.



Thoughts - Thank you




Freshly installed WSUS 10.0 in windows server 2016 shows updates downloading with 0 download

$
0
0

Hi 

Freshly installed WSUS 10.0 in windows server 2016 shows updates downloading with 0 download. i did decline the updates and approve one update to check as well. But still the same. BITS shows the attached error

where is this "Monthly Roll Up Updates"?

$
0
0

in this Windows Update History Survey

number 6, monthly rollup updates is mentioned separately from security updates.

but if you look at WSUS' classification tab, there is no way to select monthly rollup updates.

looks like the survey itself needs a survey on correctness.

The WSUS Content Directory is not accessible

$
0
0

Single Primary Site running SCCM 2012 R2 on Windows Server 2012 R2.

WSUS on same server using Ports Http: 8530 and HTTPS: 8531 and is using SUSDB as database.

No Proxy in place.

Everything was working and issue started last week. No changes were made.

We get following WSUS errors 

System.net.webException: The request failed with HTTP status 503: Sevice Unavailable~~~ Failures reported during periodic health check by the WSUS server. will retry check in 1 mins

I then ran the WSUSutil.exe checkhealth command and in event viewer, get a few different errors:

Event ID 13042: Self-update is not working.

Event ID 10021: The catalog was last synchronized successfully 1 or more days ago.

Event ID 12002: The Reporting Web Service is not working.

Event ID 12012: The API Remoting Web Service is not working.

Event ID 12032: The Server Synchronization Web Service is not working.

Event ID 12022: The Client Web Service is not working.

Event ID 12042: The SimpleAuth Web Service is not working.

Event ID 12052: The DSS Authentication Web Service is not working.

Event ID 12072: The WSUS content directory is not accessible.

System.Net.WebException: The remote server returned an error: (503) Server Unavailable.

   at System.Net.HttpWebRequest.GetResponse()

   at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)

Please suggest.

WSUS - 2019 All Computers Server Node Crash

$
0
0

I wanted to try out a test 2019 WSUS server. Everything seemed to go smoothly, however when I go look at All Computers, I get a system node crash.

I looked at the possibility of it being the same as the bad BIOS name, but I do not seem to see any errors.

The error is as follows:

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists, 

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.


System.InvalidCastException -- Unable to cast object of type 'System.Guid' to type 'System.String'.

Source
Microsoft.UpdateServices.BaseApi

Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchComputers(String computerTargetScopeXml)
   at Microsoft.UpdateServices.Internal.BaseApi.ComputerTarget.SearchComputerTargets(ComputerTargetScope searchScope, UpdateServer updateServer)
   at Microsoft.UpdateServices.UI.AdminApiAccess.ComputerTargetManager.GetComputerTargets(ComputerTargetScope searchScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.BulkComputerPropertiesCache.GetAndCacheComputers(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.ComputersListPage.GetListRows()

Has anyone come across this error before?

Thanks.


hotfix download

$
0
0

We use DUNDAS BI program and when we do a health check it says for us to install the hotfix for Microsoft KB 2683913. When I google that hotfix, I cannot find it. This server is running windows server 2016 and by default it doesn't seem this is currently installed.

Below is the application that explains this. Can you advise where I can download this hotfix for the OS needed as I cannot find it when doing a google search.

https://www.dundas.com/support/learning/documentation/administration/health-check

conflicting approvals

$
0
0

computer A is in WSUS group B and WSUS Group C.

update D is approved for install on WSUS Group B, and Not Approved for Group C.

is computer A going to detect/install update D?

Server won't reboot Automatically

$
0
0

I noticed that my servers are not automatically rebooting after installing the approved updates as per this GPO in place.....

GPO is working I checked as the clients are moved into the correct Group in WSUS.


Thanks in Advance.

Is the March 2019 KB4490128 part of the Security Monthly Quality Rollup

$
0
0
KB4490128 is Classified as an Update Rollup in WSUS (this is a DST update). WSUS says all of my machines need it. If I go straight to Microsoft Update it says I don't need it. My machines have the March Security Monthly Quality Rollup installed, I assume an Update Rollup is included in Security Monthly quality rollup and therefore I can just decline?

March .NET updates KB4489488 and KB4489486

$
0
0

WSUS says my clients and servers need either KB4489488 and KB4489486 (.NET), depending on the OS. WSUS lists these as "Updates". However, if I go straight to Microsoft Update it says I don't need it, it isn't listed as an option update either. I am struggling to figure Microsoft out. I can't tell if this is a WSUS issue (don't think so).

Jason

Viewing all 12331 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>