O
olaf_aepfle.de
There is an overwhelming list of results in your favorite search engine for the following entry in the WindowsUpdate.log:
WebServices Auto proxy settings for this web service call.
So far I found no page which explains how to turn exactly this thing OFF in a fresh "Windows Server 2016" deployment.
Does anyone happen to know how to not use a proxy and go directly to the internet?
Long version of the story:
I had to install "Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO" after hardware failure. The physical machine is apparently in a network where Windows finds the local optional (!) proxy server. Without asking for permissions, it uses it to fetch updates, and fails to fetch them as a result. If the very same ISO image is used to install in a VM in a slightly different part of the network, then windows can update itself without an issue right away.
What I did to install is essentially just hitting Next/Next/Next during install. Datacenter Desktop, whole disk, some Admin password. After that, the VM can update itself, and the bare metal system can not. The only relevant entry in the WindowsUpdate.log is really the one shown above. Even forcing (or clearing) the usage of the local proxy in the Internet Explorer settings or 'netsh winhttp' makes zero difference. With Wireshark.exe I see requests initially going directly to some update.microsoft.com hosts, and at some point I see rejected requests to the local proxy server.
Therefore the question: How does one turn that off, what would be the correct search term to find the answer myself?
Meanwhile the physical machine was moved to the network segment that does not expose this issue, and it is currently updating itself just fine.
Continue reading...
WebServices Auto proxy settings for this web service call.
So far I found no page which explains how to turn exactly this thing OFF in a fresh "Windows Server 2016" deployment.
Does anyone happen to know how to not use a proxy and go directly to the internet?
Long version of the story:
I had to install "Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO" after hardware failure. The physical machine is apparently in a network where Windows finds the local optional (!) proxy server. Without asking for permissions, it uses it to fetch updates, and fails to fetch them as a result. If the very same ISO image is used to install in a VM in a slightly different part of the network, then windows can update itself without an issue right away.
What I did to install is essentially just hitting Next/Next/Next during install. Datacenter Desktop, whole disk, some Admin password. After that, the VM can update itself, and the bare metal system can not. The only relevant entry in the WindowsUpdate.log is really the one shown above. Even forcing (or clearing) the usage of the local proxy in the Internet Explorer settings or 'netsh winhttp' makes zero difference. With Wireshark.exe I see requests initially going directly to some update.microsoft.com hosts, and at some point I see rejected requests to the local proxy server.
Therefore the question: How does one turn that off, what would be the correct search term to find the answer myself?
Meanwhile the physical machine was moved to the network segment that does not expose this issue, and it is currently updating itself just fine.
Continue reading...