Issue with Slow OWA Login After Migrating from Exchange 2013 to Exchange 2016

Moshiur (Moshiur Khan) 40 Reputation points
2024-10-15T10:13:13.01+00:00

Hello everyone, I recently migrated from Exchange Server 2013 to Exchange Server 2016. After the migration, I'm experiencing some issues with OWA on one of my Exchange servers.

When I try to log in to OWA using localhost on this server, it takes a long time to log in. Despite installing the latest Security Updates and updating the Client Access Server (CAS), the issue persists. Has anyone else encountered a similar issue after a migration, and what steps did you take to resolve it? Thanks in advance!

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,332 questions
Windows Server Migration
Windows Server Migration
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Migration: The process of making existing applications and data work on a different computer or operating system.
433 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Jake Zhang-MSFT 6,375 Reputation points Microsoft Vendor
    2024-10-16T05:49:14.26+00:00

    Hi @Moshiur (Moshiur Khan) ,

    Welcome to the Microsoft Q&A platform!

    Based on your description, it is not uncommon to encounter OWA issues after migrating from Exchange Server 2013 to Exchange Server 2016. Here are a few steps you can take to troubleshoot and potentially resolve the issue:

     

    1. Since you are experiencing delays when logging into OWA using localhost, there may be some network delays or DNS resolution issues. Make sure the server's network configuration is correct and there are no issues with the DNS settings.

     

    1. Check Event Viewer on the Exchange server for any warnings or errors that may give you more insight into what is causing the delay. Look for events related to OWA, IIS, or authentication.

     

    1. Sometimes, an IIS reset can resolve issues with OWA. You can do this by running iisreset from an elevated command prompt.

     

    1. Verify that the authentication settings for OWA are configured correctly. Incorrect settings can cause delays in the logon process.

     

    1. Make sure the OWA virtual directory URL is set correctly. You can check and configure these settings using the Exchange Management Shell.

     

    1. Use performance counters to monitor the performance of the server. This can help determine if the issue is related to resource utilization.

     

    1. Make sure you have installed the latest cumulative updates for Exchange Server 2016. There have been issues in the past that were resolved by installing the latest updates.

     

    1. If the issue is specific to a certain mailbox, try migrating the mailbox to another database and see if the issue persists.

     

    1. Create a new test mailbox and see if you experience the same delay when logging into OWA. This can help determine if the issue is related to the mailbox or server configuration.

     

    1. Make sure your SSL certificate is configured correctly and is not expired. Certificate issues can sometimes cause delays in the logon process.

     

    1. If you use a load balancer, make sure it is configured correctly and there are no issues with the load balancing configuration.

     

    1. Check if your antivirus or firewall is causing the delay. Sometimes these can interfere with the OWA logon process.

     

    These are some general steps that can help you diagnose and possibly resolve the issue. If the issue persists, it may be helpful to provide more details about your environment and any specific error messages you see. This can help narrow down the cause of the delay.


    Please feel free to contact me for any updates. And if this helps, don't forget to mark it as an answer.

    Best,

    Jake Zhang


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.