Monitoring of Exchange2003 and Exchange 5.5

[vad-u]

Hallo colleagues,
has somebody of you experience in monitoring of an
Exchange 2003 server? Our organization runs in the moment an Exchange 5.5, which consists of several sites.
We would like to consolidate it. At the same time we would like to
migrate it to Exchange 2003.
Which parameters would be important for the monitoring of an Exchange
2003 cluster?
Operation system parameters would be are also interesting, but optional.

Thanks and regards

[JuergenF]

[FLynch]

Hi,

Been using HM for Exchange 2003 monitoing for a while now.

Check out:

http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3Perf_ScalGuide/e37b2de5-ac8d-4e92-9e18-85e13f8386ca.mspx

...for an excellent guide on performance monitoring for EX2003.

I use HM perf counters for:

The client-side performance counters include:

• Client: RPCs attempted

• Client: RPCs succeeded

• Client: RPCs failed

• Client: RPCs failed: Server unavailable

• Client: RPCs failed: Server too busy

• Client: RPCs failed: all other errors

• Client: RPCs attempted / sec

• Client: RPCs succeeded / sec

• Client: RPCs failed / sec

• Client: RPCs failed / sec: Server unavailable

• Client: RPCs failed / sec: Server too busy

• Client: RPCs failed / sec: all other errors

• Client: Total reported latency

• Client: Latency > 2 sec RPCs / sec

• Client: Latency > 5 sec RPCs / sec

• Client: Latency > 10 sec RPCs / sec


works really well

[jtaugher]

SNMP Informant's WMI-Exchange contains many OIDs for Exchange that can be reported back for analysis and alerts in AHM using SNMP.

Info found at: http://www.wtcs.org/informant/wmi-exchange/overview.htm

[vad-u]

[FLynch]

Hi,

We use a number of the other MSExchange performance counters - manily for items such as total message sent etc - however from the business perspective we are most interested in the user experience.

There are a number of MTA counters which you could look up at TechNet.

Thanks
Fergus