DAG not recognised on Some Exchange servers


Article ID: 140148


Updated On:


DX Infrastructure Management NIMSOFT PROBES


exhange_monitor probes are not detecting a DAG on half of the DAG members. 


Release :



One possibility of this is if different version of Exchange Server have been installed on the server and cleanup of prior versions has either not been done or is incomplete.

The probe, on initial deployment, checks for the exchange server version and if there are issues within the environment then it is likely to drop through the checks e.g.

exchange_monitor: (main) server check...is 2007: no

exchange_monitor: (main) server check...is 2010: no

exchange_monitor: (main) server check...is 2013: no

exchange_monitor: (main) server check...is 2016: no

One place to check for issues is in the registry keys. There should be a key/folder relating to the exchange server version e.g.  

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange Server\v15

If keys/folders for other versions of Exchange Server exist at the same time e.g.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange Server\v14

then this can cause issues with detection. 

A cleanup should be done so that only the current Exchange version has a registry key/folder entry.

Once that is done, the existing probe configuration should be saved and probe and folder deleted.

Deploy the probe from new and check the log to determine whether it has correctly identified the Exchange server version.