Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 0 subscribers
  • Views 8234 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WSUS & Windows Updates

Dhornby

Has anyone had any issues getting WSUS and Windows Updates (Both on Windows server 2012) Through the web appliance setup as a proxy?

I can't see anything blocked but both fail (They work if I punch a direct hole through the Firewall)

Also Windows activation doesn't seem to work through the proxy for any Operating system.

Any ideas??

:38219


This thread was automatically locked due to age.
Parents
  • 0

    A common scenario encountered when dealing with proxy servers is that WinHTTP does not support authenticated connections. If your proxy server requires authentication this will block the outbound connection. You'll have to configure the proxy server to support anonymous connections from the WSUS server.

    Perhaps more significantly though is whether you should route the WSUS server through the proxy server. If you're not required by organization policy to route everything through the proxy server (and since you've already tested this going directly out the firewall, perhaps not), then I would suggest not to do so. The WSUS server is going to download gigabytes of file content on a monthly basis (particularly if you plan to use WSUS to update Defender/Office 2010 definition files), and this content is not usable by any other entity in the organization. It will just clog up the proxy cache and cause web performance issues for other clients (who now have to re-prime the cache with content that would have otherwise still been there had the WSUS server not pushed it all the way out the door).

    :38257
Reply
  • 0

    A common scenario encountered when dealing with proxy servers is that WinHTTP does not support authenticated connections. If your proxy server requires authentication this will block the outbound connection. You'll have to configure the proxy server to support anonymous connections from the WSUS server.

    Perhaps more significantly though is whether you should route the WSUS server through the proxy server. If you're not required by organization policy to route everything through the proxy server (and since you've already tested this going directly out the firewall, perhaps not), then I would suggest not to do so. The WSUS server is going to download gigabytes of file content on a monthly basis (particularly if you plan to use WSUS to update Defender/Office 2010 definition files), and this content is not usable by any other entity in the organization. It will just clog up the proxy cache and cause web performance issues for other clients (who now have to re-prime the cache with content that would have otherwise still been there had the WSUS server not pushed it all the way out the door).

    :38257
Children
No Data
Unfiltered HTML