Ben S
asked on
Office 365 Migration free/busy detail
Hi,
I'm currently in the middle of an Office 365 migration from exchange 2010.
I have started to test my first batch of migrated users, but have found when a Cloud users tries to see the free/busy details of an on-prem user the information is not available the Outlook error is 'The recipient's mailbox server could not be contacted'
I have checked the IIS logs and can't see any POST logs,
I have used the PowerShell to set the TargetSharingEpr to the URL that bypasses the load balancer (https://webmail.sbs.co.uk/EWS/exchange.asmx)
I have test Autodiscover on https://testconnectivity.microsoft.com
the final error is
Checking for account settings after domain redirection
We were unable to get account settings after a domain redirection.
Additional Details
The Microsoft Connectivity Analyzer doesn't support multiple domain redirections. Please check that your redirections aren't looping.
Elapsed Time: 0 ms.
Does anyone have any suggestions?
I'm currently in the middle of an Office 365 migration from exchange 2010.
I have started to test my first batch of migrated users, but have found when a Cloud users tries to see the free/busy details of an on-prem user the information is not available the Outlook error is 'The recipient's mailbox server could not be contacted'
I have checked the IIS logs and can't see any POST logs,
I have used the PowerShell to set the TargetSharingEpr to the URL that bypasses the load balancer (https://webmail.sbs.co.uk/EWS/exchange.asmx)
I have test Autodiscover on https://testconnectivity.microsoft.com
the final error is
Checking for account settings after domain redirection
We were unable to get account settings after a domain redirection.
Additional Details
The Microsoft Connectivity Analyzer doesn't support multiple domain redirections. Please check that your redirections aren't looping.
Elapsed Time: 0 ms.
Does anyone have any suggestions?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Amit Kumar
I agree with Michelangelo
ASKER
Hi,
It's currently to o365,
should I update the cname or can I use PowerShell?
Thanks,
It's currently to o365,
should I update the cname or can I use PowerShell?
Thanks,
If it is in hybrid mode and still users are homed on Exchange On-Prem then you must configure Autodiscover URLs to exchange On-prem with best practices. This will be done by changing DNS records pointing in your DNS registrar.