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

I can't to disable a responder on Exchange Server 2013

$
0
0

Hello; i have a problema with continuos restart of a Exchange Server 2013.

Analizing the dumb the bugcheck was: 0x000000ef (0xffffe001c4228080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000).

Investigating in this fórums and internet; i found that reboot cause from ActiveDirectoryConnectivityServerReboot responder. Whit this query:

(Get-WinEvent -LogName Microsoft-Exchange-ManagedAvailability/* | % {[XML]$_.toXml()}).event.userData.eventXml| ?{$_.ActionID -like "*ForceReboot*"} | ft RequesterName

ActiveDirectoryConnectivityServerReboot

This Exchange 2013 server is in CU7

Name      AdminDisplayVersion
----      -------------------
EXC01   Version 15.0 (Build 1044.25) 

And then i tried to add a global monitoring override to disable the ActiveDirectoryConnectivityServerReboot responder

Add-GlobalMonitoringOverride -Identity Exchange\ActiveDirectoryConnectivityServerReboot -ItemType Responder -PropertyName Enabled -PropertyValue 0 -ApplyVersion “15.0.1044.25”

The before command end without errors

But when a try to query the status of the responder propertie; show enable.

(Get-WinEvent -LogName Microsoft-Exchange-ActiveMonitoring/responderdefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like “ActiveDirectoryConnectivityServerReboot"} | ft name,enabled

Name                                                                       Enabled

---------                                                                   -------------------------- 

ActiveDirectoryConnectivityServerReboot                        1

Why i can't to disable that responder? what i am doing wrong?

please help me. Thank you very much.


Best regards, Javier Uribe


Viewing all articles
Browse latest Browse all 8719

Trending Articles



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