Each Exchange server in the organization relies on a set of services
for routing messages, processing transactions, replicating data, and
much more.
Tip
Of all the Exchange services, the one service that relies on having
a network connection at startup is the Microsoft Exchange Information
Store service. If you start an Exchange server and the server doesn’t
have a network connection, the Microsoft Exchange Information Store
service might fail to start. As a result, you might have to manually
start the service. Sometimes, you’ll find the service has a Stopping
state. In this case, you have to wait until the server completely stops
the service before you restart it.
Working with Exchange services
To manage Exchange services, use the Services node in the Computer
Management console, which you start by completing the following steps:
-
Type compmgmt in
the Apps Search box, and then select Computer Management. Or, on the
Tools menu in Server Manager, select Computer Management.
-
To connect to a remote Exchange server, press and hold or
right-click the Computer Management entry in the console tree, and then
select Connect To Another Computer from the shortcut menu. You can now
choose the Exchange server for which you want to manage services.
-
Expand the Services And Applications node, and then select Services.
Figure 1 shows the Services view in the Computer Management console. The key fields of this window are as follows:
-
Name
. The name of the service.
-
Description
. A short description of the service and its purpose.
-
Status
. The status of the service as started, paused, or stopped. (Stopped is indicated by a blank entry.)
-
Startup Type
. The startup setting for the service.
Note
Automatic services are started when the computer is started. Manual
services are started by users or other services. Disabled services are
turned off and can’t be started. To start a disabled service, you must
first enable it and then start it.
-
Log On As
. The account the service logs on as. The default, in most cases, is the local system account.
Checking required services
You can use
Test-ServiceHealth to determine whether all Windows services that
Exchange requires are running. As shown in the following example and
sample output, the command output lists required services that are
running as well as required services that aren’t running for each
configured Exchange role:
test-servicehealth
Role : Mailbox Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology,
MSExchangeDelivery, MSExchangeIS, MSExchangeMailboxAssistants,
MSExchangeRepl, MSExchangeRPC, MSExchangeServiceHost,
MSExchangeSubmission, MSExchangeThrottling, MSExchangeTransportLogSearch,
W3Svc, WinRM}
ServicesNotRunning : {}
Role : Client Access Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeIMAP4,
MSExchangeMailboxReplication, MSExchangePOP3, MSExchangeRPC,
MSExchangeServiceHost, W3Svc, WinRM}
ServicesNotRunning : {}
Role : Unified Messaging Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology,
MSExchangeServiceHost, MSExchangeUM, W3Svc, WinRM}
ServicesNotRunning : {}
Role : Hub Transport Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology,
MSExchangeEdgeSync, MSExchangeServiceHost,
MSExchangeTransport, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning : {}
