No one has responded to this discussion for at least a year, so this information may be out of date. If you're looking for information about this topic, please search for a more recent discussion or post a new question.

Hybrid migration Exchange 2007 on-prem

  • 3 Followers
  • 4 Replies |
  • This post has 1 verified answer |
Answered (Verified) This question is answered

Hello All

 

I will be performing a hybrid migration from on-prem 2007 sp3 to O365. The current A record for autodiscover, OWA, and OA all point to the 2007 CAS server (mail.mydomain.com) When I introduce the 2010 hybrid server do i need to chang DNS to point  mail.mydomain.com and autodiscover.mydomain.com to the 2010 hybrid server, or do i keep pointing mail.mydomain.com and autodiscover.mydomain.com to the 2007 CAS server?  I'm assuming i need to introduce a new namespace for the 2010 hybrid server, but i am not sure what purpose doing so porvides?

 

As you can see i am a bit lost on this coegisistence piece

 

  • Post Points: 20
Verified Answer
All Replies
  • Thank you Larry for the providing the link, it was helpfule.

    When i go through the Exchange Server Deployment Wizard for a Hybrid migration the task "Redirect Outlook web connections to Hybrid server" suggest's that i need to create a new namespace for the hybrid server i.e OWA.Contosos.com, and continue pointing "mail.Contoso.com" to the 2007 CAS server. The instructions in this step suggest that all usrs will hit "OWA.Contoso.com" (Hybrid server) and the Hybrid server will redirect the request to either the 2007 (mail.Contoso.com) or provide a link to OWA in O365.

    If i follow these directions then my users have to learn a new name for OWA access (OWA.Contoso). However if i pointed Mail.Contoso.com to the Hybrid server , and then configured the externalurl on the 2007 CAS Server to OWA.Contoso.com, and pointed OWA.Contoso.com to the 2007 CAS server, then users do not have to learn a new url for OWA access. Its almost like the Exchange Server Deployment wizard has it backwards? Again if i followed the wizards steps i see two things breaking until the clients are reconfigured

    #1 Outlook Anywhere. The outlook client requires that the principal name in the cert match the name thats configured in the  proxy settings in the outlook client. If OWA.Contoso.com is the principal name then this is going to break already configured Outook anywhere clients.

    #2 My users will have to be given directions on how to access thee mailbox using OWA, as they have never used OWA.Contoso.com

    • Not Ranked
    • Post Points: 0
  • Hi skipster,

     

    We can configure the cloud-based Outlook Web Application redirect during the Hybrid migration so that your user could still use the old URL for OWA, please refer the below link for detailed information:

    Configure Outlook Web App for an Exchange 2010 Hybrid Deployment

     

    In addition, for specific deployment guidance of Hybrid Deployment, please refer the below link, and you can choose different scenario as your demands:

    http://technet.microsoft.com/en-us/exdeploy2010/default.aspx#Index

     

    Thanks,

    • Not Ranked
    • Post Points: 0
  • Hi skipster,

    Thanks,JQQ.

    Is these information provied by JQQ helpful?
    Do you have any other questions?

    Thanks,
    Larry He

    • Top 150 Contributor
    • Post Points: 0
Page 1 of 1 (5 items)