Home All Groups Group Topic Archive Search About

30 seconds to receive message

Author
13 Apr 2005 10:11 AM
Maki
Running a single exchange 2003 server. Some staff members need 30 seconds to
receive a message once sent. Is this a standard time for the exchange server
or should everybody within the same network get the message instantly?

Author
15 Apr 2005 6:45 PM
Tim
If you want it to go faster, don't use cached exchange mode in outlook.
Otherwise it appears to be working normal.

Outlook 2003 Cached Exchange Mode synchronization timing

To provide a good balance between usability and network efficiency, the
timing of synchronization communications between Outlook 2003 and Exchange
Server 2003 has been optimized by using synchronization timers.

Warning   If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.

You can change these synchronization timer values by creating and modifying
the following registry keys and values under the
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Outlook\Cached Mode
registry key:

- "Upload=dword:0000000f" (default is 15 seconds).

- "Download=dword:0000001e" (default is 30 seconds)

- "Maximum=dword:0000003c "(default is 60 seconds)

By default, whenever the client is in Cached Exchange Mode, and a user
makes a local change, the "Upload"  timer starts. Changes have the following
effects:

- If a local change occurs in the "Upload" 15-second window, the timer
restarts.

- If no other local changes occur before the "Upload" 15 -second window 
expires, the data is synchronized to the server.

- If changes continue to occur before the timer expires and at least one
minute elapses, the changes are synchronized to the server without additional
delay.

    When the Exchange Server computer notifies Outlook 2003  of a change,
the "Download"  timer starts. Outlook delays receiving the change information
in favor of server load and in favor of network performance, because Outlook
is frequently notified of multiple server changes in quick succession. All
notifications that occur in the "Download" 30-second window are grouped 
together, and then they are processed at the end of the timer.  The timer is
then reset to wait for the next server notification.

When a new mail notification is received, Outlook 2003 synchronizes folders
where new or changed items reside. Unread counts are updated, and then any
rules are processed.

Show quoteHide quote
"Maki" wrote:

> Running a single exchange 2003 server. Some staff members need 30 seconds to
> receive a message once sent. Is this a standard time for the exchange server
> or should everybody within the same network get the message instantly?