Note This problem affects Outlook 2003 because it uses UDP as its primary method for receiving notifications from an Exchange server.Outlook 2007 is mostly unaffected by this problem because, by default, it uses an asynchronous notification process that does not rely on UDP notifications. I am wondering if importing all the old pst is why (colleague did this method not me). It will be fine for a few days then creep up again. its happened to me a few times but not as much as others. I was having a very similar issue with our users today including my own mailbox.This means when Outlook 2003 moves to Exchange 2010, Outlook clients will fall back to polling which by default only gets notifications at the aforementioned 1 minute intervals.
For more information about how to back up and then restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows You can download Update Rollup 1 for Exchange Server 2010 from the following article in the Microsoft Knowledge Base: 976573 Description of Update Rollup 1 for Exchange Server 2010 After you install the update, you must add the following registry data to the server by using the Client Access role. If you want to make sure that the new settings are applied to all clients, you should recycle the Microsoft Exchange RPC Client Access service because connections from clients can remain alive for a long time. It also resolved the VSS writer timeout errors that I was receiving.
• Items that are moved from one folder to another folder take up to 1 minute to disappear from the original folder.
Generally, you notice that folder updates do not occur automatically in a timely manner.
By default, Outlook performs polling every 60 seconds.
The problems that are described in this article occur because Exchange Server 2010 does not issue UDP notifications to Outlook.
Back to the top Cause When Outlook opens an initial connection to an Exchange server, Outlook tries to...