Customizing Public Folder Referrals
Topic Last Modified: 2005-04-22
When a user connects to a public folder store that does not contain a copy of the public folder content that the user is looking for, Exchange redirects or refers the user to another public folder store that does have a copy of the content. By default, Exchange tries to redirect the user to a server in the local routing group. If those servers do not have the required content, Exchange follows the organization's routing group topology to find an appropriate server. Exchange finds an appropriate server based on the most efficient routing path, using costs of connectors between routing groups.
|For additional information about public folder referrals, see "Managing Mailbox Stores and Public Folder Stores." For more information about routing in Exchange, see "Understanding and Configuring Message Routing and Transport."|
Because Exchange keeps track of available connections between routing groups and uses the most efficient route possible, it is recommended that you use routing groups (the default) to determine how Exchange refers a user to another public folder. However, if you must troubleshoot a specific server, or if you are performing maintenance on part of your network and want to designate specific servers that are available during this maintenance, you can create a custom list of servers for public folder referrals.
|A custom list for public folder referrals is new in Exchange 2003. In Exchange 2000, you can only specify whether to allow public folder referrals among routing groups.|
To create a custom list of servers for public folder referrals, you use the Public Folder Referrals tab. For detailed instructions, see How to Specify a Custom List for Public Folder Referrals. When you create a custom list of servers, you also assign costs to prioritize the servers in your referral list.