Reverse Proxy for Microsoft Exchange

With the end-of-life of Microsoft’s Threat Management Gateway (TMG), Exchange administrators are faced with the question of how to replace the reverse proxy features of TMG. Some admins may take the view that while Microsoft continue to offer support, they see no reason to replace TMG while others are searching for solutions that will fill the TMG roles.

Acting as a reverse proxy in front of an Exchange deployment is one of the major TMG roles and replacement can be addressed in a number of ways such as using Application Request Routing (ARR) or by deploying a load balancer. As a reverse proxy, TMG also implemented features such as session logging, Kerberos authentication, content caching, compression and application layer protection. While ARR offers a way to implement the load balancing component of TMG, it does not offer the depth of features that TMG provided.

The above list is not exhaustive but gives an indication of how a LoadMaster not only delivers the TMG reverse proxy feature set but adds significant additional value in a future-proofed and scalable package.