New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Having Issues getting Exchange Sensors Working

Votes:

0

Your Vote:

Up

Down

Anyone else having trouble getting Exchange 2007 sensors working? I've attempted to add a number of the builtin Exchange sensors in PRTG and I'm getting the following error.

"Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition: The specified class was not found."

Any suggestions would be appreciated.

2007 exchange exchange-2007 microsoft prtg sensor wmi

Created on Mar 5, 2010 9:43:18 PM by  Scott K (60) 1 1

Last change on Mar 12, 2010 10:41:58 AM by  Daniel Zobel [Paessler Support]



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Under Exchange 2007, Microsoft has indeed replaced CDOEXM and Exchange WMI providers with PowerShell cmdlets. This could, of course, be the reason for this particular issue.

Created on Mar 12, 2010 10:39:19 AM by  Patrick Hutter [Paessler Support] (7,164) 3 3



5 Replies

Votes:

0

Your Vote:

Up

Down

Created on Mar 7, 2010 7:45:49 AM by  Aurelio Lombardi [Paessler Support]

Last change on Mar 9, 2010 7:35:53 AM by  Daniel Zobel [Paessler Support]



Votes:

1

Your Vote:

Up

Down

Thanks for the reply! I've reviewed the information suggested above and I'm still not having any luck. One thing that's got me confused is that I've read that the WMI classes aren't available on Exchange 2007. Can anyone confirm or deny that?

Created on Mar 11, 2010 8:24:11 PM by  Scott K (60) 1 1



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Under Exchange 2007, Microsoft has indeed replaced CDOEXM and Exchange WMI providers with PowerShell cmdlets. This could, of course, be the reason for this particular issue.

Created on Mar 12, 2010 10:39:19 AM by  Patrick Hutter [Paessler Support] (7,164) 3 3



Votes:

1

Your Vote:

Up

Down

I am having the same problem.

Created on Jun 11, 2010 10:48:26 PM by  alexjhart (10)



Votes:

0

Your Vote:

Up

Down

I had the same problem with WMI and Exchange 2007. The following fixed the issue: Run wmiadap /f to re-parse all of the available libraries on the system. Note that you may need to restart the WMI service (winmgmt) after this.

Created on Dec 7, 2010 11:16:41 AM by  Wouter Hindriks (10) 1



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.