The index updating for caching mode is normally nicely hiding in the background, and under normal situation works just fine. It is better than in the past where it would only index a portion of messages on each restart of the client, but currently it the client needs to be left running for at least overnight to process fully if there's been a lot of messages such as for a new cache.
So there are times where we need that index updated or rebuilt ASAP (fully update all NOW, please use all CPU and tell me when you are done)
- a new cache for an existing heavy user such as the CEO so that the index is complete Before we give them their new notebook.
- a rebuilt of a corrupt index.
- a periodically used account that gets lots of status messages, such as a part time support admin trying to deal with all those different GWCheck messages with the same subject line.
- somebody just back from maternity/paternity or other extended leave

by: Andy K. | over a year ago | Windows Client