Running Exchange Hybrid Configuration Wizard, unable to create endpoint

Joe Grover 156 Reputation points
2021-01-14T03:39:48.34+00:00

I'm running Exchange 2016 CU16 and am trying to set up a Hybrid environment with Microsoft Exchange Online in order to start a migration to 365 services.

When running the Hybrid Configuration Wizard, I get the error HCW8078 - Migration Endpoint could not be created

56414-error-01.jpg

I've also run Test-MigrationServerAvailability and the output indicates that no MRSProxy was found running at the host indicated (this host being our autodiscover URL).

56434-error-03.jpg

If manually go to the MRS Proxy URL (either internally or externally) I'm prompted for authentication. After putting in an admin login credential, I get the following page:

56389-error-02.jpg

However, I have confirmed both via the EAC and via PowerShell (via Test-MRSHealth and Get-WebServicesVirtualDirectory) that the MRSProxy is enabled and responding to a ping.

56379-error-04.jpg

56428-error-05.jpg

I've done the following to try to resolve this:

  • I've simply issued an IISRESET command and tried again: still fails
  • I set the MRSPRoxy configuration on the EWS site to $false, issued IISRESET, then set it back to $true, and issued another IISRESET: still fails
  • I've recycled the MSExchangeServicesAppPool in IIS: still fails

I'm not sure what else to try? The Microsoft Connectivity Analyzer indicates everything on my server looks good, the only warning being that I have a GoDaddy cert that requires clients to be running their Windows Updates in order to trust the root cert provider. Does the account provided for this require certain privileges? I'm using the general domain admin account I use for all of my Exchange management.

Exchange | Hybrid management
0 comments No comments
{count} votes

Accepted answer
  1. Joe Grover 156 Reputation points
    2021-01-14T15:00:51.233+00:00

    This turned out to be as simple as adding Basic Authentication to the EWS Default Website and then recycling the MSExchangeServicesAppPool in IIS. I believe Basic Authentication was removed during a call with MS Support a few years ago.

    After doing these two steps I ran the Test-MigrationServerAvailability command again and it completed successfully.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.