Starting, stopping, and pausing Exchange Server services
As an administrator, you’ll often have to start, stop, or pause
Exchange services. You manage Exchange services through the Computer
Management console or through the Services console.
To start, stop, or pause services in the Computer Management console, follow these steps:
-
If necessary, connect to the remote Exchange server for which you want to manage services, as discussed earlier in this section.
-
Expand the Services And Applications node, and then select Services.
-
Press and hold or right-click the service you want to manipulate,
and then select Start, Stop, or Pause, as appropriate. You can also
choose Restart to have Windows stop and then start the service after a
brief pause. Also, if you pause a service, use the Resume option to
resume normal operation.
Tip
When services that are set to start automatically fail, the status
is listed as blank, and you usually receive notification in a pop-up
window. Service failures can also be logged to the system’s event logs.
You can configure recovery actions to handle service failure
automatically.
Configuring service startup
Essential Exchange services are configured to start automatically
and normally shouldn’t be configured with another startup option. That
said, if you’re troubleshooting a problem, you might want a service to
start manually or you might want to temporarily disable a service.
Configure service startup by completing the following steps:
-
In the Computer Management console, connect to the Exchange server for which you want to manage services.
-
Expand the Services And Applications node, and then select Services.
-
Press and hold or right-click the service you want to configure, and then select Properties.
-
On
the General tab, use the Startup Type drop-down list to choose a
startup option. Select Automatic to start a service when the computer
starts. Select Manual to allow services to be started manually. Select
Disabled to disable the service. Tap or click OK.
Note
The Disabled option doesn’t stop the service if it’s currently
running. It just prevents the service from starting the next time you
start the server. To stop the service, you must tap or click Stop.
Configuring service recovery
You can configure Windows services to take specific actions when a
service fails. For example, you can attempt to restart the service or
reboot the server. To configure recovery options for a service, follow
these steps:
-
In the Computer Management console, connect to the computer for which you want to manage services.
-
Expand the Services And Applications node, and then select Services.
-
Press and hold or right-click the service you want to configure, and then select Properties.
-
On the Recovery tab, you can configure recovery options for the
first, second, and subsequent recovery attempts. The available options
are as follows:
-
Take No Action
-
Restart The Service
-
Run A Program
-
Restart The Computer
-
Configure other options based on your previously selected recovery
options. If you elected to restart the service, you need to specify the
restart delay. After stopping the service, Windows Server waits for the
specified delay period before trying to start the service. In most
cases, a delay of one to two minutes should be sufficient. Tap or click
OK.
When you configure recovery options for critical services, you might
try to restart the service on the first and second attempts and then
reboot the server on the third attempt. If you notice that a service
keeps failing, do some troubleshooting to diagnose and resolve the
underlying issue causing the failure.
Customizing Remote Management services
The Exchange management tools use the Microsoft .NET Framework,
Windows Remote Management (WinRM), and Windows PowerShell for remote
management. WinRM is implemented in the Windows Remote Management
service, which is also referred to as the WS-Management Service or
simply the Management Service. To remotely manage Exchange, your
management computer must run this service and be configured to use the
transports, ports, and authentication methods that your Exchange
servers use. The Exchange server you want to connect to must also run
this service. If this service isn’t running on your management computer
and on the server, remote connections will fail. For remote management,
you normally connect to the PowerShell virtual directory configured in
IIS on a Client Access server.
By default, the Management Service connects to and listens on TCP
port 80 for HTTP connections and on TCP port 443 for secure HTTP
connections. Because firewalls and proxy servers might affect your
ability to connect to remote locations over these ports, talk with your
company’s network or security administrator to determine what steps
need to be taken to allow administration over these ports. Typically,
the network/security administrator will have to open these TCP ports to
allow remote communication between your computer or network and the
remote server or network.
The Management Service is preconfigured to share ports with IIS when
it runs on the same computer, but it does not depend on IIS. To support
remote management, you need to install basic authentication and Windows
authentication for IIS on your Exchange servers. These authentication
techniques are used when you work remotely.
When you are working with an elevated, administrator
command prompt, you can use the WinRM command-line utility to view and
manage the remote management configuration. Type winrm get winrm/config to display detailed information about the remote management configuration.
