Exchange Server 2013/2016 Components in an Inactive State

Thursday, May 25th 2017

updated – I  made this post more than a year go when I encountered an issue doing maintenance on Exchange Server 2013. Coming from Exchange 2010 maintenance experience it was a quite a different change and for some time I was not sure why the service were not coming backup online. And then it was all related to Exchange 2013/2016 Managed Availability. When I looked it up (only possible via Powershell) I fond that all the services were in InActive State.

You can also use the script to bring the component state back to active state

Original post from 08/7/2014
After applying update or patches on Exchange 2013/2016 and bringing back to out of maintenance you notice that server components are still Inactive as shown below.  In a situation like this you need to go extra mile to bring the server as is before maintenance. Below is the set of cmdlet when you put the server on maintenance where requester is calling for maintenance.

cmdlets/ script is bringing the server out of the maintenance but the component state is still Inactive
Set-ServerComponentState $Server -Component ServerWideOffline -State Active -Requester Maintenance
Set-ServerComponentState $Server -Component UMCallRouter –State Active –Requester Maintenance
Resume-ClusterNode $Serve
Set-MailboxServer $Server -DatabaseCopyActivationDisabledAndMoveNow $False
Set-MailboxServer $Server -DatabaseCopyAutoActivationPolicy Unrestricted
Set-ServerComponentState $Server -Component HubTransport -State Active -Requester Maintenance


In addition to the single components which can be managed individually, there’s also a component called “ServerWideOffline”, which is used to manage the state of all components together, with the exception of “Monitoring” and “RecoveryActionsEnabled”. For this purpose, “ServerWideOffline” overrides individual settings for all other components. It doesn’t touch “Monitoring” and “RecoveryActionsEnabled” because these two components need to stay active in order to keep MA going. Without them, no “OnlineResponder” could bring “ServerWideOffline” back to “Active” automatically. But in this case both Monitoring and RecoveryActionEnabled are Inactive which will not bring the ServerWideOffline back to Active.

 So the server is not 100% functional even though you took it out of maintenance. You will need to perform  the following cmdlet to bring the server in ACTIVE State

Set-ServerComponentState -Component ServerWideOffline -State Active -Requester Functional
Set-ServerComponentState -Component Monitoring -State Active -Requester Functional
Set-ServerComponentState -Component RecoveryActionsEnabled -State Active -Requester Functional



You can also get  the Get-ServerComponentState cmdlet from the Shell to retrieve these settings along with timestamp


You can also use the script to bring the component state back to active state