What is your primary use case for Kemp LoadMaster?

I use Kemp LoadMaster for the application delivery controller. I have a couple of applications hosted behind the load balancer.

I use Kemp LoadMaster in my company as a replacement for Microsoft Forefront Threat Management Gateway and as a load balancer for Microsoft Exchange services in an on-premises environment. Nowadays, I use Kemp LoadMaster as an application load balancer for SQL Server, DNS servers, and different applications where load balancing is possible.

For one major customer, we installed the Kemp Loadmaster as before this I was in security and firewall. But it was requested by Microsoft that there needs to be a Load Balancer in front of the exchange platform. So Kemp is used as a Load Balancer.

The solution is used for load balancing the servers.

My primary use case for this solution is load balancing and application load balancing.

We primarily use this solution as an application load balancer internally and externally for load balancing of web-based software.

My primary use case of this solution is as a web application firewall.

We use an on-premises Skype for Business Server VoIP service that utilizes the Kemp LoadMaster LM-2400 for service resiliency. This allows our three front-end servers to seamlessly support our service. We never miss a call and our chat service is always ready as a result. Kemp has a pre-made virtual service profile that perfectly fits our use case so the initial setup is quite easy. We also have expanded the use of the LoadMaster to accommodate a number of ancillary services that also require resilience.

Our primary use case of this solution is for simple things like balancing web servers or balancing remote desktop servers. My company is based in Brazil. We are resellers of this solution, usually to small and middle size businesses.

Our primary use is to provide application load balancing for inbound SMTP mail and webmail for Microsoft Exchange. We have also used the product to load balance Citrix applications and delivery controllers. In our Citrix environment, it is much easier to implement, manage, and use versus Citrix's own Netscaler that we have used in the past.

Our primary use case is to synchronize mail to mobile devices and specifically, the Outlook application on laptops. I have a virtualized environment that contains Exchange Server 2016 and I need a service in the DMZ that knows how to handle emails that have arrived, as a reverse proxy product. My employees are using mobile phones like Samsung. They need to be able to send and receive emails anywhere with their mobile phones and laptops, so now, for about one year, we are working with Kemp and the users are satisfied. There is no complaining, as they had done before.

The primary use case of this solution was to replace our Citrix Netscaler and help us load balance traffic for solutions such as Citrix, Exchange, RDP, as well as for web servers using HTTP and SMTP.

We have several customers for different services. We have built services on private cloud libraries. We load Java and Python. A lot of these applications interact at multiple data points. For that, we use software load balancers.

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.

We use the Kemp Loadmaster to load-balance enterprise-wide applications that require high-availability. We also wanted to make sure the performance and throughput meet the needs of the usage of our applications. These applications include Microsoft Exchange, Microsoft Active Directory Federation Services (ADFS), Microsoft SharePoint (2010, 2013), file sharing servers, multiple public-facing websites, multiple internal websites, on-premise IT Service Management applications, and others. The LoadMaster handles both production and development environments for these applications.

Our organization provides resources for public safety. For continuous service and support, we need to run our system with high availability and avoid failures or downtime. Kemp LoadMaster helps us achieve this goal by utilizing the Kemp LoadMaster virtual appliance in our VMware environment. Kemp LoadMaster allows us to provide load balancing and high availability to our web and API services for internal and public use, making sure that public safety is not put at risk. Along with making sure public safety is not put at risk, Kemp LoadMaster allows us to keep our web services secure by adding another security layer with its web application firewall and IPS.

We acquired Kemp LoadMaster initially to balance our Exchange multi-site environment. We configured it and now balance the Autodiscover, OWA, and mail services for our three Exchange services in three different sites. Everything flows and works without issues. As time went on, we added other services such as RDP connections, online banking, and other applications to the LM to balance the load, which made our operations even more efficient.

We use it to load balance our ADFS serves. We also have it set up at our DR location when we need to switch over to DR. We have it set up and just flip the server over and since we have it set up at DR, once the IPs are swapped to the new DR IP range it picks up and starts working in our DR location. We also use it for our main application. We have multiple app servers that people log on to which allows us to keep the logins spread out among the servers. And if we need to take one down we can force the user to one server.

We use the Kemp Load balancer with our on-premise Exchange 2016 using two servers on a DAG at different locations. The Kemp load balancer allows us to have a hands-off failover between servers either in a Disaster Recovery model or during upgrades for security patches or service pack updates for the Exchange software. We are now expanding this for our corporate webserver that will also be hosted at both of our locations. We have more confidence in having on-premise applications than trusting the Cloud.

We use Kemp to balance the load of connections to various places. We have IIS, RDP, API, gateway servers, and objects that get over 5000 connections that are balanced with Kemp. We have had very good success at getting this working properly and doing exactly what we need. We need to balance resources and utilize the Kemp Loadmaster to organize the servers and resources to keep them operating at an optimal level. RDP and Gateway servers are 99.99% uptime so having Kemp in the middle makes that an easy transition if there is an outage or server error.

We use LoadMaster for load balancing our Exchange, Skype for Business, LDAP, Citrix, and SharePoint solutions. We have virtual services setup for traffic originating from inside and outside our network and can manage them separately. These sites each have certificates and we can update and manage them in one place, which is really helpful with our wildcard certificate that applies to multiple services. We also use the load balancers to manage some security protocols we want to allow or deny per application.

We use LoadMaster for HA Clustered Pair Load Balancer for primarily Exchange on-premises deployment and all supporting services (SMTP, ActiveSync, Autodiscovery, OWA/EWS, etc.) Secondarily, for non-Exchange, application-server-based mail routing. We implemented in 2014 as a dedicated load handling solution for inbound on-prem internal Exchange SMTP. We soon adapted the appliances to handle more tasks such as VIP-based routing to our middleware MTAs, mobile devices via ActiveSync, Outlook Autodiscover services Exchange Web Services & Outlook Web Access.

We use Kemp LoadMaster for our SharePoint environment, worldwide. We use Kemp to improve the security and availability of our web services, to external customers and partners, as well as a custom banquet application that is accessed over a cloud connection. The Kemp LoadMaster gives us load balancing and reverse proxy capabilities, as well as a web application firewall to protect our web application environment and website. We use the technology across the entire organization to solve the issue of site performance and availability for external users when booking and managing events.

Kemp LoadMaster is used in our server for load balancing. Our organization produces software for public sectors like Transport, Healthcare, and Banking system. For continuous service and support, we need to run our system with high availability and avoid failures. Thus, the Kemp LoadMaster helps us to give continuous service to reach and is accessed by our clients.

Our company e-mail and mobile communication system, which is based on Exchange Servers, needed load-balancing and security. After a few discussions with resellers and external consultants, we decided on the Kemp Load Balancer solution. Our installation is a virtual Kemp Load Balancer based on VMware. We have configured four Exchange Servers in a DAG configuration and we have been very satisfied since it was installed. In the future, we would like to map further services via the Kemp.

We use this to load balance internal and external IT systems ranging from a few connections per minute to well over 10k connections per minute. We also leverage the Global WAF features that Kemp offers. We run these LoadMasters in an HA environment, to better allow for failovers and increased uptime. We use to balance HTTP/HTTPS traffic on the public internet for public sites, some with near 0k connections per minute. We also use to balance internal IT services such as LDAP, LDAPS, and DNS through various VIPs.

I use Kemp LoadMaster as a load balancer for my web applications. All web servers (all technologies) are available through the Kemp LoadMaster so all users use the transparent load balancer.

Our primary use for the Kemp LoadMaster is load balancing our exchange and IIS web services to be able to meet the high availability standard for our organization. We get additional security features so there is no need to make these configuration steps on a server again. With the offloading capability, you can even secure servers that normally can't be secured. Currently, we are using it with our web servers and exchange, for both internal and external access. Also, the reverse proxy is one of the greatest benefits.

We have a small number of internal web servers that we host on-premises in our data center, along with other services that need to be accessible from the public internet. These include Remote Desktop servers, an SFTP server, Exchange, etc. All of these servers need extra protection on top of our standard firewall, intrusion detection, and endpoint protection. The primary use case of Kemp is the reverse proxy for added protection, and load balancing for better performance. We are able to leverage Kemp to protect our web servers by adding content rules and restrictions. We will continue to add more resources as needed behind Kemp.

We currently utilize the Kemp LoadMaster VLM-500 series virtual appliances in our VMware environment. Initially, we were running with only a single appliance, but recently added a second to allow for High Availability pairing between them. Our primary use for the LoadMaster appliances is to provide load balancing between our two Microsoft Exchange servers in our Office 365 hybrid environment. This has allowed us to obtain redundancy between them, rather than having a single point of failure for our email environment.

We are using Kemp as a reverse proxy for Microsoft Exchange. We are also using the product for load-balancing internal services. The Kemp virtual appliance is installed in the DMZ and forwards the traffic to the internal servers. We configured the Edge Security Pack (ESP) so that the virtual appliance captures the credentials of the user, validates those against the authentication services, and then lets the user pass through. Using this solution, it doesn't publish Exchange servers directly over the internet, thus providing security.

Previously, we were using the Microsoft TMG server as a proxy to protect our Exchange server. We recently decided to upgrade the Exchange server, but the MS TMG server support had expired. I was looking for a solution that could provide a similar function. While I was talking to a consultant, they recommended the Kemp load balancer. On top of the proxy server, I also configured Exchange with DAG, so we needed load balancing as well. After reviewing the product, we installed it and it's doing a great job.

We currently use multiple Kemp appliances to load-balance the delivery of email to our CAS\Mailbox environment. Previously, we had multiple CAS servers and Mailbox servers and Kemp was handling that environment greatly. We also used it to migrate to a Single CAS with multiple DAGs. The process was very simple on the Kemp side. We also are using it to assist us with uptime due to any possible maintenance windows we have and/or any troubleshooting with the server environment. Kemp allows us to reboot servers and not affect mail delivery, as it will still deliver to a different node.

I used it as a front end to an RDS Farm. Its load-balancing port 80 and port 443 to multiple RDS Gateways. It's deployed as a virtual appliance on an on-prem virtual machine hosted on the Hyper-V server. Kemp LoadMaster is used by more than 1,000 internal users on a daily bases to access the application system at the back end. It's not exposed to the internet, it's used only from internal users inside the corporate LAN. We have daily VM backups setup as well as application backups from inside KEMP.

Our use case included product testing on how to configure the load balancing products. My primary use case is to deploy the load balancer. We provide the deployment professional service to the end-user. Due to Singapore's government policy, government sectors do not allow the connection of the internet. Therefore, we will be the hands and legs of the Kemp professional service. We will seek advice from the Kemp professional service team before and after every time we onsite to the customer's site.

The client required an infrastructure solution for the internal development team that was complaining regarding the performance and issues with the previous open-source solution. The usual infrastructure staging/development/production is available to the development team. Kemp LoadMaster serves as the internal load balancer for the application and web security layer with the Intrusion Prevention (IPS) and Web Application Firewall (WAF) that replace the opensource solution previously implemented.

The primary use case of this solution is for load balancing websites, load balancing Citrix solutions, and load balancing Microsoft Dynamics.

Our primary use case is for load balancing traffic for solutions such as Exchange and Skype, as well as for web servers using HTTP and SMTP. Another team is in charge of operating this solution.

We implement it for our customers and we have every different version available from Kemp. The primary use case is for load balancing for different applications, mostly Microsoft Exchange. We use the on-prem deployment model.

I have worked with Kemp products for at least 10 years, as a consultant. In most cases, they are used for load balancing Exchange environments, but also as reverse proxies for other workloads such as Skype for Business, ADFS, etc. The customer environments vary greatly. In most scenarios, it’s up to 2,000 users but in some cases more than 30,000. My last case involving Kemp was an Exchange 2016 site-resilient solution with 12 servers for 35,000 mailboxes.