XP SP 2 changes Outlook 2000 behaviour...

[run4yourlives]

Just a message to all, since I had a hell of a time dealing with this
problem, and the "solutions" are few and far between; remaining
unacceptable in my mind.

XP Service Pack 2 changes the way Outlook 2000 interacts with the
Exchange Server, causing a "delay" in sending and recieving mail.

From MS:

"The default preference for e-mail notification in Outlook is UDP, and
if that fails, then it uses polling...The default polling time is 60
seconds and is set at the Exchange Server."

XP Service Pack 2 blocks all UDP communication between Outlook and
Exchange, EVEN IF THE FIREWALL IS "OFF"! (which makes me wonder what
"off" really means).
If someone can prove me wrong here, I'm listening, since all my
efforts to try and prove otherwise have failed.

So, with SP2 on Windows XP, Outlook will run using RPC polling, which
defaults to a 60 second minimum value, meaning the maximum polling
time is 120 seconds. To a user this means email is delayed up to two
minutes.

This is a noticable change for any user used to working with outlook
in a corporate enviornment; and to many unacceptable, as it pretty
much destroys the previous percieved real-time interaction. My gmail
account works faster.

Furthermore, the 60 second polling interval is set by the Exchange
Server and requires the addition of a registry key on the server to
change. In addition, MS recommends that 60 seconds is the minimum
value used.

Something for all those in corporate environments to be aware of.
Since we have a network firwall anyways, I'll be withholding
installing SP2 on corporate machines, lest I have to deal with people
thinking their outlook is broken.

 

[Star Fleet Admiral Q]

I doubt many corporate users would even notice a 60 second (that's 1 minute)
delay - most corporate environment take longer than that for exchange to
perform the necessary virus/worm/Trojan/malware/spammail scans (you are
doing those on all mail - inbound/outbound internal/external - right),
depending on what version of protection you are using.

 

[Berger Harald]

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\RPC]
"ForcePolling"=dword:00000000

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\RPC]
"ForcePolling"=dword:00000000

 

[run4yourlives]

Dude you need a new server... 60 seconds for email delivery is an eternity...

Ours is almost instantanous. Even with the av/spam filters.

 

[run4yourlives]

Unfortunatley, that's Outlook 2003, and at any rate, it's already
polling... setting it to default to poll is really irrelevant.

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\RPC]
"ForcePolling"=dword:00000000

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\RPC]
"ForcePolling"=dword:00000000

Just a message to all, since I had a hell of a time dealing with this
problem, and the "solutions" are few and far between; remaining
unacceptable in my mind.

XP Service Pack 2 changes the way Outlook 2000 interacts with the
Exchange Server, causing a "delay" in sending and recieving mail.

From MS:

"The default preference for e-mail notification in Outlook is UDP, and
if that fails, then it uses polling...The default polling time is 60
seconds and is set at the Exchange Server."

XP Service Pack 2 blocks all UDP communication between Outlook and
Exchange, EVEN IF THE FIREWALL IS "OFF"! (which makes me wonder what
"off" really means).
If someone can prove me wrong here, I'm listening, since all my
efforts to try and prove otherwise have failed.

So, with SP2 on Windows XP, Outlook will run using RPC polling, which
defaults to a 60 second minimum value, meaning the maximum polling
time is 120 seconds. To a user this means email is delayed up to two
minutes.

This is a noticable change for any user used to working with outlook
in a corporate enviornment; and to many unacceptable, as it pretty
much destroys the previous percieved real-time interaction. My gmail
account works faster.

Furthermore, the 60 second polling interval is set by the Exchange
Server and requires the addition of a registry key on the server to
change. In addition, MS recommends that 60 seconds is the minimum
value used.

Something for all those in corporate environments to be aware of.
Since we have a network firwall anyways, I'll be withholding
installing SP2 on corporate machines, lest I have to deal with people
thinking their outlook is broken.

 

[Berger Harald]

Disable polling !

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Outlook\RPC]
"ForcePolling"=dword:00000000

and exclude Outlook.exe in the firewall !

Unfortunatley, that's Outlook 2003, and at any rate, it's already
polling... setting it to default to poll is really irrelevant.

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\RPC]
"ForcePolling"=dword:00000000

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\RPC]
"ForcePolling"=dword:00000000

Just a message to all, since I had a hell of a time dealing with this
problem, and the "solutions" are few and far between; remaining
unacceptable in my mind.

XP Service Pack 2 changes the way Outlook 2000 interacts with the
Exchange Server, causing a "delay" in sending and recieving mail.

From MS:

"The default preference for e-mail notification in Outlook is UDP, and
if that fails, then it uses polling...The default polling time is 60
seconds and is set at the Exchange Server."

XP Service Pack 2 blocks all UDP communication between Outlook and
Exchange, EVEN IF THE FIREWALL IS "OFF"! (which makes me wonder what
"off" really means).
If someone can prove me wrong here, I'm listening, since all my
efforts to try and prove otherwise have failed.

So, with SP2 on Windows XP, Outlook will run using RPC polling, which
defaults to a 60 second minimum value, meaning the maximum polling
time is 120 seconds. To a user this means email is delayed up to two
minutes.

This is a noticable change for any user used to working with outlook
in a corporate enviornment; and to many unacceptable, as it pretty
much destroys the previous percieved real-time interaction. My gmail
account works faster.

Furthermore, the 60 second polling interval is set by the Exchange
Server and requires the addition of a registry key on the server to
change. In addition, MS recommends that 60 seconds is the minimum
value used.

Something for all those in corporate environments to be aware of.
Since we have a network firwall anyways, I'll be withholding
installing SP2 on corporate machines, lest I have to deal with people
thinking their outlook is broken.

 

[Berger Harald]

for outlook 2000:

Disable polling !

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\9.0\Outlook\RPC]
"ForcePolling"=dword:00000000

and exclude Outlook.exe in the firewall !

Unfortunatley, that's Outlook 2003, and at any rate, it's already
polling... setting it to default to poll is really irrelevant.

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\RPC]
"ForcePolling"=dword:00000000

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\RPC]
"ForcePolling"=dword:00000000

Just a message to all, since I had a hell of a time dealing with this
problem, and the "solutions" are few and far between; remaining
unacceptable in my mind.

XP Service Pack 2 changes the way Outlook 2000 interacts with the
Exchange Server, causing a "delay" in sending and recieving mail.

From MS:

"The default preference for e-mail notification in Outlook is UDP, and
if that fails, then it uses polling...The default polling time is 60
seconds and is set at the Exchange Server."

XP Service Pack 2 blocks all UDP communication between Outlook and
Exchange, EVEN IF THE FIREWALL IS "OFF"! (which makes me wonder what
"off" really means).
If someone can prove me wrong here, I'm listening, since all my
efforts to try and prove otherwise have failed.

So, with SP2 on Windows XP, Outlook will run using RPC polling, which
defaults to a 60 second minimum value, meaning the maximum polling
time is 120 seconds. To a user this means email is delayed up to two
minutes.

This is a noticable change for any user used to working with outlook
in a corporate enviornment; and to many unacceptable, as it pretty
much destroys the previous percieved real-time interaction. My gmail
account works faster.

Furthermore, the 60 second polling interval is set by the Exchange
Server and requires the addition of a registry key on the server to
change. In addition, MS recommends that 60 seconds is the minimum
value used.

Something for all those in corporate environments to be aware of.
Since we have a network firwall anyways, I'll be withholding
installing SP2 on corporate machines, lest I have to deal with people
thinking their outlook is broken.

 

[run4yourlives]

Disable polling !

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Outlook\RPC]
"ForcePolling"=dword:00000000

and exclude Outlook.exe in the firewall !

Unfortunatley, that's Outlook 2003, and at any rate, it's already
polling... setting it to default to poll is really irrelevant.

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\RPC]
"ForcePolling"=dword:00000000

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\RPC]
"ForcePolling"=dword:00000000


On 8 Sep 2004 15:28:00 -0700, (e-mail address removed) (run4yourlives)
wrote:

Just a message to all, since I had a hell of a time dealing with this
problem, and the "solutions" are few and far between; remaining
unacceptable in my mind.

XP Service Pack 2 changes the way Outlook 2000 interacts with the
Exchange Server, causing a "delay" in sending and recieving mail.

From MS:

"The default preference for e-mail notification in Outlook is UDP, and
if that fails, then it uses polling...The default polling time is 60
seconds and is set at the Exchange Server."

XP Service Pack 2 blocks all UDP communication between Outlook and
Exchange, EVEN IF THE FIREWALL IS "OFF"! (which makes me wonder what
"off" really means).
If someone can prove me wrong here, I'm listening, since all my
efforts to try and prove otherwise have failed.

So, with SP2 on Windows XP, Outlook will run using RPC polling, which
defaults to a 60 second minimum value, meaning the maximum polling
time is 120 seconds. To a user this means email is delayed up to two
minutes.

This is a noticable change for any user used to working with outlook
in a corporate enviornment; and to many unacceptable, as it pretty
much destroys the previous percieved real-time interaction. My gmail
account works faster.

Furthermore, the 60 second polling interval is set by the Exchange
Server and requires the addition of a registry key on the server to
change. In addition, MS recommends that 60 seconds is the minimum
value used.

Something for all those in corporate environments to be aware of.
Since we have a network firwall anyways, I'll be withholding
installing SP2 on corporate machines, lest I have to deal with people
thinking their outlook is broken.

that doens't work. My SP2 firewall is disabled (!) and it still polls.
Besides, like I said, it's for 2003, not 2000. I don't have those keys
in my registry. Under 9.0, I only have the first one, and it reverts
back to "1" as soon as outlook is opened.

Thanks for your help though.