Heheheh thats true! Sorry about that.
Windows 2003 SP1 on Exchange 2003 w/ SP1. Workstations are Dell Precision 470 with Windows XP Pro SP2. Two DC with Win2k3 & SP1.
WT.
Main Topics
Browse All Topics
Hello,
Recently we have been experiencing major slowness in our Exchange server. Symptoms are slow Outlook operation, and dropped connections, while alerting of inaccessible Exchange server. Most connectivity problems are gone within 2-3 secs!
Hardare Spec:
Single P4 3.0 GHZ
1G RAM
4 SATA 80G disks (RAID5 on a 3ware card)
Approx. 30 users
1G Ethernet on 1G NICs
I was wondering, other then the performance monitor, is there a way for me to efficiently monitor the Exchange server?
What counters should I use to monitor the exchange server?
I am not using the Exchange caching mode in Outlook, should I?
I even replaced a Dell switch with a 3COM switch and disabled the previously configured Jumbo Frames feature, does it matter?
I know this is not the best hardware spec, and indeed we are one step away from buying a new Dell PowerEdge 2850 for that task. But I figured there has to be away to troubleshoot the system, or at least monitor it to pinpoint the problem.
Any information will be greatly appreciates,
WT.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Any clients using desktop search? Google desktop client for example?
It has been identified as a source of issues with performance of the Exchange server.
http://support.microsoft.c
Simon.
If the clients want to use desktop search tools, then they must be pretty static users. Just switch them over to cached mode.
The docs on EXMON aren't brilliant, so take a look at these articles instead:
http://www.msexchange.org/
http://www.windowsitpro.co
You will need to run the tool for a little while to see the trends, but you are looking for heavy users of the Exchange resources.
Here are some perfmon counters that can be useful when troubleshooting these types of issues:
MSExchangeIS\RPC Requests - If this counter reaches 100, connections will be dropped. This is usually an indication that the store is behind on processing.
PhysicalDisk\Avg Disk Sec/Read
PhysicalDisk\Avg Disk Sec/Write - this counter should stay between .001 and .020 on avg (1 and 20 milliseconds). The spikes on this should never exceed 50 ms (.050). If you are consistently above this then Disk I/O latency is probably the issue.
PhysicalDisk\%Idle Time - This should remain in the 95-100% range. If its dropping near 0 then you need to analyze your disk subsystem performance.
CPU usage for store.exe - check this with task manager. If it is spiking (90-100%) then you will probably have to get a process dump of store.exe to figure out whats happening (most likely if it comes to this you will need assistance from MS).
Database\Log Record Stalls - If this is consistently above 0 then the latency could be caused by a lack of log buffers. See http://support.microsoft.c
hope this helps...
Business Accounts
Answer for Membership
by: SembeePosted on 2005-10-04 at 13:02:44ID: 15017219
You missed the vital information.
Windows / Exchange version?
On the clients - Windows / Outlook version. Using cached mode?
Simon.