Reverse Proxy

An often-overlooked component of a deployment can be the requirement for a reverse proxy server when enabling remote access. Microsoft Thread Management Gateway has been the default position for a reverse proxy, but any product that can support the required functionality will work. The typical requirements for a reverse proxy are not nearly as high as for a Lync Server role but do consume some resources on a host. You should see your specific reverse-proxies documentation for virtualization requirements and support, and remember to include these requirements if you plan to have the reverse proxy on the same host as a Lync Server role.