Document sharing and collaboration: PFs do not provide any document management features such as check-in and check-out functionality and automatic notifications for content change.

Data Archiving: Sometimes users will use the PFs to archive their mailbox data this will affect the storage of PF.

NOTE: Public Folders are not designed for: Single-Master Replication Model: In this model the Public folder is part of DAG and it uses standard transaction log shipping method. Problem here is the replication is carryied through SMTP messages sent between the server databases and it may lead to conflicts when the same data is updated concurrently. Have 2 or more Public Folder Databases and all databases are replicating each other and all PF databases are writable. Multi-Master Replication Model: In this model we

The PF is moving away from Multi-Master Replication Model to a Single-Master Replication Model of the Database Availability Groups (DAGs). These are special mailboxes which store both the public folder hierarchy and the content and the replication uses continuous replication model. In Exchange 2013 the Public Folder is no longer a separate database. The drawback with this replication is that sometimes the user needs to wait for minutes to get the PF updated. In Exchange2010, the public folders were not part of Database Availability Groups (DAGs) and used same PF replication method to achieve resilience and high availability.

This was done for to allow PF replica to be available to users on the nearby network/server in order to save bandwidth and improve performance. Public folders used their own database replication between servers for high availability.

View exchange public folder