Run the Hybrid Configuration Wizard (HCW) (2024)

This Post Has 39 Comments

1. Hello ALI, thank you for everything!!! I’d like to know if the FQDN on the Exchange server (mail.exoip.com) represents the host name we’ve configured on the virtual directories.

   Reply

2. If I follow this all the way through as described, will the mailboxes automatically get transferred? I would like to manually move mailboxes in batches as opposed to an automatic move when the wizard completes!

   Reply

   1. Nothing will happen to the on-premises mailboxes after you go through the steps.

      The HCW will ensure an Exchange Hybrid deployment between two Exchange environments.

      After that, you can start migrating mailboxes to Microsoft 365.

      Reply

3. Hi,

   Thank for this awesome article.

   I am receiving a Hybrid agent setup failing on the “Validating Hybrid Agent for Exchange usage error”.

   Guidance to resolve this issue would be highly appreciated.

   Reply

4. I cannot complete the HCW after i executed your MonitorExchangeAuthCertificate.ps1 script to renew the server auth certificate.
   It stuck at the task “configure email flow” with error message HCW8099 – command not recognized. Please verify you have the correct Management Role assigned to your account.
   In the log file i see this: “cmdlet New-InboundConnector is not present in the role definition of the current user”.
   I checked the Organization Management Role but the user is included.

   Do you have any ideas maybe?

   Reply

5. Just want to thank you Ali for your most valuable articles, itis really helpful for me, you almost covered all aspect of Exchange servers.

   Reply

6. Hi,

   Very nice article

   If I’m running a 2019 on premise exchange environment and only want to run the HCW as a pre requisite for enabling modern auth is there anything else I need to do differently other than select the Classic hybrid topology option? At the end do I still transfer the objects online ?

   Many thanks

   Reply

7. Is it okay to re-run Hybrid Configuration Wizard when we’re having issues? We are currently facing issues all of a sudden about Free-Busy schedule between 2 environments. Both environments used to be able to see each other’s Free-Busy schedule but a few days ago, our on-prem users are not able to see our Cloud user’s free-busy sched. Whenever an onprem user access cloud calendar, there’s a yellow diamond with red exclamation captioned “could not be updated”.
   Any thoughts?

   Reply

   1. Yes, it’s completely fine to re-run the Hybrid Configuration Wizard.

      There are different reasons why calendar sharing is breaking between on-premises and cloud. Here is an article that you can go through: Exchange Hybrid calendar sharing not working.

      Reply

8. If you have any proxy involved on your Exchange server, make an exception for *.windows.net to be able to run this.

   Reply

9. Hello,
   I have 2 Exchange 2016 servers installed on Windows 2012 R2.
   I want to install a new Exchange 2016 cluster on Windows 2016 and migrate mailboxes to it.
   I don’t have newer CALs and I want to get rid of Windows 2012R2.

   I have a hybrid setup but all mailboxes onsite (local)
   When installing new Exchange 2016 servers in my organization, do I have to install and configure Microsoft Office 365 Hybrid Configuration Wizard on each of them or is it was done once on one server for the entire organization?

   How can I verify the current configuration on installed servers (Windows 2012 R2)?
   I didn’t install it.

   Regards 🙂
   Daniel

   Reply

10. Hi,

    Our exchange 2019 is running on a windows core server. I installed the Hybrid configuration on another server to run the wizard.
    The wizard has run without error. But I cannot see the ‘Microsoft hybrid service’ as being installed.
    When I look at the ‘Hybrid’ page on the on-premise admin center. I cannot see the configuration.
    When I run ‘Get-hybridconfiguration’, I have results.

    Do you have any ideas?

    Tannks

    Reply

    1. The “Hybrid” page in on-premises Exchange admin center will stay empty, and you will not see any details there.

       Running the Get-HybridConfiguration cmdlet is the correct way.

       Reply

11. Hi Ali,
    I need to migrate an onpremise exchange to the cloud, but we want to use teams. Which type of migration should I use, classic or modern?
    Thank you very much for your tutorials

    Reply

    1. You should choose Exchange full Classic Hybrid deployment.

       Modern Hybrid support is limited to Free/Busy and will not provide calendar integration from Teams to mailboxes on-premises.

       Reply

12. Hi Ali,

    First of all, over time, I found valuable and useful info on your site.

    Straight to the point… We have an exchange classic hybrid organization, in on prem we have 8 exchange servers 2013 mbx&cas and 2 edge servers. We are planning to add 2 more servers mbx&cas to store journaling mailboxes. We do not intent to change the mailflow in any way The question is do we have to run again Hybrid config wizard ?

    Reply

    1. Hi Cristian

       I was reading your question and i am thinking like why you have the hybrid setup at this point. Do you have mailboxes in the exchange365 environment or is all on-prem ?

       The hybrid config wizard wants to know your primary on-prem server and some exchange configuration and routing. I guess the routing is now central configured on the on-prem server ?

       if that’s the case I don’t think you need to run the wizard again.

       If you change or upgrade your on-prem servers then it would be a good practice to run the EHW again.
       but hopefully Ali will ready your post and give you a straight answer.

       Reply

13. First of all, a very good article as always!
    i am running into the following error and can not find any on the internet about this issue. I hope you all have any suggestion …

    Its a hybrid wizard issue running for Exchange 2016 CU22
    Transport organisation config is needed for the teams calanders en contacts.

    Cheers

    2022.10.27 12:49:21.887 *ERROR* 11078 [Client=UX, Page=OCTChoice, fn=BuildOctConfig, Thread=11]
    System.AggregateException: Encountered errors while running organization configuration transfer. —> System.ArgumentOutOfRangeException: Could not find property ‘Action’ in object ‘Deserialized.Microsoft.Exchange.Data.Directory.Management.MalwareFilterPolicyPresentation’.

    Reply

    1. Exact same issue, never found the issue. Are you running forefront at all?

       Reply

14. Hello Ali,

    thank you for your courses, you re the best 🙂

    In this example, we will use Exchange Servers EX01-2016 and EX02-2016 for Hybrid Servers.
    My question is, where did you actually select or define EX01 and EX02 as Hybrid Servers ?
    By “Receive-Send Connector Configuration” section or not ?

    If we have 3 or 4 On-Oprem Exhange Servers with different versions, could we select as Hybrid Server only the newest versions of Exchange-Servers ? If yes where could we define this ?

    Thanks for your advices.

    Reply

    1. Hi Emre,

       That’s correct.

       So you will select the newest Exchange Server versions from the Receive/Send Connector configuration.

       After running the Hybrid Configuration Wizard, you can check its configuration:

       1. Run Exchange Management Shell as administrator
       2. Run the below command:

       Get-HybridConfiguration

       Note: If the Exchange Server is not yet licensed, you choose it in the first step. So it will download and install a free Exchange Hybrid license. Suppose your Exchange Server is already licensed; you select that Exchange Server (shown in this article).

       Reply

15. Hello Ali,

    How are you?

    Very good content. Taking advantage of the opportunity, you have already experienced the error HCW8099 – Command not recognized – Please verify you have the correct Management Rol assigned to your account?

    Get-OrganizationRelationship

    Reply

16. which port to authorize for HCW in dmz or very protected environnement pleasee

    Reply

17. Thank you so much, your courses is incredible.

    I tried to run HCW today, I need to use Classic Full on my client, but the installer doesn’t show the option screen for Classic or Modern, it’s the only screen that doesn’t appear.

    Reply

    1. I tried it on my end, and the Hybrid Topology option appears.

       Reply

       1. Checking the log I found:

          Hybrid Connector Availability: False, Reason: Previous Migration Endpoint found with standard on-premises configuration.

          I searched on local servers in Exchange Powershell with Get-MigrationEndpoint but didn’t find anything, I connected to 365 with Connect-ExchangeOnline and found the old Endpoint, I removed it (Remove-MigrationEndpoint -Identity identity-name) and now I’ve successfully finished the wizard 🙂

          Reply

18. hi there,

    is it neccessary to configure Exchange Hybrid option within the AzureAD Connect first
    or will it be just ok to run the wizzard as you mentioned here?

    thanx for an advise..

    kind regards

    juergen

    Reply

19. Is the modern hybrid still not supported for hybrid modern authentication?

    Reply

    1. Only Exchange Classic Hybrid Topology (Classic Full) supports Hybrid Modern Authentication.

       Reply

20. getting this same error for duplicate.
    there is nothing in enterprise apps in azure.
    we want to use the modern
    same external/internal url

    Reply

21. Hi Ali,

    Just wanted to start by thanking for all your document and so easy to follow! You save my butt a couple time. I was wondering if you could assist migrating from MX 2010 SP3 (has not had any release update installed on the original version for SP3) to Microsoft 365. Thank you in advanced!

    I am getting the errors below when running the wizard, the HCW8077 Tenant organization is dehydrated error resolved after running again:
    TargetServicePlan=’BPOS_S_E15_0′ TenantRelocationsAllowed=0 UMAvailableLanguages=[‘en-US’] UnblockUnsafeSenderPromptEnabled=1 VisibleMeetingUpdateProperties=’Location,AllProperties:15′ WebPushNotificationsDisabled=0 WebSuggestedRepliesDisabled=0 WhenChanged=’11/29/2021 3:29:11 PM’ WhenChangedUTC=’11/29/2021 10:29:11 PM’ WhenCreated=’6/11/2019 10:08:40 AM’ WhenCreatedUTC=’6/11/2019 5:08:40 PM’ WorkspaceTenantEnabled=1}
    2021.11.29 22:29:59.436 *ERROR* 10271 [Client=UX, Page=Configuring, fn=RunWorkflow, Workflow=Hybrid, Task=Initial, Phase=ValidateConfiguration, Thread=18] FINISH Time=269.0ms Results=FAILED – (Validation Failure)
    2021.11.29 22:29:59.438 *ERROR* 10273 [Client=UX, Page=Configuring, fn=RunWorkflow, Workflow=Hybrid, Task=Initial, Thread=18] FINISH Time=38.7s Results=FAILED
    2021.11.29 22:29:59.439 *ERROR* 10268 [Client=UX, Page=Configuring, fn=RunWorkflow, Workflow=Hybrid, Thread=18] FINISH Time=38.7s Results=FAILED
    2021.11.29 22:29:59.442 *ERROR* 10025 [Client=UX, Page=Configuring, fn=RunWorkflow, Thread=18] HCW8077 Tenant organization is dehydrated. Try running the Hybrid wizard again and if the issue persists contact support to remediate this issue.
    2021.11.29 22:29:59.444 *ERROR* 10025 [Client=UX, Page=Configuring, fn=RunWorkflow, Thread=18] HCW8001 Unable to determine the Tenant Routing Domain
    2021.11.29 22:29:59.445 *ERROR* 10025 [Client=UX, Page=Configuring, fn=RunWorkflow, Thread=18] HCW8092 One or more items failed validation during ‘Hybrid Initialization’ task. Please see log file for details.
    2021.11.29 22:29:59.446 10101 [Client=UX, Provider=Tenant, Thread=18] Disposing Runspace.
    2021.11.29 22:29:59.513 10101 [Client=UX, Provider=OnPremises, Thread=18] Disposing Runspace.
    2021.11.29 22:36:52.191 10044 [Client=UX, Thread=1] Opening https://support.microsoft.com/kb/3068010
    2021.11.29 22:37:13.096 10044 [Client=UX, Thread=1] Opening C:\Users\itsupport\AppData\Roaming\Microsoft\Exchange Hybrid Configuration\20211129_222254.log

    Reply

22. Errors occur when configuring User Exchange Modern Hybrid Topology in an Exchange 2013 and Exchange 2019 coexistence environment.

    Is it because of Exchange 2013?

    2021.10.27 14:43:46.586 *ERROR* 10277 [Client=UX, Session=Tenant, Cmdlet=Remove-MigrationEndpoint, Thread=19]
    FINISH Time=948.6ms Results=PowerShell failed to invoke ‘Remove-MigrationEndpoint’: 끝점 ‘Hybrid Migration Endpoint – EWS (Default Web Site)’이(가) 한 개 이상의 일괄 처리와 연결되어 있기 때문에 제거할 수 없습니다. ex2013. {CategoryInfo={Activity=[System.String] Remove-MigrationEndpoint,Category=[System.Management.Automation.ErrorCategory] 1000,Reason=[System.String] CannotRemoveEndpointWithAssociatedBatchesException,TargetName=[System.String] ,TargetType=[System.String] },ErrorDetails=,Exception=[System.Management.Automation.RemoteException] End Point ‘Hybrid Migration Endpoint – EWS (Default Web Site)’ It can’t be removed because it’s connected to one or more batches.. ex2013.,FullyQualifiedErrorId=[System.String] [Server=YT3PR01MB5332,RequestId=4d22e1bd-4171-4998-b7d0-a98bc7f18e47,TimeStamp=2021-10-27 오후 2:43:46] [FailureCategory=Cmdlet-CannotRemoveEndpointWithAssociatedBatchesException] A7D26DFF,Microsoft.Exchange.Management.Migration.MigrationService.Endpoint
    .RemoveMigrationEndpoint}
    2021.10.27 14:43:46.587 *ERROR* 10232 [Client=UX, Page=Configuring, fn=RunWorkflow, Workflow=Hybrid, Task=MRSProxy, Phase=Configure, Thread=19]
    Microsoft.Online.CSE.Hybrid.PowerShell.PowerShellInvokeException: PowerShell failed to invoke ‘Remove-MigrationEndpoint’: 끝점 ‘Hybrid Migration Endpoint – EWS (Default Web Site)’이(가) 한 개 이상의 일괄 처리와 연결되어 있기 때문에 제거할 수 없습니다. ex2013. {CategoryInfo={Activity=[System.String] Remove-MigrationEndpoint,Category=[System.Management.Automation.ErrorCategory] 1000,Reason=[System.String] CannotRemoveEndpointWithAssociatedBatchesException,TargetName=[System.String] ,TargetType=[System.String] },ErrorDetails=,Exception=[System.Management.Automation.RemoteException] 끝점 ‘Hybrid Migration Endpoint – EWS (Default Web Site)’이(가) 한 개 이상의 일괄 처리와 연결되어 있기 때문에 제거할 수 없습니다. ex2013.,FullyQualifiedErrorId=[System.String] [Server=YT3PR01MB5332,RequestId=4d22e1bd-4171-4998-b7d0-a98bc7f18e47,TimeStamp=2021-10-27 오후 2:43:46] [FailureCategory=Cmdlet-CannotRemoveEndpointWithAssociatedBatchesException] A7
    D26DFF,Microsoft.Exchange.Management.Migration.MigrationService.Endpoint.RemoveMigrationEndpoint} —> System.Management.Automation.RemoteException: 끝점 ‘Hybrid Migration Endpoint – EWS (Default Web Site)’이(가) 한 개 이상의 일괄 처리와 연결되어 있기 때문에 제거할 수 없습니다. ex2013.
    — 내부 예외 스택 추적의 끝 —
    위치: Microsoft.Online.CSE.Hybrid.PowerShell.PowerShellInvokeResult.CreateOrThrowMapped(String cmdlet, IReadOnlyDictionary`2 parameters, DateTimeOffset start, IPowerShellDataStreams dataStreams, ILogger logger, IPowerShellObject[] objects)
    위치: Microsoft.Online.CSE.Hybrid.Provider.PowerShell.PowerShellProvider.PowerShellInstance.Invoke(String cmdlet, IReadOnlyDictionary`2 parameters, Int32 millisecondsTimeout)
    위치: Microsoft.Online.CSE.Hybrid.PowerShell.RemotePowershellSession.Invoke(IPowerShell powershell, String cmdlet, IReadOnlyDictionary`2 parameters, Int32 millisecondsTimeout)
    위치: Microsoft.Online.CSE.Hybrid.PowerShell.RemotePowershellSession.RunCommandInternal2(String cmdlet, SessionParameters parameters, Int32 millisecondsTimeout, Boolean skipCmdletLogging)
    위치: Microsoft.Online.CSE.Hybrid.PowerShell.RemotePowershellSession.RunCommandInternal(String cmdlet, SessionParameters parameters, Int32 millisecondsTimeout, PowerShellRetrySettings retrySettings, Boolean skipCmdletLogging)
    위치: Microsoft.Online.CSE.Hybrid.Session.PowerShellTenantSession.RemoveMigrationEndpoint(IIdentity identity)
    위치: Microsoft.Online.CSE.Hybrid.StandardWorkflow.MRSProxyTask.Configure()
    위치: Microsoft.Online.CSE.Hybrid.Engine.Engine.c.b__12_2(ITaskContext c, ITask t)
    위치: Microsoft.Online.CSE.Hybrid.Engine.Engine.ExecutePhase(ILogger logger, TaskPhase phase, IWorkflow workflow, ITask task, Func`3 phaseFunction, LogEntryType typeForFalse)

    Reply

    1. Remove all migration batches and rerun the Hybrid Configuration Wizard (HCW).

       Reply

       1. Hi, I’m trying to setup 2 Exchange hybrid into single M365 tenant. And I have the same error like JKYU.
          1st Exchange is already setup and working, but on the 2nd hybrid wizard end with this same error.
          What happend if i delete migration batches and run wizard again, it will delete the 1st endpoint?
          I want to keep both endpoints.
          Thank you.

          Error
          START Remove-MigrationEndpoint -Identity ‘Hybrid Migration Endpoint – EWS (Default Web Site)’ -Confirm: $false
          2022.12.01 13:07:08.169 10177 [Client=UX, Provider=Tenant, Thread=20] PowerShell Error Record: {CategoryInfo={Activity=[System.String] Remove-MigrationEndpoint,Category=[System.Management.Automation.ErrorCategory] 1000,Reason=[System.String] CannotRemoveEndpointWithAssociatedBatchesException,TargetName=[System.String] ,TargetType=[System.String] },ErrorDetails=,Exception=[System.Management.Automation.RemoteException] The endpoint ‘Hybrid Migration Endpoint – EWS (Default Web Site)’ cannot be removed because it is associated with one or more batches

          Reply

23. Thanks so much Ali, you’ve solved a great puzzle for me!!!
    Beautiful blog, congratulations.

    Reply

24. When I run the HCW it fails on Register Hybrid Agent. In the log it is telling me this:

    {“applicationServerTimeout”:”Default”,”applicationType”:”microsoftapp”,”externalAuthenticationType”:”passthru”,”externalUrl”:”https://941fe306-841e-46e6-ae92-c19d824dd36e.resource.mailboxmigration.his.msappproxy.net:443/”,”internalUrl”:”https://mail.domain.com:443/”,”isOnPremPublishingEnabled”:true,”isTranslateHostHeaderEnabled”:false,”isTranslateLinksInBodyEnabled”:false,”singleSignOnSettings”:null,”verifiedCustomDomainCertificatesMetadata”:null,”verifiedCustomDomainKeyCredential”:null,”verifiedCustomDomainPasswordCredential”:null}}
    2021.08.18 13:17:44.082 10333 [Client=UX, fn=SendAsync, Thread=12] FINISH Time=543.0ms Results=BadRequest {“error”:{“code”:”InternalUrl_Duplicate”,”message”:”Internal url ‘https://mail.domain.com/’ is invalid since it is already in use”,”innerError”:{“date”:”2021-08-18T13:17:44″,”request-id”:”de4f1e8a-f045-4b31-b943-82fd1501805d”,”client-request-id”:”de4f1e8a-f045-4b31-b943-82fd1501805d”}}}
    2021.08.18 13:17:44.084 10407 [Client=UX, Thread=12] Updating Local Client Configuration File
    2021.08.18 13:17:44.107 10341 [Client=UX, Page=HybridConnectorInstall, Step=ConfigOrgRoute, Thread=12] FINISH Time=581.1ms Results=Failed

    What does this mean I have a duplicate URL. Yes my internal and external URL are the same. They are can be. You instructions for setup even show that. Can you tell me what else to look for?

    Reply

    1. You get the Hybrid Agent registration error because you already have another Enterprise App published with the same URL.

       The best way is to rerun the Hybrid Configuration Wizard and select “Use Exchange Classic Hybrid Topology” instead of the “Use Exchange Modern Hybrid Topology”. This way, you will not get this error.

       Reply

       1. We are also getting that error. Do you know of a way to check what Enterprise App is published with that same URL? Thanks for your help.

          Reply

          1. Is there way to figure out which Enterprise App is published with the same URL?

             Reply