Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, February 22, 2017 11:07 AM
Hi there
I have a question regarding an Exchange 2016 proof of concept test lab that is set up. None of the Exchange services start automatically after system boot-up (even though they are configured as such), yet if manually started or configured as Delayed Start, everything appears to be working as expected. The latter method of delayed start is causing an expected delay to get up and running but at least I do not have to go manually start all services. Surely this is not normal?
The test environment consists of a domain (2016 functional level) set up from scratch and both the DC and Exchange servers are running the latest build of Server 2016, whilst the latter is running CU4 for Exchange which is also the latest.
Any inputs would be highly appreciated. Thank you in advance.
Regards,
CTV
All replies (3)
Wednesday, February 22, 2017 2:32 PM
Hi there
I have a question regarding an Exchange 2016 proof of concept test lab that is set up. None of the Exchange services start automatically after system boot-up (even though they are configured as such), yet if manually started or configured as Delayed Start, everything appears to be working as expected. The latter method of delayed start is causing an expected delay to get up and running but at least I do not have to go manually start all services. Surely this is not normal?
The test environment consists of a domain (2016 functional level) set up from scratch and both the DC and Exchange servers are running the latest build of Server 2016, whilst the latter is running CU4 for Exchange which is also the latest.
Any inputs would be highly appreciated. Thank you in advance.
Regards,
CTV
Do you see anything in the Application and System Event logs as to why the services aren't starting?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread
Thursday, February 23, 2017 3:21 AM | 1 vote
Hi,
Are you installing a Exchange server on a domain controller?
The main reason services won't start automatically is if their dependencies are not met. All of Exchange services are dependant on the first one - AD Topology. If it fails to start then the rest do as well.
Also refer to the following KB:
Exchange Server services don't start automatically on a global catalog server
Best Regards,
David Wang
TechNet Community Support
Please remember to mark the replies as answers if they helped.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, May 25, 2018 3:51 PM | 1 vote
I think your test machine is just not strong enough.
I tried to run Exchange 2016 on a DELL Latitude E6520 (i7 and 8GB RAM) in our lab and could not get Exchange 2016 Services to start at boot neither. Finally I putted all Exchange 2016 Services who start by default "Automatic" on "Automatic (Delayed Start)" and that works, you just have to wait a few minutes before your test machine is up.
I actually did this an elevated command prompt:
sc config MSExchangeADTopology start=delayed-auto
sc config MSExchangeAntispamUpdate start=delayed-auto
sc config MSComplianceAudit start=delayed-auto
sc config MSExchangeCompliance start=delayed-auto
sc config MSExchangeDagMgmt start=delayed-auto
sc config MSExchangeEdgeSync start=delayed-auto
sc config MSExchangeFrontEndTransport start=delayed-auto
sc config MSExchangeHM start=delayed-auto
sc config MSExchangeHMRecovery start=delayed-auto
sc config MSExchangeIS start=delayed-auto
sc config MSExchangeMailboxAssistants start=delayed-auto
sc config MSExchangeMailboxReplication start=delayed-auto
sc config MSExchangeDelivery start=delayed-auto
sc config MSExchangeSubmission start=delayed-auto
sc config MSExchangeNotificationsBroker start=delayed-auto
sc config MSExchangeRepl start=delayed-auto
sc config MSExchangeRPC start=delayed-auto
sc config MSExchangeFastSearch start=delayed-auto
sc config HostControllerService start=delayed-auto
sc config MSExchangeServiceHost start=delayed-auto
sc config MSExchangeThrottling start=delayed-auto
sc config MSExchangeTransport start=delayed-auto
sc config MSExchangeTransportLogSearch start=delayed-auto
sc config MSExchangeUM start=delayed-auto
sc config MSExchangeUMCR start=delayed-auto
By the way do not try to run Exchange 2016 on a machine with less than 8 GB RAM.
The system will be so slow you won't be able to do any testing on it.
Regards,