On July 12 th , we announced that Exchange Server 2013 RTM CU2 contained an issue that could result in the loss of public folder permissions when the public folder mailbox is moved between Exchan...
Updated Jul 01, 2019
Version 2.0
Blog Post
I installed two new servers (1x CAS & 1x MBX) with latest CU2 (build 15.0.712.24). Microsoft Exchange Health Manager service does not start automatically after reboot.
Event Viewer System log:
Event ID: 7000
Level: Error
Description:
The Microsoft Exchange Health Manager service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Event ID: 7009
Description:
A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Health Manager service to connect.
Event Xml:
No problem manually starting Microsoft Exchange Health Manager service. When you set the service to ‘Automatic (Delayed Start)’ it starts fine after each reboot.
See also: http://howexchangeworks.com/2013/08/exchange-health-manager-service-wont-start-automatically-after-installing-2013-cu2-v2.html
I think MS should investigate this.