In my previous post Troubleshooting Autodiscover I wrote about Autodiscover service and the difference between POX and SOAP requests. Over the last years Microsoft evolved Autodiscover and introduced a new Autodiscover service V2. The new version is based on JSON and the main difference is the fact you don’t need to be authenticated.
I spent last weeks quite some time with Outlook performance issues in an Exchange Hybrid scenario. In addition this is not a normal Hybrid as here multiple Exchange Organizations from different AD Forests without any Trust Relationships are involved.
Thus I’m not talking about the scenario described in TechNet Multi-forest hybrid deployment scenario. It looks more like this:
This post was lingering around for a long time, but the last weeks showed me it’s time.
Actually I came across this topic last year just before Ignite. But somehow this topic felt into oblivion. To make it short:
It’s all about the number of TCP connections an Outlook Client establishes in a Cached Mode. Especially when it comes to shared mailbox or delegate scenarios.
What is Outlook Cached Mode?
Read more about it here. But what you really want to avoid it something like this:
A long time ago Jim Martin wrote an excellent article how Exchange maps folder IDs for ActiveSync:
Lately I had to troubleshoot Exchange ActiveSync devices and had also the need of mapping IDs to folder as the IIS logs contain only the folder IDs. Glen’s script was doing a good job, but wasn’t too user-friendly. Therefore I improved the usability and extended the ability of gathering data.
In my Ignite session with fellow MVP Andrew Higginbotham Troubleshooting Complex Exchange operational issues, I mentioned Fiddler as a perfect tool for troubleshooting also Exchange ActiveSync clients as well as Exchange servers itself.
After this session a lot of people reached out to me and asked me about how to do this. So I thought a write-up would be a good idea.
Recently we saw an increasing number of tickets where user complained about issues retrieving Free/Busy data while scheduling a meeting or for shared calendar.
When trying to schedule a meeting you would see only hash marks
Currently I see an increasing number of reports about missing body of meeting series. As most of the series are Skype for Business and contain the dial-in information, this is really a bad end-user experience. Imagine you want to join the meeting and have no dial-in information or the attachments are gone.
My first thoughts were that this is a Skype for Business only issue or related to Exchange ActiveSync. But this time it turned out it’s not. After analyzing of several cases, it came down to an Outlook for Windows only issue in a delegate scenario.
The issue was resolved in Version 1706 (Build 8229.2103), which is the July version of the Current Channel. Please be aware about the changes to Office 365 ProPlus update management! You can read more about the changes here. Either way, when you are on Deferred or Semi-Annual Channel you have to wait for this fix.