In Exchange Server 2003 it is possible to connect to public folders using an IMAP4 connection. Is this still possible with Exchange Server 2010?
In Exchange Server 2007 or 2010 you may encounter an error that the public folder store is corrupted and is in an inconsistent state.
This article demonstrates how to update the public folders setting on multiple Exchange Server mailbox databases at once using PowerShell.
Support for public folders in Exchange Server 2010 can be unclear for some customers since Microsoft began de-emphasizing them in Exchange 2007.
In this tutorial two methods of moving public folder replicas from Exchange Server 2003 to Exchange Server 2010 are demonstrated.
In an Exchange Server 2010 environment Outlook 2003 users may receive an error message when they attempt to connect to an Exchange 2010 Mailbox server.
There is a change in behaviour between Commvault version 7 and version 8 in the way that the Public Folder iData Agent handles public folders, which can lead to some undesirable outcomes.
During a migration from Exchange Server 2007 to Exchange Server 2010 you may encounter a problem with the replication of public folders.
During a transition from Exchange Server 2007 to Exchange Server 2010 you may encounter an error removing a Public Folder Database from the Exchange 2007 server.
In some scenarios a mailbox user sending emails to a mail-enabled Public Folder may receive an undeliverable message with a reason of “MapiExceptionNotAuthorized”.