Quantcast
Channel: Exchange Server 2013 - Administration, Monitoring, and Performance 论坛
Viewing all articles
Browse latest Browse all 8719

Health monitoring e-mails.

$
0
0

Hi folks,

I'm just starting to take a look at Exchange Server 2013, but one topic I'm finding difficult to navigate is the whole monitoring/probe/responder side of things.

I haven't managed to find much technical reference information on how it works and how to configure it outside of a few TechNet articles that deal with the basic handful of "monitoring" commandlets,this KB article and this appendix that makes reference to some of the object hierarchy.

What I'm having difficulties with, specifically, is that I cannot run Get-MessageTracking log without aplethora of unwanted monitoring e-mails completely obscuring the more relevant user-focused traffic. When I take a look at these messages using the "| fl" option, I get clues that I'm looking at a monitoring situation - as shown with one example below (using "fl Source*,MessageSubject"), but I simply do not know how to make use of this information to find the right override to apply. I've used Get-MonitoringItemIdentity to try and track down the culprit, but I'm just not having any luck it would seem.

Example output from get-messagetrackinglog ... | fl Source*,MessageSubject:

SourceContext  : MDB:0d34c89c-65c8-4741-9779-7370444684e5, Mailbox:2d9eb357-bf57-4eab-9dd6-07d3f7c33ca1, Event:1196011,
                 MessageClass:IPM.Note.MapiSubmitLAMProbe, CreationTime:2013-07-01T15:00:58.600Z, ClientType:Monitoring
Source         : STOREDRIVER
MessageSubject : MBTSubmission/StoreDriverSubmission/0000003a-0000-0000-0000-0000954d15d6-MapiSubmitLAMProbe

SourceContext  : MDB:0d34c89c-65c8-4741-9779-7370444684e5, Mailbox:2d9eb357-bf57-4eab-9dd6-07d3f7c33ca1, Event:1196018,
                 MessageClass:IPM.Note.MapiSubmitLAMProbe, CreationTime:2013-07-01T15:02:58.622Z, ClientType:Monitoring
Source         : STOREDRIVER
MessageSubject :

SourceContext  : 08D03608B0A9C2E3
Source         : STOREDRIVER
MessageSubject : MBTSubmission/StoreDriverSubmission/0000003a-0000-0000-0000-0000954d15d7-MapiSubmitLAMProbe

SourceContext  : MDB:0d34c89c-65c8-4741-9779-7370444684e5, Mailbox:2d9eb357-bf57-4eab-9dd6-07d3f7c33ca1, Event:1196018,
                 MessageClass:IPM.Note.MapiSubmitLAMProbe, CreationTime:2013-07-01T15:02:58.622Z, ClientType:Monitoring
Source         : STOREDRIVER
MessageSubject : MBTSubmission/StoreDriverSubmission/0000003a-0000-0000-0000-0000954d15d7-MapiSubmitLAMProbe

I'm not running CU1 at this point in time.

Can anyone point me in the right direction about where I can read up on this new object hierarchy and how it's configured? I'm quite keen to get these disruptive e-mails out of the logs so I can get back to being productive with get-messagetrackinglog.

Cheers,
Lain


Viewing all articles
Browse latest Browse all 8719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>