Office 365 hybrid configuration wizard application cannot be started

Office 365 hybrid configuration wizard application cannot be started


  • Exchange Server Hybrid License for Office 365 deployment
  • Misja Geuskens
  • How to Set Up a Hybrid Office 365 and Migrate to Exchange Online
  • Introducing the Microsoft Office 365 Hybrid Configuration Wizard
  • HCW fails on intra-organization configuration
  • Exchange 2016 – “Application cannot be started” when running Hybrid wizard
  • Exchange Server Hybrid License for Office 365 deployment

    Create Support Package This is very useful for us people in support. There is a second screen once you click on the link, where you can specify to ZIP logs from the last 24 hours, or within a date range. You then have the option to copy the file to the clipboard so it can be easily attached to an email. This log is therefore not present in Classic Hybrid Configs. See here for more info on ProcDump download and syntax, we would normally use a quick command like shown below to get the stack exception but if you have to get here with troubleshooting, we advise you open a support case with us: procdump.

    It will restore the application. See more on this step here. Installation of the agent on the local computer this prompts for your Office Global Administrator credentials again. Registration of the agent in Azure, including creation of the URL used to proxy requests.

    Testing migration viability from your Office tenant to your on-premises Exchange organization via the agent. Starting with HCW version The first step is to go to that machine and check the status of the service Microsoft Hybrid Service should be started and if the Hybrid Connector is up and running.

    By checking HCW. When narrowing down registration issues, always check the installation prerequisites as mentioned here and run Test-HybridConnectivity. Check if the Hybrid Service is installed and running, reference here. You would install the agent automatically via HCW when choosing Modern Hybrid Topology or — less commonly — manually in case of installing additional Agents.

    In this folder, there is a config file of the Hybrid Service called Microsoft. You would run the Notepad as Administrator and then open this config file to edit it. The file should look like this after removing the XML comments and turning on logging: Restart the Microsoft Hybrid Services in services.

    Follow the procedure from here to attempt a connection to the connector. Navigate to these 2 folders and check the HybridService logs: C:programdataMicrosoft Hybrid ServiceLogging will have logs related to connector registration and startup.

    Validating the Hybrid Agent Once we established that the Hybrid Agent is installed, registered and running, it is time to validate its functionality.

    If the requests counter goes up when doing Test-MigrationServerAvailaility, the connector is fine. For the above example, you can narrow down the statuses between as an example for this situation. Hope you find this helpful! I realize this is not really a post that you sit down and read from end to end, but it should come in handy when troubleshooting!

    Mirela Buruiana.

    Misja Geuskens

    You use this domain as logon domain part of the User Principal Name and your email reply address. For some reason a new domain needs to be added to your existing Hybrid Exchange configuration so you can you this domain in new email addresses.

    The steps involved to add this new domain are described in this article, but before you begin you need to make sure how this new domain will be used. If you need the new domain to be added to the user mailboxes only as a mail alias, than the figuration is pretty straight forward. But if this domain needs to be used as the reply address, you also need to to decide if you keep your existing domain as part of the logon name or you also need to change that domain.

    Add the new domain to Office The first thing we need to do is add the new domain to Office Logon to the Office Admin center, go to Setup and click on Domains. Choose Add domain, enter your new domain in this example dpconsultancy. Verify domain After your domain is verified, the domain is added to Office Depending on your mailflow configuration your MX-record should point to your on-premises Exchange Server or to Exchange Online.

    On-premises Exchange configuration We also have to add the new domain to the on-premises Exchange, because from their we control the email addresses for local en online mailboxes in a Hybrid Configuration.

    Switch to your on-premises Exchange server and open the Exchange Admin Center in case of Exchange or Go to Mailflow and choose the Accepted domains tab. Click the plus sign. Exchange admin center Add your new domain as Authoritative. After verifying your credentials for the local domain and Exchange online, click Next till you see the Hybrid Domains screen.

    Make sure you check the newly added domain. Check Yes, upgrade the current configuration. Upgrade configuration The wizard will upgrade your existing configuration, for example it adds the domain to the mailflow connector between your Exchange Server and Exchange Online. When the wizard is finished you can add an email address with your new domain to your users mailboxes. Adding the new domain to your mailboxes The new domain is added to Exchange Online and your on-premises Exchange, now it needs to be added to the mailboxes.

    Depending your needs you can add a new email address with the domain manually to the mailboxes using the on-premises Exchange Admin Center or Powershell or by changing the Email Address Policy or add a new policy.

    Add new domain After you have added new email addresses via the on-premises Exchange and performing an Azure AD Connect sync the new email address is added to the Exchange Online mailbox. In the example below my UPN contains my old existing domain and my new reply address contains the new domain. Here you can add an alternative UPN Suffix your new domain. You can do this manually by changing the domain in the User account properties.

    Change UPN You can also do this in bulk. Replace "contoso. UPN and email addresses.

    How to Set Up a Hybrid Office 365 and Migrate to Exchange Online

    Later you also have to assign this certificate on the Receive Connector from the Edge Server. In most cases is this smtp. You can create the certificate signing request directly on your Edge server. After getting the signed certificate back from your public CA, import the the certificate as follows. Mutual TLS authentication between Exchange and other messaging servers. So now after copying this certficate also from the Edge to one of my internal Mailbox Servers, I can select this Mailbox Server in order to be able to select this purchased certificate for the Send- and Receive Connector of my Edge Server.

    For hybrid configuration I configured both edge servers from each AD Site.

    Introducing the Microsoft Office 365 Hybrid Configuration Wizard

    In this case also only one Outbound to Office Sendconnector is created and will be associated to both edge servers. This will configure the outbound mail connector to route mail from the the Exchange Online Protection EOP service to your Microsoft Exchange on-premises organization. When the wizard is finished you can add an email address with your new domain to your users mailboxes. Adding the new domain to your mailboxes The new domain is added to Exchange Online and your on-premises Exchange, now it needs to be added to the mailboxes.

    Depending your needs you can add a new email address with the domain manually to the mailboxes using the on-premises Exchange Admin Center or Powershell or by changing the Email Address Policy or add a new policy. Add new domain After you have added new email addresses via the on-premises Exchange and performing an Azure AD Connect sync the new email address is added to the Exchange Online mailbox.

    In the example below my UPN contains my old existing domain and my new reply address contains the new domain.

    HCW fails on intra-organization configuration

    Here you can add an alternative UPN Suffix your new domain. You can do this manually by changing the domain in the User account properties. Change UPN You can also do this in bulk. Replace "contoso. Federation fails with "An unexpected error occurred on a receive" or "An unexpected error occurred on a send.

    Exchange 2016 – “Application cannot be started” when running Hybrid wizard

    Detailed Information "An error occurred accessing Windows Live. Detailed information: "The underlying connection was closed: An unexpected error occurred on a receive. Detailed information: "The underlying connection was closed: An unexpected error occurred on a send. WebException The underlying connection was closed: An unexpected error occurred on a send.


    thoughts on “Office 365 hybrid configuration wizard application cannot be started

    Leave a Reply

    Your email address will not be published. Required fields are marked *