Additional Exchange Server 2003 Services

In addition to IIS protocol engines and Exchange Server 2003 core services, the following Exchange services provide additional functionality:

• Calendar Connector   The Calendar Connector service enables the sharing of free/busy information between Exchange Server 2003 users and Lotus Notes or Novell GroupWise users. This service depends on the event log, Exchange Information Store service, and Microsoft Exchange Connectivity Controller. For more information about the architecture of Calendar Connector, see Gateway Messaging Connectors Architecture.

  The executable file is Calcon.exe, which resides in the \Program Files\Exchsrvr\Bin directory. The registry key is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeCalCon.

• Connectivity Controller   The Connectivity Controller service provides support services for Connector for Lotus Notes, Connector for Novell GroupWise, and Calendar Connector. This service depends on the Event Log service and System Attendant. For additional information about the architecture of Connectivity Controller, see Gateway Messaging Connectors Architecture.

  The executable file is Lscntrl.exe, which resides in the \Program Files\Exchsrvr\Bin directory. The registry key is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeCOCO.

• Connector for Lotus Notes   The Connector for Lotus Notes service enables the transfer of messages and directory synchronization between Exchange Server 2003 and Lotus Notes. This service depends on Event Log, Connectivity Controller, and the Exchange Information Store service. For more information about the architecture of Connector for Lotus Notes, see Gateway Messaging Connectors Architecture.

  The executable file is Dispatch.exe, which is started with LME-NOTES command-line parameters to launch Lotus Notes-specific connector processes. Dispatch.exe resides in the \Program Files\Exchsrvr\Bin directory. The registry key is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LME-NOTES.

• Connector for Novell GroupWise   The Connector for Novell GroupWise service enables the transfer of messages and directory synchronization between Exchange Server 2003 and Novell GroupWise. This service depends on Event Log, Connectivity Controller, Router for Novell GroupWise, and the Exchange Information Store service. For more information about the architecture of Connector for Novell GroupWise, see Gateway Messaging Connectors Architecture.

  The executable file is Dispatch.exe, which is started with LME-GWISE command-line parameters to launch Novell GroupWise-specific connector processes. Dispatch.exe resides in the \Program Files\Exchsrvr\Bin directory. The registry key is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LME-GWISE.

• Exchange Event service   The Exchange Event service monitors folders and triggers events for server scripts that are compatible with Exchange Server 5.5. This service is required only when you are running Exchange Server 5.5 compatible applications on a server running Exchange Server 2003. It is disabled by default. This service depends on the Exchange Information Store service. The executable file is Events.exe, which resides in the \Program Files\Exchsrvr\Bin directory. The registry key is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeES.

• Exchange Management service   This service provides Exchange management information using Windows Management Instrumentation (WMI). If this service is stopped, WMI providers implemented to work in Microsoft Exchange Management, such as message tracking and Active Directory access, will not work. For this reason, you should leave this service running on all servers running Exchange Server, so that you can view and set the domain controllers and global catalog servers for an Exchange Server 2003 server, and use the message tracking center to audit message flow through Exchange. To provide directory access, you can use Exchange System Manager to manually configure a domain controller or global catalog server (open the server's Properties page, then use the options on the Directory Access tab). The servers running Exchange Server will then use the specified servers to access the directory.

  The Exchange Management service depends on the Remote Procedure Call (RPC) service and the Windows Management Instrumentation (WMI) service. The executable file is Exmgmt.exe, which resides in the \Program Files\Exchsrvr\Bin directory. The registry key is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeMGMT.

• Microsoft Exchange MTA Stacks service   The Microsoft Exchange MTA Stacks service (MTA) routes messages through X.400 and gateway connectors to non-Exchange messaging systems. In a mixed environment with servers running Exchange Server 5.5 in the local routing group, the MTA is also used to transfer messages between Exchange Server 2003 and Exchange Server 5.5. This occurs because Exchange Server 5.5 MTAs communicate with each other in the local site directly through RPCs. Exchange Server 2003 must rely on this communication method for backward compatibility.

  The executable file of the Microsoft Exchange MTA Stacks service is EMSMTA.exe, which is located in the \Program Files\Exchsrvr\bin directory. This service depends on System Attendant and maintains its own specific message queues outside the Exchange store in the \Program Files\Exchsrvr\Mtadata directory. The registry key is HKEY_Local_Machine\System\CurrentControlSet\Services\MSExchangeMTA.

  Note

  You should leave the Microsoft Exchange MTA Stacks service running, so that server monitors in their default configuration do not report a server running Exchange Server as unavailable. For more information about server status tracking, see Exchange System Manager Architecture.

• Router for Novell GroupWise   The Router for Novell GroupWise service works in conjunction with Connector for Novell GroupWise to transfer messages and perform directory synchronization between Exchange Server 2003 and Novell GroupWise. The Router for Novell GroupWise service interfaces with the Novell GroupWise API gateway, while Connector for Novell GroupWise interfaces with Exchange Server 2003. For more information about the architecture of Connector for Novell GroupWise, see Gateway Messaging Connectors Architecture.

  The Router for Novell GroupWise service depends on System Attendant. The executable file is GWRouter.exe, which resides in the \Program Files\Exchsrvr\Bin directory. The registry key is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeGWRtr.

• Routing Engine   The Routing Engine service provides topology and routing information to servers running Exchange Server 2003. The advanced queuing engine within the SMTP transport subsystem uses this service to provide next-hop information when routing messages within the Exchange organization. If this service is stopped, optimal routing of messages is not available. For additional information on the Routing Engine service and its role in message delivery, see SMTP Transport Architecture.

  The Routing Engine service depends on IIS Admin and runs within the Inetinfo.exe process. This service is implemented in a file called RESvc.dll, which resides in the \Program Files\Exchsrvr\Bin directory. The registry key is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RESvc.

• Site Replication Service   Site Replication Service (SRS) provides directory integration between Exchange Server 5.5 and Exchange Server 2003. SRS runs on Exchange Server 2003 and serves as a modified Exchange Server 5.5 directory. Exchange server 5.5 responds to SRS as another Exchange Server 5.5 directory replication partner. SRS is automatically enabled on the first server that joins an Exchange Server 5.5 site. When you remove the last server running Exchange Server 5.5 from the network, you can disable SRS.

  SRS has no service dependencies. This service is implemented in an executable file called srsmain.exe, located in the \Program Files\Exchsrvr\Bin directory. The registry key is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSRS.

The following figure illustrates how the additional services integrate with the core services of Exchange, IIS, and the operating system.

Core and additional services of Exchange Server 2003

Tip   To stop all Exchange Server 2003 services on a server, you must stop System Attendant, IIS Admin service, ExIFS, and SRS (if this service is running), and all dependent services. For detailed instructions about how to stop all Exchange Server 2003 services on a server, see How to Stop All Exchange Server 2003 Services on a Server.