Entourage 2004 crippling Exchange 2003

G

Guillaume Roberge

300 mailbox Exchange 2003 server. Mostly XP clients using Outlook 2003.
After installing 5 Entourage 2004 running Panther, the Exchange server
response time dropped drastically affecting the entire organization.



After investigating with Windows 2003 PerfMonitor, the RAID Array I/O sky
rockets to abnormaly high levels. (Avg Disk Queue lenght)

Entourage 2004 clients have fairly large mailbox (1-2GB).



Anyone has stumble upon this problem and figured out a solution to what
appears to be a synch issue?



THANKS
 
N

Nathan Herring [MSFT]

300 mailbox Exchange 2003 server. Mostly XP clients using Outlook 2003.
After installing 5 Entourage 2004 running Panther, the Exchange server
response time dropped drastically affecting the entire organization.



After investigating with Windows 2003 PerfMonitor, the RAID Array I/O sky
rockets to abnormaly high levels. (Avg Disk Queue lenght)

Entourage 2004 clients have fairly large mailbox (1-2GB).



Anyone has stumble upon this problem and figured out a solution to what
appears to be a synch issue?



THANKS
Click to expand...

Out of curiosity, are you using public folder support? If so, is it hosted
on the same machine?

-nh
 
G

Guillaume Roberge

Our Exchange 2003 server does host our public folder and our private store
( We have a standalone Exchange site)

Public folders access by Entourage 2004 clients could cause the slowdown of
our Exchange server ?

Thanks for any input on the problem
 
N

Nathan Herring [MSFT]

The previous-to-SP2 mechanism Entourage used (at the instruction of the
Exchange team) ended up causing significant performance issues on the public
folder server. Very few Entourage clients accessing public folders would use
all of the processing power of the server.

After finding the issue and sorting it out with the Exchange team, we
introduced a slight tweak to how we access public folders which reduces the
performance penalty on the servers drastically.

If you have not, I would suggest downloading the 11.2.0 update on your
various clients and seeing if your problem recurs.

-nh
 
Top