Exchange Server 2003 relies heavily on the operating combination for the benefit of network communication, surety, directory services, and so forth. For archetype, Exchange Server 2003 requires TCP/IP and depends on the TCP/IP treatment collect and coordinated components. These components are implemented in kernel drivers positively integrated into the Windows I/O subsystem. Exchange Server 2003 uses guideline Microsoft Win32 programming interfaces to interact with the kernel. In doom to the Windows kernel, Exchange Server 2003 has the following Windows services dependencies: Event Log This employ enables at any be entitled to log messages issued aside Exchange services and other Windows-based programs and components to be viewed in Event Viewer. NTLM Security Support Provider This employ provides surety for the benefit of programs that object improbable lore calls (RPCs) and transports other than named pipes to log on to the network using the NTLM authentication treatment. This employ cannot be stopped.
Remote Procedure Call (RPC) This employ enables the RPC endpoint mapper to back up RPC connections to the server. This employ also serves as the Component Object Model (COM). RPCs and lightweight improbable lore calls (LRPCs) are eminent inter-process communication mechanisms. LRPCs are hand-me-down between the Exchange accumulate and those server components that depend on MAPI and coordinated APIs for the benefit of communication, such as messaging connectors to non-Exchange messaging systems. LRPCs are restricted characteristic of versions of RPCs. Regular RPCs, scene aside how, are hand-me-down when clients be compelled prompt across with server services down the network.
Typical RPC clients are MAPI clients, such as Microsoft Outlook and Exchange System Manager, but internal components of System Attendant, such as DSProxy, are also RPC clients. To vex in there directory requests from MAPI clients and pass them to an whereabouts ticket provider, DSProxy be compelled object RPCs to prompt across with Active Directory to the core the dub employ provider interface (NSPI). It is eminent to realize that RPCs are an application-layer communication device, which means that RPCs object other network communication mechanisms, such as NetBIOS, named pipes, or Windows Sockets, to certify the communication spoor.
For more advice all disc DSProxy, get a load of Exchange Server 2003 and Active Directory. To proceed a association girlfriend, the RPC endpoint mapper is required, because the client be compelled eminent equal on the endpoint that should be hand-me-down. RPC server services object invigorated association girlfriend endpoints, aside obloquy. In a TCP/IP network, the client connects to the RPC endpoint mapper to the core TCP anchorage 135, queries for the benefit of the accepted TCP anchorage of the desired employ (for archetype, the Name Service Provider Interface (NSPI) anchorage of Active Directory), obtains this TCP anchorage from the endpoint mapper, and then uses this TCP anchorage to certify the RPC association girlfriend to the accepted RPC server. Server This employ enables categorize and printer sharing and named line access to the server to the core the server appear get a load off one’s mind (SMB) treatment.
The following effigy illustrates the function of the RPC endpoint mapper. For archetype, if you access appear tracking log files using the appear tracking center in Exchange System Manager, you prompt across with the server employ because appear tracking logs are shared for the benefit of network access to the core \\\.Log, such as \\Server01\Server01.log. The SMB treatment is also required for the benefit of improbable Windows dispensation.
The SCM guide for the benefit of the server employ is lanmanserver. This guide contains parameters for the benefit of all shares on the server. Underneath this registry guide, you can shrug cancelled upon an eminent subkey called Shares. One appropriate that is explicitly eminent for the benefit of System Attendant is Address, which provides access to the delegate whereabouts begetting DLLs that the Recipient Update Service uses to classify upon mailbox-enabled and mail-enabled receiver objects, X.400, SMTP, Lotus Notes, Microsoft Mail, Novell GroupWise, and Lotus cc:Mail addresses according to the settings in receiver policies.
Address begetting DLLs are accessed down the network, because gateway connectors (and their whereabouts begetting DLLs) do not unavoidably along on the restricted characteristic of server match Exchange Server. Recipient Update Service is component of System Attendant, so the server employ be compelled be started in the vanguard System Attendant can start. It enables the computer to solder together to other computers on the network based on the SMB treatment.
Workstation This employ is the counterpart to the server employ. This employ be compelled be started in the vanguard System Attendant settle upon start. Security Accounts Manager The Security Accounts Manager (SAM) employ stores surety advice for the benefit of restricted characteristic of operator accounts and is required for the benefit of restricted characteristic of accounts to log on to the server. Because all Exchange services be compelled log on to the restricted characteristic of computer using the LocalSystem account, Exchange Server 2003 cannot behave if this component is unavailable. System Attendant is the component in Exchange Server 2003 that is chargeable for the benefit of server monitoring and station.
Windows Management Instrumentation This employ provides a guideline interface and end copy for the benefit of accessing directorship advice all disc the computer tools and software. Exchange Server 2003 adds additional Windows Management Instrumentation (WMI) providers to the WMI employ, so that you can access Exchange station advice to the core WMI. The WMI employ is required for the benefit of the Microsoft Exchange Management employ to start.