Opening another user's calendar or folder" My personal experience is keeping desktop users configured from non-cached mode.This will allow those users to primarily view the updates in "real-time"..." id="ctl00_m_m_i_ctl00_gr_ctl03_bestanswerbody" class="textarea-bestanswerhidden" name="bestanswerbody" answerbody Id="2661707" / If this is an exec admin, I would suggest keeping their outlook client configured for non-cached mode.Cached Exchange Mode works like this: When the Exchange Server notifies Outlook of a change, the Download timer starts and Outlook delays receiving the change information.All notifications that occur in the 30 second window of the Download timer are grouped and processed as a batch at the end of the timer, then the timer is reset.The theory here is that as we deal with larger and larger mailboxes, it does not make much sense to keep everything cached because users really only need access to their most recent data.

This behavior can be changed using a simple registry change, or, as I recommend, using Group Policy.

Verify what version of Outlook the user is using and whether or not they are updated with the latest outlook client patches.

My personal experience is keeping desktop users configured from non-cached mode.

In a nutshell, I made the user a full control access member of the mailbox, and also a editor delegate for the calendar Only a few people are allowed to schedule the resource. Washington III mode does not download another user's data to the OST file" and Manager would observe inconsistent calendar details, if any of them is in Cached mode" "Practices to Avoid ...

Opening another user's calendar or folder"" id="ctl00_m_m_i_ctl00_gr_ctl01_bestanswerbody" class="textarea-bestanswerhidden" name="bestanswerbody" answerbody Id="2661427" / mode does not download another user's data to the OST file" and Manager would observe inconsistent calendar details, if any of them is in Cached mode" "Practices to Avoid ...