Jul 21 2017 05:04 AM
Jul 21 2017 05:04 AM
Within the last hour or so I have carried up a cleanup of our WSUS and reindexed the database as per this article https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus...
Once complete I re-enable the SUP schedule and WSUS has not been able to Sync since. Our SCCM Version is 1702 with the hotfix, hosted on a Server 2012r2 system. WSUS content is within a SQL database.
WCM.log;
"System.Net.WebException: The request failed with HTTP status 403: Target service not allowed.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)"
WsusCtrl.log does not seem to indicate any proxy related errors;
"No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name ####### and Proxy Port ##"
Jul 21 2017 05:16 AM
Jul 21 2017 05:16 AM
Jul 21 2017 05:24 AM - edited Jul 21 2017 05:25 AM
Jul 21 2017 05:24 AM - edited Jul 21 2017 05:25 AM
Thanks Bhushan. Will take a look into that now
Jul 24 2017 01:25 AM
Jul 24 2017 01:25 AM
Unfortunately that does not appear to have resolved the issue. I have tech support on the case now
Jul 26 2017 03:25 AM
Jul 26 2017 03:25 AM
So it would appear that this issue is only when a proxy is specified within the site system properties of the primary site server
I am just wondering why this would all of a sudden start happening it would appear as a result of carrying out the WSUS cleanup and database reindex as per the link provided? Unless just a mere coincidence
Also On the proxy logs I am not even seeing an attempt from the SCCM server to access the Windows update URL's only https://fef.msub05.manage.microsoft.com which is intune and passes successfully.
When I remove the proxy I can see connection to https://fe2.update.microsoft.com
Continuing to investigate.
Nov 09 2017 10:55 PM
hi,
facing exact the same Problem also right now. also after a wsus Cleanup.
Any solution for this yet?
Nov 20 2017 05:26 AM
Nov 20 2017 05:26 AM
Dec 04 2017 09:01 AM
Well noticed that too and was hoping. Bad news is this didn't fix our Problem, Contacting MS Support now.
Greetings
mike
Feb 23 2018 04:12 AM - edited Feb 23 2018 04:14 AM
Did you manage to fix this?
Having similar issue on of our SCCM 2012 R2 after wsus cleanup and re-index with a different error
On WCM
System.Net.WebException: The request failed with HTTP status 407: authenticationrequired.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)
and on wsyncmgr
DB Server not detected for SUP from SCF File. skipping.