locked
OWA Redirection from Exchange 2013 to 2007 RRS feed

  • Question

  • Hi,

    I have Exchange 2013 and 2007 running in coexistence and Outlook clients can connect to their respective mailboxes.

    I am however going round in circles now with OWA which I am currently testing internally first before rolling out to external users.

    I've read and followed various articles and seem to be getting a step closer each time and hopefully someone can point me in the right direction for the final hurdle!

    The issue we are having is as follows:

    We enter URL of https://mail.mycompany.com/owa which in turn presents the 2013 OWA page.  We enter credentials for a 2013 mailbox user and get straight into OWA no problems at all.

    So we do the same with a 2007 mailbox user, enter credentials "domain\user", OWA redirects and presents a second login screen which I can see is to connect to the legacy.mycompany.com/owa site.

    However after entering the credentials for the second time, the web page refreshes and takes the user back the original 2013 landing page.

    Grateful for any suggestions.

    Many thanks

    Chris

    Wednesday, July 24, 2013 3:27 PM

Answers

  • Hi,
    Having to log on twice is not very user friendly, so installing CU2 is a good thing.
    You can read about changes made in CU2 here


    Yea, check if any VDir in Exchange 2007 has redirection configured.
    You should be able to log on directly using the URL https://legacy.domain.com/owa with a mailbox on EX07.


    Martina Miskovic

    Wednesday, July 24, 2013 4:18 PM
  • Your firewall should redirect the traffic for legacy to your Exchange 2007 Server and mail to your Exchange 2013 Server. Both legacy and mail must be accessible from external source as well as internal.

    If your firewall can't differentiate the traffic on the FQDN or something, then you'll need to use two NAT Rules.


    Martina Miskovic

    • Marked as answer by whorahaha Friday, July 26, 2013 10:20 AM
    Wednesday, July 24, 2013 7:11 PM

All replies

  • Hi,
    Why not install CU2 so that you'll get a single sign-on experience?

    If you have redirection configured in IIS on the Exchange 2007 Server...Make sure that the Virtual Directories doesn't have it configured.

    Have you changed the Internal- and ExternalUrl for OWAVirtualdirectory on EX07 to legacy?


    Martina Miskovic

    Wednesday, July 24, 2013 3:48 PM
  • Hi,
    Why not install CU2 so that you'll get a single sign-on experience?

    If you have redirection configured in IIS on the Exchange 2007 Server...Make sure that the Virtual Directories doesn't have it configured.

    Have you changed the Internal- and ExternalUrl for OWAVirtualdirectory on EX07 to legacy?


    Martina Miskovic

    Hi

    I'm just in the process of downloading CU2 at the moment, the URLs on EX07 are as follows:

    Internal https://EX07serverFQDN/owa (this entry was already like this prior to coexistence, I have changed this to the same as the external and result is still the same)

    External https://legacy.mycompany.com/owa

    No IIS changes have been made on EX07 server but I will double check.

    I'll see if the CU2 makes a difference also.

    Thanks,

    Chris

    Wednesday, July 24, 2013 4:08 PM
  • Hi,
    Having to log on twice is not very user friendly, so installing CU2 is a good thing.
    You can read about changes made in CU2 here


    Yea, check if any VDir in Exchange 2007 has redirection configured.
    You should be able to log on directly using the URL https://legacy.domain.com/owa with a mailbox on EX07.


    Martina Miskovic

    Wednesday, July 24, 2013 4:18 PM
  • Hi,

    Yea the legacy.domain log on works just fine and goes straight EX07 mailbox, now just waiting for the CU2 to finish installing and checking the VDir in the meantime.

    Thanks,

    Chris

    Wednesday, July 24, 2013 5:05 PM
  • Hi

    So the CU2 install is now completed and internally everything is working as it should, hooray :) and no second sign in :)

    Unfortunately, coming in externally I can get as far as the 2013 OWA mailbox but when I try an EX07 account Chrome reports "Webpage has redirect loop" and IE just sits there with a timer.

    I can see in the browser bar it changes to legacy but doesn't reach the mailbox.  I really thought if the internal redirection works then external should.

    I changed the Static NAT rule on the Cisco firewall to point at the new EX2013 server, I can't see anything else to change now.

    Most grateful for any further suggestions

    Thanks

    Chris

    Wednesday, July 24, 2013 6:35 PM
  • One step in the right direction at least :)

    Can you confirm that https://legacy.domain.com/owa works from external source?

    Martina Miskovic

    Wednesday, July 24, 2013 6:46 PM
  • Certainly is :)

    well the https://legacy.domain.com/owa has the same error externally as well :(

    I have already added the public dns for this via my ISP, so legacy.mycompany.com points back to the same external IP as our mail.mycompany.com

    This then hits our firewall and the static NAT points to the EX2013 server which combined with internal DNS would take care of the EX07 requests.

    Am I missing something obvious here?

    Wednesday, July 24, 2013 7:03 PM
  • Your firewall should redirect the traffic for legacy to your Exchange 2007 Server and mail to your Exchange 2013 Server. Both legacy and mail must be accessible from external source as well as internal.

    If your firewall can't differentiate the traffic on the FQDN or something, then you'll need to use two NAT Rules.


    Martina Miskovic

    • Marked as answer by whorahaha Friday, July 26, 2013 10:20 AM
    Wednesday, July 24, 2013 7:11 PM
  • Hi,

    Try to publish the legacy Exchange 2007 server as a separate Exchange 2013 rule on firewall.

     

    Hope it is helpful

    Mavis

    Thursday, July 25, 2013 12:04 PM
  • Thanks, still trying to get this resolved with external legacy access, proving tricky to get the Cisco firewall config to play ball on this :(

    Frustrating as this must be the final piece of the puzzle

    I will tick a solution once resolved :-)
    Thursday, July 25, 2013 5:16 PM
  • Thanks Martina, a combination CU2, Public IP/DNS and Firewall rules, everything is working correctly, a great way to finish my week off :)
    Friday, July 26, 2013 10:21 AM
  • If you cant use legacy and need to use the servername is that ok as well? We have updated our v directories to the servername.
    Wednesday, September 30, 2015 6:50 PM
  • Hi whorahaha,

    I have what seems to be the same issue you had.

    internally OWA working, and redirectly to Exchange 2007 accounts fine.

    once i change my firewall to point to Exchange 2013, OWA its not routing properly for Exchange 2007 accounts (looping it seems).

    Want changes did you do regarding Public IP or DNS and firewall rules?

    Friday, November 20, 2015 5:38 AM