When an ENow monitoring check reports a warning or error, you can often confirm the result by hand from the monitored server. The table below pairs each check with the command that validates it.
Before you start
- Run Exchange commands from the Exchange Management Shell on the monitored server, not a plain PowerShell window.
- Run these under an account with the same rights as the ENow monitoring service account, or the result will not match what ENow sees.
- Replace anything in
<angle brackets>with your own value. - A command succeeding by hand while ENow still reports a failure usually points at the service account's permissions rather than the service itself.
Validation commands
| Monitoring check | Validation command |
|---|---|
| Active Directory Status | Test-Connection <IP Address> |
| ActiveSync | Test-ActiveSyncConnectivity |
| AD Replication Status | repadmin /showrepl * /csv >showrepl.csv |
| DAG Database Copy Health | Get-MailboxDatabaseCopyStatus |
| DAG Replication Health | Test-ReplicationHealth |
| DNS Status | Test-Connection <Server> |
| Edge-Hub Communication | Test-EdgeSynchronization -FullCompareMode |
| IMAP4 | Test-ImapConnectivity |
| Mail Flow | Test-Mailflow |
| MAPI Connectivity | Test-MAPIConnectivity |
| OWA Status | Test-OwaConnectivity |
| POP3 | Test-PopConnectivity |
| Queue Status | Get-Queue |
| Server Component State | Get-ServerComponentState |
Notes on individual checks
- AD Replication Status — run this from a command prompt opened as administrator, not the Exchange Management Shell. The command writes its results to
showrepl.csv; open that file in Excel to read them. - Active Directory Status and DNS Status use the same
Test-Connectioncmdlet, targeting an IP address and a server name respectively.
To open the MailscapeWeb page behind a check instead, see MailscapeWeb monitoring page URLs by check.
Comments
0 comments
Please sign in to leave a comment.