Microsoft Exchange Server for Windows 2000: Planning, Design, and Implementation
A comprehensive resource for implementors and managers of Exchange Server 2000 networks.
TABLE OF CONTENTS Microsoft Exchange Server for Windows 2000: Planning, Design, and Implementation
4.7 Public folders
Public folders are designed to act as repositories for information that must be shared between people. In effect, they are the Exchange equivalent of network file shares. Anything you can put in a file share can be put into a public folder with the same level of protection because both use Windows 2000 ACLs. Information in public folders forms part of the Web Storage system so it can be accessed via automatically generated and maintained URLs. This is an additional benefit not available to network shares.
All of the reasons to create and use public folders that exist in Exchange 5.5 are still valid today. The advent of the Web Storage system makes Exchange 2000 public folders a more powerful repository that can drive websites, and server-side events hold out the prospect that applications can make better use of the data held in the folders. All of the potential can't be exploited unless we have some understanding of how public folders fit into the Store and how they are managed, so let's get going on this topic.
4.7.1 Public folder differences between Exchange 5.5 and Exchange 2000
Two major differences exist between public folders in Exchange 5.5 and Exchange 2000. First, in line with the general partitioning of the Store, multiple public stores can exist on a server instead of the single Public Information Store (PUB.EDB) used by previous versions of Exchange. By default, a single public store called PUB1.EDB is created on a new Exchange 2000...
Copyright Butterworth-Heinemann 2001 under license agreement with Books24x7
