This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 77%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDH%3C/text%3E%3C/svg%3E)
Hi,
actually we are in a migration from Exchange 2010 to 2016.
We have the proble that i can't see the free busy times.
Start Outlook with /cleanfreebusy don't solve the Problem.
What can this cause?
Regards
Dennis
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Do suggestions help? If you have any questions or needed further help on this issue, please feel free to post back.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 98%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETA%3C/text%3E%3C/svg%3E)
Not the faintest idea! Sorry.
In your case, It may possibly be the known issue according to this kb: No Free/Busy information after a mailbox moves from Exchange 2010 to Exchange 2013 or Exchange 2016
The cause is Exchange 2016 continues to proxy the EWS request to Exchange 2010 after the mailbox was moved.
Please run the following commands to restart the Autodiscover Application Pool and the Exchange Web Services Application Pool on the Exchange 2016 Server.
Restart-WebAppPool MSExchangeAutodiscoverAppPool
Restart-WebAppPool MSExchangeServicesAppPool
If the problem persists, please test with Owa or Online mode to see if the free/busy information shows correctly.
Hi,
thanks for your answer.
Problem is solved. The EWS URL was not reachable.
Thanks
Dennis
Thanks for reply, please be free to mark your reply as answer to highlight it,this will make answer searching in the forum easier and be beneficial to other community members as well.