Never did a network scan to determine what the load would be, but you might
find http://msexchangeteam.com/archive/20...13/181940.aspx fun to read
since it deals with this very question.

"Kerry" wrote in message
...
Hi I added the force polling registry key ... will this cause alot of
network
traffic if I apply it to 300 machines?

"neo [mvp outlook]" wrote:

Generally this means that client workstation is not receiving a UDP
network
packet from the server to update itself. Since you didn't mention what
version of Microsoft Outlook your site is using nor operating system, I
would start with the basics of...

1) If running Windows XP with the firewall (any firewall really), to turn
it
off or create an exemption for the binary Outlook.exe so it can listen
for
all traffic types.

2) If running an older version of Microsoft Outlook (e.g. Outlook 2002
from
Office XP) and you don't want to mess with firewall settings, then you
can
try the force polling registry edit.

Outlook 2000
http://support.microsoft.com/default...304849&sd=RMVP

Outlook 2002
http://support.microsoft.com/default...305572&sd=RMVP

Outlook 2003 and later doesn't require the registry edit as it has logic
to
handle this.


"Kerry" wrote in message
...
Hello,

We just switched from exchange 55 to exchange 2003. All staff have the
outlook client. Oneof the things that was happening before our switch
was
that messages sent internal were not being delivered intantly to the
staff
persons inbox. In fact, if you opened and existing email, then you
would
see
the inbox updated with messages that hadn't been delivered yet.

Can anyone help with this, are there any settings that can bechanged to
speed up delivery.

Thanks in advance
Kerry