Hi all, i am asking a question because we have this issue on multiple servers so far:

Customers with their own local terminal servers (15 users, RDP to a server session) that have office 365 mailboxes are having issues with the windows search EDB file where it becomes HUGE (80+gbs).

Reason for this is because all these users have large ost files in which they share the same shared mailboxes (site specific for example) and there goes something wrong with the windows search index database file.

Temporarly we solve this by deleting and rebuilding the search index but in mere weeks the database edb file itself is back consuming a lot of space.

We CAN NOT AFFORD to work in ONLINE mode of outlook: the whole experience for end user is horrible. the outlook clients just react real slow because you're constantly working in mailboxes of sizes larger than 20gbs combined. So we managed to cache it for one month, this is plenty for our customer. With result that the OST files are easily using up this space locally per month.

is there any permanent fix to tihs, how can we make our outlook mailboxes work fine on this terminal server without caching? the experience is horrible if we don't cache.

edit: we tried a lot of stuff, archiving, hardware accelerations, ...

• Edited by AJ_BE Wednesday, May 20, 2015 2:43 PM

Hello,

Is the size of OST restricted now by caching it only for one month or still its a challenge.?

Regards

Sanjay

hi,

the ost files are stable, they don't grow much larger because we cached them to one month. the main problem is the windows search edb file going berserk thanks to those files. We can not afford to use Mailbox search online (too slow) so we do caching.

Hi,

Im expreciensing the same issue.
the EDB file grows to 40-50 GB and takes up all the disk space.
I've rebuild the index everytime this happens. Trying to make a script now that rebuilds it if the disk is full.