Sure, it sounds obvious, right? However, configuring a proxy (and configuring the proxy) for Surface Hub is a task not to be taken lightly.
If you refer to the Surface Hub Administrators Guide, there are specific asks and requirements for proxy settings that will help you go through the installation phase successfully, and save you from ongoing issues going forward. If you're using Office 365 services for your Surface Hub, your environment should already be aligned with the requirements to bypass proxy for Office 365's FQDNs and CIDRs.
The proxy settings page for Surface Hub is identical to all Windows 10 proxy settings pages, with the exception of the authentication option that's exclusive for Surface Hub.
Let's cover these options from the bottom up:
The 'Manual proxy setup' option is the one where your clients' web requests will be redirected to a proxy service in your organization:
The 'Use setup script' option will refer your clients to a file share that hosts a PAC (Proxy Auto-Configuration) file.
The 'Automatically detect settings' option is the default one and will be used automatically to determine whether you don't have a proxy (if your Hub is hosted outside of your organization network, for example) or if you have DNS WPAD configured.
But there's a catch...
All proxy settings can only be configured after you completed OOBE and have access to the Settings app on the Hub.
What if you want to have the proxy configured on the hub before and during OOBE? Luckily, there's a workaround for that:
DHCP option 252 is part of the automatic discovery process for proxy servers in a Windows environment and is supported with Surface Hub.
To configure option 252 on your DHCP server, right-click your IPv4 scope and chose "Set Predefined Options..." and then "Add".
- In the Name field, type: WPAD
- In Data type, choose: String
- In the Code field, type: 252
After hitting "OK", you can enter the url for your PAC file:
And click "OK" again to finish the configuration.
There's no need to assign this option to the entire scope. Instead, you should configure a reservation for your Surface Hub(s) on your DHCP server and enable the 252 option exclusively for the reserved addresses:
When (re)started, Surface Hub will pick up the proxy configuration from DHCP using the setting in option 252.