Exchange 2010 lack support for UDP Notifications

Current Status: Issue with mitigation

With 2010 SP1 RU3 UDP notifications is being re-added to to 2010 (read more here). This means that the below symptoms will be resolved, once SP1 RU3 becomes available in March 2011.

With Exchange Server 2010, there is no longer support for User Datagram Protocol (UDP) notifications. When opening a mailbox using 2003, 2003 tries to register itself to receive new message notifications. By default 2003 tried to register for UDP notifications but since this notification method isn’t supported with Exchange 2010, 2003 will instead revert to polling the Exchange server for changes in the mailbox. Despite the fact that 2003 initiates the polling behavior, the Exchange server will dictate the polling frequency. By default 2003 polls the Exchange server every 60 seconds.

Since Exchange 2010 doesn’t support UDP based notifications, Outlook 2003 won’t be able to register itself using this method, which means changes made to any of the folders in the mailbox won’t be reflected before Outlook 2003 polls the Exchange server for changes. The result of this is that notifications about new messages etc. will be reflected in the Outlook 2003 client with delays of up to 60 seconds.
More specifically, you will see the following symptoms:

  • Outgoing e-mail messages stay in the Outbox for up to 1 minute
  • New e-mail messages do not arrive in the Inbox for up to 1 minute
  • Items that are deleted from folders do not disappear from the folder for up to 1 minute
  • Items that are moved from one folder to another folder take up to 1 minute to disappear from the original folder

Two methods exist to remediate the polling issue described above:

Method 1: Change the Polling Frequency

The issue can be remediated by installing Exchange 2010 Service Pack 1 which includes support for a new registry key that can be used to lower the polling frequency to 5 seconds.

Figure 3:
Lowering the polling frequency value

The registry key doesn’t reinstate UDP in Exchange 2010; it only lowers the polling frequency.

Method 2: Enable Cached Mode in Outlook 2003 Clients

The cached mode synchronization process uses a different architecture to update folders versus Outlook 2003 clients in online mode. So another option is to enable cached mode for all Outlook 2003 clients within the organization.

The following KB article describes the symptoms and remediation in detail:

Update: Rollup 3 for Exchange 2010 SP1 is gereleased

Special Thanks to Henrik Walther

Leave a Reply