-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We need a Proxy Server (TMG?) for the external web access #12
Comments
I would recommend using Web Application Proxy as Rev. Proxy, since TMG has been discontinued AFAIK. Web Application Proxy is a WS2012 builtin Server Feature. Instructions to deploy can be found here: https://www.microsoft.com/en-us/download/details.aspx?id=44940 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://technet.microsoft.com/en-us/library/mt346419.aspx
Keeping that in mind, these are the components you're going to need to keep in mind for deploying your Edge successfully:
Edge Servers
Reverse proxies
Firewalls
Directors (these are optional, and if they're included, they'll be located on your internal network)
Load Balancers (you can have DNS load balancing or a hardware load balancer (HLB), but for a single Edge Server, this isn't needed)
The text was updated successfully, but these errors were encountered: