It mostly happens because the Requestor name provided in Set-ServerComponentState is not matching the Requestor that changed the state originally.
(Get-ServerComponentState -Identity <ServerName> -Component <Component>).LocalStates
In following example, Monitoring & RecoveryActionsEnabled are Inactive.
Use following command to find Requestor that change state of Monitoring component to Inactive:
(Get-ServerComponentState -Identity Exch1 -Component Monitoring).LocalStates
Now that you know the Requester, use following command to change the state of Monitoring to Active:
Set-ServerComponentState -Identity Exch1 -Component Monitoring -State Active -Requester Functional
Get-ServerComponentState -Identity exch1 -Component Monitoring).LocalStates
Article ID: 2958835 - Last Review: Sep 24, 2015 - Revision: 1