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(288, 91%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EOR%3C/text%3E%3C/svg%3E)
Hello,
we have a problem with Outlook 2013 (RDS Session, Online Mode) Calendar Search and Exchange 2019 (CU6-CU8 tested).
Note: Outlook 2013 is currently still necessary due to compatibility with existing applications. Therefore, an OL 2016 or higher cannot be used at this time.
The search in the calendar works very strangely. When entering search terms (directly in the calendar on the right side of the corner), entries are only displayed to a small extent - many entries are missing.
If I go through the "advanced search" then all entries will be displayed. See picture (only in german, but show the issue).
It affects all users (20) - no exceptions.
For me, this would be primarily a question of indexation. That's why we reindexed all mailboxes in Exchange 2019, with no visible success.
Now my question would be, what else is wrong here? Is the effect known if necessary?
Thank you for your tips.
![](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)
Thanks for the detailed information!
I tested in my lab (Exchange 2019 CU8 and Outlook 2013) but was not able to reproduce the issue.
Sorry I need to ask several questions to get some more information:
Supplement:
When searching via the OWA in the calendar, all entries (at least at first glance) are found correctly. So it must be a "thing" between Exchange 2019 and Outlook 2013!
]1
Thanks @Kael Yao ,
We first tested it in the Combination Outlook 2013 and Exchange 2019 CU6 - it didn't work out.
After that, we installed CU8 -> the same problem.
The direct search in the Outlook calendar yields only 2-3 results, while the advanced search in Outlook finds "all" results. The search in the OWA also yields all results (at least according to our test).
-> see pic. below.
Yes we also moved the MBX to a new database -> the same problem. After that we moved is back to the original MBX.
So it doesn't seem to be a problem with the search index in Exchange, but rather that Outlook 2013 has a problem with Exchange 2019 in direct calendar search (to in the advanced search!).
Hint: The result of Outlook advanced search looks like the same as in OWA search. So I think the search index in the Exchange shouldn't be the problem.
Hi,
Thanks for the update!
If possible, would you please also test it on a normal windows 10 client? (instead of on the RDS server)
Hi,
Unfortunately, there is no local Office 2013 installation on Windows 10. This is related to the necessary ERP application on the RDS.
However, we may be able to pair the Windows 10 calendar with the Exchange and search there. If that would clarify anything?
If that would clarify anything?
If on another device it works fine, I suppose that the problem may be with the RDS server.
Here is a link in the similar situation for your reference: RDS and Outlook Search
In this case, Advanced Search works fine while Instant Search (the search bar) doesn't work as well.
Hi,
thanks for the link. But the post doesn't help much. Things with Windows Search are taken into account. Reindexing does not change.
It is proven that the Outlook Calendar Search (Instant Search) shows hardly any results, but the Outlook Email Search (Instant Search) works correctly. The Exchange index also cannot be erroneous, then the OWA search would not provide perfect results. I think it's some issue Outlook 2013 with Exchange 2019 in calendar search.
Hi,
The Exchange index also cannot be erroneous, then the OWA search would not provide perfect results.
Yes. I agree with that the server index may not be the cause of the issue.
While, it is hard to tell whether the issue is caused by the RDS server.
Besides, if you are using some add-ins in Outlook, please also try running Outlook in safe mode to see if it makes any difference.
Open Outlook in safe mode
Hi,
the safe mode was a good idea. But unfortunately, it doesn't change anything in behavior.
Sorry!
BR Oliver
Hi Oliver.
Do you have some GPOs settings with Windows Search in your organization?
Hi,
not that I know. No special settings or even GPOs created for Windows Search settings.
What would be special to look out for here? Would there be a GPO setting that would have such a systemic effect on instant search in the Outlook calendar?
Hi,
My apologizes for the late reply.
According to these links:
Description of Windows Search 4.0 and the Multilingual User Interface Pack for Windows Search 4.0
Windows Desktop Search and the implications on WAN performance
There seems to be a behavior that windows search would still try to index the items even if Outlook is in online mode.
I am not sure if it may be the cause.
Hi,
thanks for your feedback.
"Reduced effect on Microsoft Exchange when you index e-mail in online mode" is an extremely vague formulation.
It's more like old systems like Office 2007, not Outlook 2013. Is this comparable?
And was it necessary to do now? Uninstalling Windows Search only brings other problems and no search at all.
Thank for your help.
Hi,
Sorry I wasn't able to find more detailed documents on this topic.
And was it necessary to do now? Uninstalling Windows Search only brings other problems and no search at all.
While, I think the best practice to narrow down the issue would still be using another client device to test.
Meanwhile it won't cause additional troubles to the current environment.
Hi,
this is not simple client device, but an RDS server with some users on it, they all have the same problem.
If I just install the Outlook 2013 on a Windows 10 client now and it works there, I still can't draw any conclusions about the RDS server.
Hi,
In my former reply I meant that the cause may be on the RDS server.
And I suggested testing with a normal windows client instead.
Sorry I didn't make it clear.
If I just install the Outlook 2013 on a Windows 10 client now and it works there, I still can't draw any conclusions about the RDS server.
Did you mean a normal windows 10 client works fine while using the instant search?
If so, I suppose that the cause should actually be on the RDS server.
While, it may be really hard to locate the root cause.
Hello Oliver,
I've been facing this before.. back then, we found out, that the indexer did not include the path to the .ost file.
If you have already checked and corrected that, here's a blog article about FAST and WDS, maybe this give's you some hints:
https://techcommunity.microsoft.com/t5/outlook-global-customer-service/how-outlook-2016-utilizes-exchange-server-2016-fast-search/ba-p/381195
I hope this helps...
KR, Alex
Thanks @AlexC
Thanks for the tips. However, Outlook 2013 is operated in Online Mode (RDS Session). There is no OST file. In addition, Exchange 2019 would have a very different "BigFunnel" search. So the procedure does not fit.