locked
CAS Server issue (SCR- setup) RRS feed

  • Question

  • Hello All, 

    Need help as part of DR setup (SCR- database portibility ) where i port one of the databases for testing purpose to the DR server and after that i checked the mailboxes it was showing that it was moved to new mailbox server at DR location. All good. 

    Now when i tried to open OWA (https://webmail.domain.com/owa) it was given me an error "Outlook Web Access is not available. If the problem continues, contact technical support for your organization and tell them the following: There is no Microsoft Exchange Client Access server that has the necessary configuration in the Active Directory site where the mailbox is stored." earlier i thought it might be due to the AD replication but seems to be not.

    ON the same side when i tried to configure the outlook it worked, able to receive email but NOT send as i think i need to enable the exchange server authentication on the other side hub trsport servers receive connectors . SO what went wrong for Client Access server where i missed is anything more needs to be configured.

    What all i can check to fix the this. 

    My goal is to test the SCR database portibility where i can test the CAS and HUB server also .

    When i am trying to access the OWA for the ported database to DR site using https://localhost/owa i am able to access and log but when i am trying to access through https://webmail.domain.com/owa, getting the above mentioned error . 

    PLs help Thanks

    • Edited by Jugalkumar Friday, July 17, 2015 11:50 AM
    Friday, July 17, 2015 11:17 AM

Answers

  • Hi,

    As Nithyanandham mentioned in your other thread, we need configure autodiscover for new CAS server your DR site, and ensure the name can be resolved by DNS as well as certificate.

    Others, it seems that OWA proxy or redirection not work correctly. Please run Get-OWAVirtualDirectory | FL Identity,*Auth*,*URL* to check whether you can get OWA VD configuration in AD. If it don't return DR's CAS server, check the replication between sites first.

    Here's an blog about "OWA Cross-Site Silent Redirection", for your reference: http://blogs.technet.com/b/exchange/archive/2011/12/12/owa-cross-site-silent-redirection-in-exchange-2010-sp2.aspx

    Thanks


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    • Marked as answer by Allen_WangJF Monday, July 27, 2015 1:38 PM
    Monday, July 20, 2015 9:06 AM

All replies

  • Hi Jugalkumar ,

    After reading your description ,What i understand is that the users from the external world cannot able to access the owa after DR site is activated .However when you try to access the owa internally it is working fine without issues .

    For this issue you need to check with your internal network and security team .

    Whenever a user tries to access the webmail.domain.com it will get resolved in to an public address which would be terminated in firewall .From there they would redirect that owa request to the ip address of the cas server which is in your production site .So in your case you need ask you security team to redirect the external owa request from that firewall to the cas server which is residing in your DR site.

    In case if you wan to use namespace "webmail.domain.com" to access owa internally then you need to make sure that the namespace is resolvable on your internal DNS .

    Please reply me if you have any queries.


    Thanks & Regards S.Nithyanandham

    Friday, July 17, 2015 2:08 PM
  • No so the thing is i did the SCR- database portability not the complete site failover. In which only one database i mount to the SCR target machine. U can take this as a simple testing to check where things are working as expected or not. 

    In which i moved few users into the test database and then enable replication to target machine. dismount the database and used the restore-storagegroupcopy after that performed the move-database -configuration only . All good till here .

    Now when i tried to access the OWA with - http://localhost/owa i am able to open mailbox via OWA

    But when i tried to use the OWA with https://webmail.domain.com/owa its given me an above mentioned error. 

    So when i tried with mailbox configuration (outlook profile ) that i am able to configure and its working as well. in addition to that , on my site 1 , there are two cas servers are their with WNLB and on site 2 only one cas server So do i need to set cas -redirection or cas-proxy-ing something that ?

    Apart from this do i need to configure the Autodiscover , will it not configure automatically during the CAS server installation ?

    I got your point for need to request security team to redirect the ip to DR site cas server , but in that i have another databases/ users on site 1 , they will face the issue, so is there any way i can test for the user who has been moved to DR site .  

     
    Friday, July 17, 2015 4:56 PM
  • Hi,

    As Nithyanandham mentioned in your other thread, we need configure autodiscover for new CAS server your DR site, and ensure the name can be resolved by DNS as well as certificate.

    Others, it seems that OWA proxy or redirection not work correctly. Please run Get-OWAVirtualDirectory | FL Identity,*Auth*,*URL* to check whether you can get OWA VD configuration in AD. If it don't return DR's CAS server, check the replication between sites first.

    Here's an blog about "OWA Cross-Site Silent Redirection", for your reference: http://blogs.technet.com/b/exchange/archive/2011/12/12/owa-cross-site-silent-redirection-in-exchange-2010-sp2.aspx

    Thanks


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    • Marked as answer by Allen_WangJF Monday, July 27, 2015 1:38 PM
    Monday, July 20, 2015 9:06 AM