Determine requestor that changed Server component state

Symptoms
On Exchange Server 2013, you are trying to change state of server component to Active using the Set-ServerComponentState command. The command completes without any error, however, component remains Inactive.

It mostly happens because the Requestor name provided in Set-ServerComponentState is not matching the Requestor that changed the state originally.
Resolution
In such scenario, use following command to find the Requestor that has changed component state:

(Get-ServerComponentState -Identity <ServerName> -Component <Component>).LocalStates

Example:

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



Verify:



Get-ServerComponentState -Identity exch1 -Component Monitoring).LocalStates




More information
Read this blog for in depth understanding of Server component states in Exchange Server 2013.

http://blogs.technet.com/b/exchange/archive/2013/09/26/server-component-states-in-exchange-2013.aspx
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.
Properties

Article ID: 2958835 - Last Review: 09/24/2015 19:40:00 - Revision: 3.0

  • kbsurveynew KB2958835
Feedback