And why should they, old email is unlikely to be referenced frequently. I am not convinced even the most modern of mail applications really can handle the volume of email some people tend to store. I have broached enterprise archiving (and client backups for that matter) in the past to no avail.
#OUTLOOK FOR MAC WON'T SEARCH ARCHIVE#
Personally I clean out any email older than a year to an archive with mail steward. Thus there are many users (Windows and Mac) that have very extensive collections of local mail. In regards to the storage use, we do not give end users a lot of primary mailbox space and have no plans to enable exchange online archiving. I have some other mdimport things I am going to try before going nuclear and rebuilding the whole user profile. I didn't mention it in my initial post but I had followed KB 2741535 when I went out to investigate (this was originally reported by desktop, I don't generally interact with end users). Short story TLDR: Apologies i don't have a concrete answer, but it seems correlated to the size of the local "DB." With apple of course saying "It's MS's fault." I have an open case with Microsoft about it and they are just as puzzled as to what could "corrupt" searching even after a rebuild and reinstall. NOTE: In this case it was a developer who was tinkering with system permissions and we killed it with fire.Ī few times when the local mailbox structure was what we consider insane (20gb+) we had to rebuild the OS X user profile. (i don't believe the app uninstall does anything other than buy time for the new index) It usually works, but one user still had a search problem. The helpdesk has tried uninstalling office - deleting the local database folders - resetting spotlight indexing - then reapplying office. Clearing the spotlight cache and re-indexing has worked with a low success rate.
/StuckinOutbox-5bd9b2e446e0fb00514d5d12.jpg "outlook for mac won")
If the user's DB gets over say 5-10gb we start to see these anomalies. Your keywords to me were extensive local storage - that is when we run into this issue also.
0 kommentar(er)
