Forum Discussion

Lussy150's avatar
Lussy150
Copper Contributor
Dec 23, 2022
Solved

Prepare Exchange 2019 for Hybrid Configuration Wizard

Greetings! This particular environment is new to me and I'm assigned the task of migrating to Exchange Hybrid. After an initial assessment, I concluded that I require your feedback since the environ...
exchange online
Exchange Server
hybrid
  • Ahmed_Masoud97's avatar
    Ahmed_Masoud97
    Dec 23, 2022

    Hello Lussy150 

    here is Ahmed a community visitor 😉

    Let me try to help you 🙂

     

    There are a few steps you can take to ensure that your environment is ready for the migration:

     

    Configure external URLs for all virtual directories: You can use the Exchange Management Console or the Exchange Management Shell to configure external URLs for all virtual directories. This will allow Exchange Online to communicate with your on-premises Exchange server.

     

    Configure Autodiscover: You can use the Exchange Management Console or the Exchange Management Shell to configure Autodiscover so that it is reachable from both on-premises and off-premises. You may also want to consider using a split DNS configuration to ensure that Autodiscover is reachable from both on-premises and off-premises.

     

    Obtain a certificate: You will need to obtain a certificate that includes the required subject alternative names (SANs) for your Exchange server. The SANs should include your Exchange server's public FQDN, as well as the Exchange Online domains. You can use a publicly signed certificate from a trusted certificate authority (CA) such as Let's Encrypt, or you can use a self-signed certificate.

     

    Configure DNS records: You will need to update your DNS records to reflect the new configuration of your Exchange server. This may include updating the MX records for your domain and subdomains to point to Exchange Online.

     

    Run the Hybrid Configuration Wizard: Once you have completed the above steps, you can run the Hybrid Configuration Wizard (HCW) to complete the migration to.


    Best of the best 🙂

    Ahme:D

Lussy150's avatar
Lussy150
Copper Contributor
Dec 29, 2022

Ahmed_Masoud97 

 

Thank you for your reply.

Only a few more questions left which I would appreciate help with.

 

  1. Autodiscover currently does not have an internal or an external URL configured. It is working though (internally on-prem only) through an SRV record and an existing SCP entry. Will adding/setting an external URL mess with the internal on-prem Autodiscover service in any way?  And since we are on topic, what, if anything, triggers the SCP entry in ADDS to change?
  2. For a hybrid environment, will a certificate work that has both the .local and the .com SANs? I have not mixed local and public domains in a certificate before. 

Thanks!

Ahmed_Masoud97's avatar
Ahmed_Masoud97
Iron Contributor
Dec 29, 2022

Hello Lussy150,

 

Thanks for updating me...

 

I'v checked for you: 

  1. Configure Autodiscover: You can use the Exchange Management Console or the Exchange Management Shell to configure both an internal and an external Autodiscover URL. This will ensure that Autodiscover is reachable from both on-premises and off-premises. You may also want to consider using a split DNS configuration to ensure that Autodiscover is reachable from both on-premises and off-premises.

  2. Obtain a certificate: You will need to obtain a certificate that includes the required subject alternative names (SANs) for your Exchange server and Exchange Online. The SANs should include the FQDNs for both your on-premises Exchange server and the Exchange Online domains. It is generally recommended to use a publicly signed certificate from a trusted certificate authority (CA) rather than a self-signed certificate.

    I hope I could answer your questions! Otherwise, please let me know!
    Best of the Best:)
    Ahme:D

  • Lussy150's avatar
    Lussy150
    Copper Contributor
    Dec 29, 2022

    Ahmed_Masoud97 

     

    I do have one more question for which I couldn't find a clear answer. 

    Regarding on-prem domain joined clients and Autodiscover. Would, with Exchange 2019, an internal Autodiscover URL and DNS entry even be required? Or would AD DS SCP lookup work anyways without any additional configuration?

    Because if so, wouldn't it be almost impossible to break on-prem Autodiscover for domain joined clients since the first thing the clients query for, before any URL's, is the SCP?

     

    Thanks!

    • Ahmed_Masoud97's avatar
      Ahmed_Masoud97
      Iron Contributor
      Dec 29, 2022
      domain joined clients in an Exchange 2019 environment will typically use the Active Directory Service Connection Point (SCP) to locate the Autodiscover service. However, it is generally recommended to also configure an internal Autodiscover URL and use a split DNS configuration to ensure that the Autodiscover service is reachable from both on-premises and off-premises. It is important to properly configure and test the Autodiscover service to avoid potential connectivity issues.

      Best of the Best:)
      Ahme:D

Resources