Unfortunately, you can only configure the download location for an ADR is during the initial creation.
The resolution is to configure the ADR to download the content from the WSUSContent UNC share rather than using the WSUS content URL. If the improvements in Configuration Manager 2002 don’t resolve your issue due to WSUS using the FQDN, you have another workaround to allow the content to be automatically downloaded. Workaround for Proxy Issue when Using HTTPS WSUS Note: The actual error code can vary depending on the proxy configuration. When the proxy can’t resolve the internal WSUS server, you will often receive an HTTP response error such as:ĮRROR: DownloadUpdateContent() failed with hr=0x800701f6ĮRROR: DownloadUpdateContent() failed with hr=0x800701f7ĮRROR: DownloadUpdateContent() failed with hr=0x80070193 This is common for proxies that are internet-based or even internal proxies that don’t allow access or route to internal servers. This will cause an issue when the proxy doesn’t have access to the internal WSUS server. In the PatchDownloader.log you can see the proxy details as well, You can see download information in the following logs for ADRs ( RuleEngline.log and PatchDownload.log). The third-party software updates are downloaded from the internal WSUS server. The proxy server being used doesn’t have access to download content from the internal WSUS server. The software update point site system is set to use the proxy for automatic deployment rules content downloads:ģ. A proxy is configured on the software update point site system:Ģ. Here are the conditions that may cause this issue to occur:ġ. What Causes Error HttpSendRequest failed 502 / 0x800701f6 or 503 / 0x800701f7 or 403 / 0x80070193?įirst, we will dig into the conditions where this issue is most likely to occur.
0 kommentar(er)
