Microsoft KB Archive/274219

= XCCC: Front-End Server Considerations =

PSS ID Number: 274219

Article Last Modified on 6/6/2003

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-



This article was previously published under Q274219



SUMMARY
This article describes issues that you should consider when you configure a front-end server in an Exchange 2000 Server front-end and back-end topology.

For additional information about the latest service pack for Microsoft Exchange 2000 Server, click the article number below to view the article in the Microsoft Knowledge Base:

301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

NOTES:  Exchange 2000 Standard Edition cannot be used as front end server in a front end/back end configuration. Exchange 2000 Standard Edition can be used as a back end server. Exchange 2000 Enterprise Server can be implemented as a front end server or a back end server for front end/back end configuration. For additional information about the differences between Exchange 2000 Enterprise Server and Exchange 2000 Standard Edition, click the article number below to view the article in the Microsoft Knowledge Base:

296614 Differences Between Exchange 2000 Standard and Enterprise





MORE INFORMATION
When you are configuring an Exchange 2000-based front-end server, you must take the following considerations in to account:
 * If the front-end server accepts SMTP mail from the Internet, you must start the Microsoft Exchange Information Store service, and mount at least one private information store. In certain situations (most notably, the generation of non-delivery reports), the SMTP service requires the store to do conversion. If the store is not mounted, messages that need to be converted are stuck in the local delivery queue. For security reasons, it is recommended that no user mailboxes are homed on a front-end server's information store.
 * If there are servers that are running Exchange Server 5.5 in the same site (routing group), you must configure the Microsoft Exchange Message Transfer Agent (MTA) Stacks service to run on the front-end server so that the MTAs can bind and transfer mail through the remote procedure call (RPC). If X.400 connectors or Exchange Development Kit (EDK) gateway connectors are homed on the front-end server, the MTA service must run on the front-end server as well.
 * If you delete all public and private information stores, you are not able to change configurations by using Internet Services Manager (ISM). If you must change configurations by using ISM, for example, changes to the Secure Socket Layer (SSL) encryption configuration, make sure that you complete the procedures described in this article before you remove the stores, or leave the private information store intact on the front-end server.

For more information, consult the Exchange 2000 Front-end and Back-end Topology white paper, which can be found on the following Microsoft Web site:

http://www.microsoft.com/exchange/techinfo/deployment/2000/E2KFrontBack.asp

NOTE: When you create a Front End server for a Front End/Back End environment, do not delete the First Storage Group object in Exchange System Manager. The Microsoft Exchange Information Store service (and it's related services) depends on the First Storage Group object existing in the directory.

Additional query words: FE-BE firewalls hosting ASP FE IS

Keywords: kbinfo KB274219

Technology: kbExchange2000Search kbExchange2000Serv kbExchange2000ServSearch kbExchangeSearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.