Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

  1. Kemp Support
  2. Knowledge Base
  3. Content Delivery

Exchange 2019 - OWA doesn't works with multiple Real Servers

Updated: 

 

Information

 

Summary:

When we add more than one server in the OWA sub-services as Real Servers, we can't log in to the OWA.
Environment:

Product: Loadmaster

Version: Any

Platform: Any

Application: Exchange
Question/Problem Description:

When we add more than one server in the OWA sub-services as Real Servers, we can't log in to the OWA. we can see that the login was successful. But after a second you are back on the OWA login screen. But if we have only one server, then it works.
Steps to Reproduce:  
Error Message:  
Defect Number:  
Enhancement Number:  
Cause:  
Resolution:

This is something with the CU update on the exchange where Persistence is required.

Can you enable persistence as source IP or Super HTTP on KEMP for the following SubVS

Virtual Services -> View/Modify Services -> Exchange 2019 -> - Modify -> SubVSs -> Exchange 2019- Authentication Proxy - Modify -> Standard Options -> Persistence Options

Virtual Services -> View/Modify Services -> Exchange 2019 -> Modify -> SubVSs -> Exchange 2019-OWA - Modify -> Standard Options -> Persistence Options

The default timeout can be set as 15 min.

exchange.PNG

A number of users report login issues when load balancing. The solution of settings persistence resolves this.
Workaround:  
Notes: Exchange CU update details
Was this article helpful?
0 out of 0 found this helpful

Comments

In this document