none
Microsoft exchange service notifications broker

    Question

  • In my Exchange Server 2016 microsoft exchange service notifications broker is always stopped, what is this service? It's normal he stand it?
    Thursday, May 19, 2016 12:25 PM

Answers

  • Hi,

    This behavior is expected in on-premises deployments of Exchange 2016. The Notifications Broker service performs a configuration check on each time the server starts. If there is nothing for the Notifications Broker service to do, it stops automatically until the next time the server is restarted.

    When you start your Exchange server, you might notice the Notifications Broker service start and then stop after approximately 30 seconds. If you attempt to start the service manually, it will successfully start and then stop, again after approximately 30 seconds. No errors or warnings are included in the Event log.

    Best Regards.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Lynn-Li
    TechNet Community Support


    Friday, May 20, 2016 1:49 AM
    Moderator

All replies

  • Hi,

    This behavior is expected in on-premises deployments of Exchange 2016. The Notifications Broker service performs a configuration check on each time the server starts. If there is nothing for the Notifications Broker service to do, it stops automatically until the next time the server is restarted.

    When you start your Exchange server, you might notice the Notifications Broker service start and then stop after approximately 30 seconds. If you attempt to start the service manually, it will successfully start and then stop, again after approximately 30 seconds. No errors or warnings are included in the Event log.

    Best Regards.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Lynn-Li
    TechNet Community Support


    Friday, May 20, 2016 1:49 AM
    Moderator
  • Hi,

    i've noticed this issue also with On-Premises Exchange 2016 running on Server 2012.

    It's annoying in the dashboard as there is always a big red indicator stating that the service is stopped - any way for the dashboard to ignore this service as the behaviour it exhibits is considered normal?

    Kind Regards

    Brad Anderson

    Wednesday, April 26, 2017 10:33 AM
  • I was thinking the same thing!  See this...

    http://www.admin-enclave.com/en/articles/exchange/230-resolved-microsoft-exchange-notifications-broker-as-stopped-and-giving-a-red-error-in-the-dashboard.html

    Andy

    Friday, June 9, 2017 6:19 PM