Exchange 2003 server has high disk I/O latency from Entourage client connections - Not a Spotlight issue

Have an Exchange 2003 server with about 50 Entourage clients connecting to it.  The server recently has slowed down and disk access is very slow.  When I run filemon to see what is using all the disk i/o I find that it the store accessing the .stm database file that the Entourage clients connect to.  We are seeing disk read/write latency of almost .5 seconds.  If we turn http access off to the server then the disk catches up and runs like a top.  When we re-enable http access it goes back to have huge latency and the i/o is all aimed at the .stm database.  All users have spotlight turned off as far was we know.  Our guess is there is a Entourage client doing something odd.  Any ideas?
NetworkRangersAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Stacy SpearConnect With a Mentor President/Principal ConsultantCommented:
Just looked it up. You are right, Entourage uses WEBDAV over HTTP.

This KB article looks like what you may need.

http://support.microsoft.com/kb/329067
0
 
Stacy SpearPresident/Principal ConsultantCommented:
http access to the server normally relates to public folders, address books, and other things that are stored in public folders since they are accessed via http. Check out problems relating to any of those.
0
 
NetworkRangersAuthor Commented:
Does entourage not go through http to do the rest of the mailbox functions as well?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
NetworkRangersAuthor Commented:
I ran across that as well but did not have much faith in it as the errors is described did not match our scenario, but we will give it a try anyway and see what happens.  Will let you know what I see in a few days.  Thanks
0
 
NetworkRangersAuthor Commented:
The problem seems to have gone away since the registry change was made surprisingly.  The errors that were listed in the article weren't what we were getting, but it did seem to fix our problem.  Thanks
0
 
Stacy SpearPresident/Principal ConsultantCommented:
You know as well as I that Exchange, AD, and Microsoft stuff in general are so complicated that seemingly unconnected things can be in fact connected. Sometimes I feel like a witch doctor hunting for evil spirits or something!
0
All Courses

From novice to tech pro — start learning today.