Disabling Unnecessary Services
Not all Exchange services are required on a front-end server, depending on the protocols being exposed and whether you will be making configuration changes after the initial setup. To stop and disable services, in the Microsoft Management (MMC), use the Services snap-in. The following table shows the Exchange services required — stop and disable all other Exchange services.
Exchange services required for client access
| Client access method | Services required | Comments |
|---|---|---|
HTTP (Outlook Web Access, WebDAV, Exchange ActiveSync®) |
World Wide Web Publishing Service (W3SVC) |
Exchange System Attendant should also be enabled. Allows for administration and IIS metabase update |
POP3 |
Microsoft Exchange POP3 (POP3Svc) |
Exchange System Attendant should also be enabled. Allows for administration and IIS metabase update. |
IMAP4 |
Microsoft Exchange IMAP4 (IMAP4Svc) |
Exchange System Attendant should also be enabled. Allows for administration and IIS metabase update |
SMTP |
Simple Mail Transfer Protocol (SMTPSVC), Microsoft Exchange System Attendant (MSExchangeSA), Microsoft Exchange Information Store (MSExchangeIS) |
SMTP uses the Exchange Information Store for DSN formatting. If a server is running SMTP, then it should also run the Microsoft Exchange Routing Service (RESVC) |
Generally, System Attendant should be running on a front-end server. Although not required for several protocols, certain tasks only occur if System Attendant is running. Also, additional services may be required depending on other roles the front-end server performs, for example if the server is running WMI automation the Microsoft Exchange Management service must be running.
Note
NNTP must be enabled on a server during upgrade; however, you can disable it if you are not offering NNTP to your users.