Reduces site failures, easy to manage from a single pane of glass, and the support is good
What is our primary use case?
We use our devices as virtual load balancers for Exchange 2016, primarily. We have two sites with two LMs at each site in clusters. We also use the devices as global DNS services and reverse proxy/authentication servers for our external users. Our services are primarily Microsoft products being served. These include Exchange, SharePoint, CRM Dynamics, Skype, and ADFS. We are also looking at implementing websites in the future as required. SSL offloading is enabled. Our devices are set up in the network as well as the DMZ.Pros and Cons
- "The DNS Load Balancer makes it so that I don't have to worry about site failures."
- "We experienced a brief period of instability."
What other advice do I have?
My advice is to use Kemp's support to help with the initial setup. It is included in the initial cost and it makes sure that best practices are used. Keep up with the support because it's worth it. I am currently happy with everything.