none
How to force proxy rather than redirect.. RRS feed

  • Question

  • Hi Guys,

    I wonder if anyone can help please?

    I have recently upgraded Exchange from 2007sp2 to 2010 sp1. I need to know if it is somehow possible to force my 2010 CAS server to proxy OWA requests to the 2007 CAS for the users who have mailboxes on the 2007 server.

    The problem i am experiencing is that the connections are being redirected as both servers are in the same site - however the redirection redirects to the local address of the 2007 CAS server which is useless. I still have 1500 mailboxes on the 2007 server which the users need to access via OWA. The mailboxes that have been moved to 2010 are accessible.

    I need to force the 2010 CAS server to proxy the requests and not redirect. Have already copied the relevant OWA files from the 2007 CAS etc.

    Help please...

    Wednesday, July 27, 2011 2:33 PM

Answers

  • Hi Dave,

     

    I appreciate your understanding that an Exchange 2010 CAS server will never proxy OWA request to an Exchange 2007 CAS server in the SAME AD site. It is by design.

     

    All requests within the same AD site are redirected to an Exchange 2007 CAS server, using either the InternalURL or ExternalURL properties for Client Access server, depending on which properties are configured.

     

    Since your Exchange 2007 server does not has external IP address, I’d suggest you setup InternalURL to allow OWA request redirected from Exchange 2010 CAS server. To do this:

     

    1.    Undo the OWA files copy, and restore Exchange 2010 OWA folder. Make sure the file version is up to date.

    2.    Run Set-OwaVirtualDirectory and set ExternalURL valut to be NULL, set InternalURL to the FQDN of Exchange 2007 server; such as https://ex2k7.company.com/owa. See here.

     

    To coexist with Exchange 2010, Exchange 2007 server must be updated to SP2 or higher.

     

    3.    Enable FBA on Exchange 20007 server as well as the firewall if there is;

    4.    Create a new internal DNS record and point the internal URL to the exchange 2007 server.

    5.    You might also need to disable the loopback check(see here);

     

    For more information, please refer to the Microsoft article below:

     

    Understanding Proxying and Redirection

    http://technet.microsoft.com/en-us/library/bb310763.aspx


    Fiona

    • Proposed as answer by Fiona_Liao Friday, July 29, 2011 7:50 AM
    • Marked as answer by Fiona_Liao Friday, July 29, 2011 9:09 AM
    Friday, July 29, 2011 7:49 AM

All replies

  • Hi,

    You can't force proxy when the servers are installed in the same site.

    You will need to assign a legacy name for the 2007 servers and use thsi for redirection.

    http://technet.microsoft.com/en-us/library/dd638158.aspx

    http://blogs.technet.com/b/sjimmie/archive/2010/07/09/owa-coexistence-with-legacy-versions.aspx

    Leif

    Wednesday, July 27, 2011 2:41 PM
  • Unfortunately, I don't think this helps me particularly since I only have 1 external IP address and only the 2010 Exchange is internet facing so there is nowhere for me to redirect to.

    Hence the reason i need the 2010 Exchange to seamlessly proxy to the 2007 server...

    This seems like a ridiculous oversight by Microsoft, there must be a way of manually specifying that you want to proxy and not redirect, surely there's hundreds of companies out there that need to run both versions whilst migrating yet don't have the internat resources for multiple host names etc...

    Any other ideas? Perhaps create an imaginary AD site to put the 2007 box into somehow, so that the 2010 thinks it is in a non internet facing site and then proxies?

    Cheers,

    Dave

    Wednesday, July 27, 2011 3:32 PM
  • Hi Dave,

     

    I appreciate your understanding that an Exchange 2010 CAS server will never proxy OWA request to an Exchange 2007 CAS server in the SAME AD site. It is by design.

     

    All requests within the same AD site are redirected to an Exchange 2007 CAS server, using either the InternalURL or ExternalURL properties for Client Access server, depending on which properties are configured.

     

    Since your Exchange 2007 server does not has external IP address, I’d suggest you setup InternalURL to allow OWA request redirected from Exchange 2010 CAS server. To do this:

     

    1.    Undo the OWA files copy, and restore Exchange 2010 OWA folder. Make sure the file version is up to date.

    2.    Run Set-OwaVirtualDirectory and set ExternalURL valut to be NULL, set InternalURL to the FQDN of Exchange 2007 server; such as https://ex2k7.company.com/owa. See here.

     

    To coexist with Exchange 2010, Exchange 2007 server must be updated to SP2 or higher.

     

    3.    Enable FBA on Exchange 20007 server as well as the firewall if there is;

    4.    Create a new internal DNS record and point the internal URL to the exchange 2007 server.

    5.    You might also need to disable the loopback check(see here);

     

    For more information, please refer to the Microsoft article below:

     

    Understanding Proxying and Redirection

    http://technet.microsoft.com/en-us/library/bb310763.aspx


    Fiona

    • Proposed as answer by Fiona_Liao Friday, July 29, 2011 7:50 AM
    • Marked as answer by Fiona_Liao Friday, July 29, 2011 9:09 AM
    Friday, July 29, 2011 7:49 AM
  • Hi Guys,

    Our company is experiencing the exact same issue that Dave is describing (except for EWS). Is there any update on this problem?

    I understand that by design, "an Exchange 2010 CAS server will never proxy OWA request to an Exchange 2007 CAS server in the SAME AD site". However, there MUST be a way to make force proxy between between an Exchange 2010 CAS server and an Exchange 2007 CAS server in the same AD site given the fact that this would work for an Exchange 2010 CAS server and an Exchange 2007 CAS server in DIFFERENT AD site.

    I fully understand that this may involve taking steps not necessarily supported by MS, officially; nonetheless, I'd still like toknow how if there is a way.

    Again, to restate my question "Is there any way to force an Exchange 2010 CAS server to proxy EWS request to an Exchange 2007 CAS server in the same AD Site?" Thank you for any suggestion within or outside of MS domain.

     

    Thanks,

    Nick

    Wednesday, November 23, 2011 12:19 AM
  • this is how I work around in this "same site" proxy scenario

    https://blogs.technet.microsoft.com/exchange/2009/12/02/upgrading-outlook-web-app-to-exchange-2010/#comment-168263

    Can’t do same AD site but can do same physical site but two AD sites.  You can create another AD site and put 2007 servers in there and have CAS2010 proxy to CAS2007.

    no need to change ip of any exchange server,
    just create new AD site which is subset of existing "Default-First-Site-Name"
    then move exchange server to that new site,

    it call catch all subnet
    https://community.spiceworks.com/topic/157933-1-subnet-covering-multiple-active-directory-sites

    subnet can be overlap/subset in Active Directory site
    https://technet.microsoft.com/en-us/library/2009.06.subnets.aspx

    move exchange server to separate site,  single ip AD site
    https://blogs.technet.microsoft.com/marwahasamir/2011/12/16/moving-dag-nodes-between-ad-sites/

    Moving Exchange Server 2010 from an Active Directory Site ( ignore about demote dc part )
    http://msexchangeteam.in/moving-exchange-server-2010-from-an-active-directory-site/

    check replication between AD site    after move exchange to new site
    http://www.careexchange.in/moving-exchange-2016-server-to-another-active-directory-site/

    Step-By-Step: Setting Up Active Directory Sites, Subnets & Site-Links
    https://blogs.technet.microsoft.com/canitpro/2015/03/03/step-by-step-setting-up-active-directory-sites-subnets-site-links/

    test,   proxy traffic from 2010 CAS to 2007 CAS between site scenario


    Understanding Proxying and Redirection
    https://technet.microsoft.com/en-us/library/bb310763%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396

    this is by design !!!
    An Exchange 2010 Client Access server will never proxy Outlook Web App requests to an Exchange 2007 Client Access server in the same Active Directory site.

    !!! Outlook out-of-office will not work in this scenario  if

    In any Exchange organization that contains mailboxes on an Exchange 2007 Mailbox server, there must be an externally accessible Exchange 2007 Client Access server. When the Autodiscover service returns the correct Exchange Web Services URL to a requesting client, this URL matches the version of server that the user’s mailbox is on. For any Exchange organization that contains mailboxes on both Exchange 2007 Mailbox servers and Exchange 2010 Mailbox servers, two external URL’s must be configured for Exchange Web Services, one for each installed version of Exchange.

    • Proposed as answer by snoopz1 Friday, May 12, 2017 9:06 PM
    Friday, May 12, 2017 9:05 PM