Forum Discussion
Solved
Exchange 2016 EAC redirects to OWA
Hi All Hope everyone is keeping safe. Please can someone assist me with the following issue. For some reason I can no longer access the EAC on my Exchange 2016 server. I have tried different brow...
- Hello Navishkar,
These are from the EWS but could you check them for the OWA and ECP directories?
And do they match with IIS?
Also, could you recycle the IIS sites?
Hello Navishkar,
On which server is the mailbox of the admin account homed?
If it's placed on the Exchange 2010 server then it could be possible that Autodiscover or the back end virtual directory is not functioning properly.
On which server is the mailbox of the admin account homed?
If it's placed on the Exchange 2010 server then it could be possible that Autodiscover or the back end virtual directory is not functioning properly.
"It's also strange that onboarding didn't work properly, I would advice you to use the Office 365 ECP (outlook.office365.com/ecp) to create migration batches as the ECP within Exchange doesn't work properly sometimes (experienced this myself as well)." --- About this.....so what happened was that Exchange online wasn't able to connect to the migration endpoint. The only time it was able to connect was when I change the authentication options on those virtual directories.
- Hello Navishkar,
Aaah I have been dealing with this a lot lately, this is because for some reason the EWS directory isn't accessible through basic auth.
You can resolve this with the following PowerShell commands:
get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -MRSproxyenabled $false
get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -basicauthentication $true
get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -MRSproxyenabled $true
EWS is used by Office 365 to process mailbox onboarding.BemmelenPatrick Thanks for that info but I never had to change anything on the EWS virtual directory. Only after I made changes to the OWA directory was Office 365 able to connect to the migration endpoint.
- Hello Navishkar,
That's strange that this was the solution but if it works it works 😉
Did you already change the virtual directory permissions to the article I've added in my previous message?