This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Dear Friends,
We are having some issues with our hybrid Exchange environment (Online Exchange, On Prem Exchange 2016 and exchange 2010.)
I was planning to migrate some old mailboxes from Server 2016 to the cloud. It failed with "GUID.resource.mailboxmigration.his.msappproxy.net' could not be completed. Everything else, mail flow, SMTP is working fine.
I checked several things on the on prem servers, seems to be all fine. EWS is all on, and Migration Endpoint is still there. MRS proxy servers configured for both on Prem exchange servers.."
The only thing is that Exchange server 2010 was powered off last year (It used to be main mail server before setting up hybrid). We renewed SSL beginning of this year. The old server 2010 has been renewed with the latest SSL wildcard certificate. I noticed on EWS for Exchange 2010 server, MRS proxy enabled with basic authentication ticked.
Would "Expired SSL on old exchange server" be the reason why Migration failed? Is there any way we can troubleshoot this issue?
I tried disabled and enabled MRS Proxy on old server, restarted IIS, still no luck..
Help please.
Thanks
ML
Try to rerun HCW on Exchange 2016, check whether there exist issues with it.
If you could run HCW successfully, then go to Exchange online admin center. Try creating a new migration end point and check whether could migration successfully now. Make sure the migration point is point to Exchange 2016 and resolved successfully.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Thanks for that.
Did you mean I can re-run Hybrid Configuration wizard, it would't damage mail flow or sync services, right? Sorry I have never used HCW myself. Someone else before set it up.
Thanks,
ML
The rerun HCW will not damage your hybrid. If there already exists an issue with hybrid in your organization, the rerun action will fail and tell you which thing is wrong.
I will give a run. you wouldnt think it is the issue with SSL certificate expired on our Old exchange server 2010 got powered off for 1 year?
Thanks
ML
Hi Kyle,
Actually I just re-run the migration batch and then found out:
Error: MrsHttpUnauthorizedException: The Mailbox Replication Service was unable to connect to the remote server using the credentials provided. Please check the credentials and try again. The call to 'https://guid.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' failed. Error details: The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'NTLM,Negotiate'. --> The remote server returned an error: (401) Unauthorized.. --> The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'NTLM,Negotiate'. --> The remote server returned an error: (401) Unauthorized. --> The call to 'https://guid.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' failed. Error details: The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'NTLM,Negotiate'. --> The remote server returned an error: (401) Unauthorized.. --> The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'NTLM,Negotiate'. --> The remote server returned an error: (401) Unauthorized.
Does it mean the user configured in Migration Endpoint is incorrect, changed or expired something?
Thanks
Nameless
Yes, this issue is related to the credentials that you used for migration endpoint.
Use the Exchange on-premises admin account credentials for migration endpoint. About migration question, this blog also could help us narrow down: Troubleshooting Hybrid Migration Endpoints in Classic and Modern Hybrid
After creating a new migration endpoint, please delete old migration request, then create a new one to migrate mailbox.
Any update about this thread? Could you migrate mailbox successfully now?
I would like to comment, to end this cliffhanger; that I was in exactly this situation after replacing the Exchange certificates succesfully. I rand HCW succesfully. Than failed migrations with the above error. I tried IISresets. I tried HCW reruns. What finally got it working for me, was, creating a NEW migration point during the creation of the migration batch. Just fill in the fields, I didn't put in a direct URL, left it over to autodiscover. Worked like a charm. I think it's a combination of new certificates, old credentials etc. I looked at IIS to try to change the authentication settings on the Default Website, but couldn't figure out on which subsite. Since the rest of my environment was running like a charm, I didn't touch it.
Please check similar thread - https://community.spiceworks.com/topic/2314526-mrsproxy-problem-with-exchange-2010-to-office365-migration
If you run the command Get-WebServicesVirtualDirectory | select auth you’ll find that (most likely) Basic Authentication is set to $FALSE. To set this to $TRUE and thus enable Basic Authentication you can use the following command:
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory –BasicAuthentication $TRUE