Check out our new template for monitoring Exchange 2007 WMI Counters. Exchange 2007's implementation of WMI is atypical, and won't work properly with the WMI Performance Counter Monitor. We built a mechanism and template to get around the limitation. Please import this template and assign it to you Exchange 2007 Hub Transport Servers or Mailbox Servers and you'll get rich monitoring of this application.You can download the app from the Content Zone.More details here:
Exchange 2007 WMI Counters Template
This template creates APM applications to ensure the reliability of your Microsoft Exchange 2007 servers by warning you before performance problems occur.
Some of the Windows Management Instrumentation (WMI) performance counters monitored in this template are only available to Microsoft Exchange 2007 servers that fill Hub Transport Server and/or Mailbox Server roles. Associating this template with a server that does not fill one or both of these roles results in an Unknown status for the unavailable WMI component monitors.
After importing this template, set the Statistic Critical Threshold for the WMI component monitors in the template as follows:
Note: Be sure to Click Submit after modifying the threshold values.
Role: Hub Transport Server - Aggregate Delivery Queue Length (AllQueues) Statistic Critical Threshold: 5000
- Active Remote Delivery Queue Length Statistic Critical Threshold: 250
- Active Mailbox Delivery Queue Length Statistic Critical Threshold: 250
- Submission Queue Length Statistic Critical Threshold: 100
- Active NonSmtp Delivery Queue Length Statistic Critical Threshold: 250
- Retry Mailbox Delivery Queue Length Statistic Critical Threshold: 100
- Retry NonSmtp Delivery Queue Length Statistic Critical Threshold: 100
- Retry Remote Delivery Queue Length Statistic Critical Threshold: 100
- Unreachable Queue Length Statistic Critical Threshold: 100
- Largest Delivery Queue Length Statistic Critical Threshold: 200
- Poison Queue Length Statistic Critical Threshold: 0
Role: Mailbox Server - RPCAveragedLatency Statistic Critical Threshold: 25
- RPCNumofSlowPackets Statistic Critical Threshold: 3
- RPCRequests Statistic Critical Threshold: 70
- MessagesQueuedForSubmission Statistic Critical Threshold: 50
- Public: MessagesQueuedForSubmission Statistic Critical Threshold: 20
- ReplicationReceiveQueueSize Statistic Critical Threshold: 100
- SearchTaskRate Statistic Critical Threshold: 10
- SlowFindRowRate Statistic Critical Threshold: 10
- Averagedocumentindexingtime Statistic Critical Threshold: 30 These Statistic Critical Threshold values were derived from guidance provided by: "Monitoring Without System Center Operations Manager," Microsoft TechNet. http://technet.microsoft.com/en-us/library/bb201720(EXCHG.80).aspx
On Server 2003 do I need to grant specific permissions for WMI to monitor these counters? They all report unable to connect to the servers by WMI using a domain admin member account.
Jeff
Hi Jeff,
Is there a firewall that could be preventing the connection? Remote WMI connections are made through DCOM which means high numbered ports are negotiated during the connection.
To answer your question, a domain account should have the permissions required to connect via WMI.
Here's a link to a tech ref article on how to test WMI connectivity from your APM server to your Exchange server: http://www.solarwinds.com/support/apm/docs/WMITesting.pdf
I'm having the same problem. There's no firewall and the WMI testing worked. I've setup both the WMI counters template as well as the original Exchange 2007 template that came with APM, but both report an unknown status on all components.
Thanks for any help you can provide!
~CJ
***Nevermind, I have noticed that mine do not work either. Those counters are not present on my Exchange Server in either RAW or Formatted. ***
In the template, change one of the monitors from win32_perfformattedData to win32_perfrawdata. (Change the formatted to raw) and see if it starts giving you data. The numbers will not be correct, but see if you get anything.
That will help narrow down whether your WMI driver is populating the Formatted data or not.
If you need better instructions, let me know. And remember which one you did, it will have to be changed back.
Marks
I don't know if this was in response to my post, but it didn't work for me. I let it sit for about 5 minutes after the change. And actually, it was already set to raw from the get go, so I just did the opposite of what you recommended and tried it as formatted. Everything still reports as unknown status.
I think I might have figured it out, at least partially.
It looks like an account issue. I was using my domain account (without the domain prefix).
I, instead, chose an Exchange Admin's account w/ the domain prefix and I'm getting some statuses (thought still not everything).
Now that I know the proper credentials, I might just remove all these apps and start over.
I'll update if I continue to have issues.
Thanks.
Well, that reply was meant for you, but I have spent so much time trying to get SQL, Exchange, and IIS working that I have had my troubleshooting backwards.
I cannot get any meaningful data out of exchange or any of the formatted data enums. I am finding that MS is saying WMI has been removed from Exchange 2007, so I do not know if SP1 added them back. I am still waiting to talk to anyone who has a fully working Exchange 2007 monitor. At least then, I would know to keep beating my head in.
MarkS
Mark, I'm monitoring the Exchange 2007 server we have set up in the SolarWinds lab, so I know it's possible. The one thing I had to bust my head against was getting the proper credential. I thought I had an admin account, but I didn't.
CJ, you're unlikely to get all of the components in the Exchange 2007application monitor to report Up status, because some of the components included in the application template are only available on Exchange servers that are set up for specific roles. For example, if your Exchange server isn't set up in a Unified Messaging (UM) role, the "Microsoft Exchange Unified Messaging" and "Microsoft Exchange Speech Engine" components are going to be missing, and report Down.
You should remove missing components from your application monitors because the Down status of a component monitor affects the status of the application monitor. An application monitor with a missing component will indicate a Down status even though all of its components are operating as they should.
To remove components from an application monitor:
1. Click Application Performance Monitor to return to the APM Summary view.
2. Locate the application monitor in the Down Applications resource, and then click the application name.
3. Write down the components to remove.
4. Click Edit Application.
5. Click Delete adjacent to any component on your removal list, and then wait for the web page to refresh and the component to disappear.
6. Repeat Step 5 for the remaining items on your removal list.
7. Scroll to the bottom of the view, and then click Submit.
Note: If you leave this view without clicking Submit, no changes are made.
8. Verify that the missing components have all been removed from the application monitor. The application monitor status should indicate Up.
Roger Wong: Mark, I'm monitoring the Exchange 2007 server we have set up in the SolarWinds lab, so I know it's possible. The one thing I had to bust my head against was getting the proper credential. I thought I had an admin account, but I didn't.
Ok, I have mine working. In order to get mine to work, I had to do three things.
A) on the exchange server "wmiadap /f"
B) on the exchange server "wmiadap /resync"
C) restart the windows management (wmi) service.
See if that works for you.