LSeven
asked on
Exchange 2013 Search Result Limit
We recently migrated a client with a large terminal server cluster from Exchange 2007 to Exchange 2013. Immediately users began to report issues with their search results returning only a very small amount of items. We have yet to be able to find a resolution to this through standard operations of rebuilding the indexes.
What I did find online was an article talking about a 250 item result limit that is some how hard coded into Exchange 2013 when your Outlook is in online mode. Is this true? Is there a work around or fix?
What I did find online was an article talking about a 250 item result limit that is some how hard coded into Exchange 2013 when your Outlook is in online mode. Is this true? Is there a work around or fix?
ASKER
Amit,
Thanks for the quick response, but unfortunately that setting does not effect search results in Online mode. It only effects search results in Cached mode. We have messed with it and we are still limited to 250 search results on search terms that should return 1000s.
Thanks for the quick response, but unfortunately that setting does not effect search results in Online mode. It only effects search results in Cached mode. We have messed with it and we are still limited to 250 search results on search terms that should return 1000s.
So better to keep outlook in cache mode, why do you need outlook in online mode. Even I am working with an org and we prefer to use outlook in cache mode for thousands of users.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Amit/Will,
Do you have any ideas on how to best run cached mode in Exchange for a RD server farm? My only thought is a mapped drive and a GPO to force a cached location, but I believe it is against best practice to store an OST over the network.
Thoughts?
Do you have any ideas on how to best run cached mode in Exchange for a RD server farm? My only thought is a mapped drive and a GPO to force a cached location, but I believe it is against best practice to store an OST over the network.
Thoughts?
Yes you do NOT want to store the OST on the network. This will also create slowness and also possible OST Corruption. In Outlook 2013 a new feature that they have encorporated is caching a percentage of your mailbox to the machine. So this might be an option to configure Outlook 2013 with a 20 or 30 percent cached mailbox. You can play with the setting to see what works best for your users.
Another though is you could add additional storage to each RD server specifically for caching the OST files. This way it is stored locally but not on the c drive.
Will.
Another though is you could add additional storage to each RD server specifically for caching the OST files. This way it is stored locally but not on the c drive.
Will.
Please go through with this article and apply fix in your env. may help you.
Content from article: