I have 2 storage groups in my exch 2000 server and the first default public
store is linked to a tree "PUBLIC FOLDER"  in which the public folder that i
create are shown in MS outlook under public folders link.
The public folders that I create under the second public folder tree in
SYSTEM MANAGER  , are not displayed in MS Outlook , hence i am not able to
use  them .
How to make the public folders created in subsequent public folder trees be
made visibile in MS outlook or Outlook express..
CAn anyone help me on this
thanks
nanda

There can only be one MAPI Public Folder Tree and Outlook will only connect
to that single MAPI Public Folder tree.  If you look at the properties of
each Public Folder tree, you will see that the one that contains the folders
that can be seen by Outlook will have a type of "MAPI Clients".  The other
one, will have a type of "General Purpose.

Check out the Exchange 2000 Technical Library for more information:
http://www.microsoft.com/technet/prodtechnol/exchange/2000/library/default.mspx
The Default (MAPI) Public Folder Tree
When a client accesses the default public folder tree in Outlook Web Access,
an attempt is made to maintain parity with MAPI clients such as Outlook
2002. Each mailbox store is associated with a particular public folder store
somewhere in the organization (sometimes on the same server as the mailbox
store, sometimes on a dedicated public folder server). The public folder
store associated with the user's mailbox store is the public folder store
that displays in Outlook 2002.

When a user requests a public folder in the default public folder tree
through HTTP, the front-end server authenticates the user and looks up the
user in Active Directory to see which public store is associated with that
user's mailbox store. The front-end server then forwards the request to the
user's public folder server.

This ensures that users who switch between Outlook and Outlook Web Access
see the same data and take advantage of the load balancing that the
administrators configured into the system.

If an authenticated user does not have a mailbox associated with it (for
example, when users with accounts in a Microsoft Windows NT® 4.0 domain have
access to Exchange 2000 mailboxes), the front-end server treats accesses to
the default public folder tree the same way as it treats access to the
general-purpose public folder trees. Also note that if the front-end server
is not configured to authenticate users, requests for public folders are not
load balanced.

General-Purpose Public Folder Trees
Default public folder tree servers have an association with mailbox stores
because of their MAPI heritage; general-purpose public folder trees do not
have such an association. As a result, requests for folders in
general-purpose public folder trees are handled slightly differently than
requests for folders in the default public folder tree.

When a client makes a request to access a general-purpose public folder
tree, the front-end server first contacts Active Directory to find a list of
all servers running Exchange 2000 in the organization that have a replica of
the particular general-purpose public folder tree that the client is
attempting to access. This list is filtered to remove servers running
Exchange 5.5, because Exchange 5.5 does not support the HTTP extensions (Web
Distributed Authoring and Versioning) that Exchange 2000 supports.

The front-end server then uses the user's authentication token in a hashing
algorithm against the list of servers to ensure that:

·         Users are load-balanced across the available servers.

·         Individual user requests are always processed by the same back-end
server, regardless of the HTTP client used.

Note   If you add or remove a back-end server, the output from the hashing
algorithm changes, and users may be redirected to a different server from
then on. For more information, see "Adding or Removing Back-End Servers"
later in this document.


--Chris

============================================================================
====
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
============================================================================
====

Show quoteHide quote

OWA issues
Outlook 2003 & OWA on Exchange 2003 query
RUS not stamping an AD acct.
Can't see contacts folder in address list
Exchange 5.5 Trial to test upgrade path
Mail Being Killed?
Exchange 5.5 NDR
Need help asap, no incoming mail, no bad event logs.
Re: Moving the MTADATA folder
Search exchange 2000 for emails