In reaction they was up yet another 90 Exchange 2010 servers and started creating public folder replicas on these, with intends to eventually decommission all Exchange 2007 public folder servers. The rest of the 2007 servers could be decommissioned when the Office 365 migration was complete. So we now have about 230 Exchange servers spread around the world, and 1 / 2 of individuals are hosting public folders. How to proceed? The solution ended up being to migrate all mailboxes to switch On the internet and visit website Exchange 2010 public folders on-premises to exist together inside a hybrid configuration.
At this moment, Microsoft only has one article to pay for legacy public folder coexistence for hybrid deployments. Legacy describes both Exchange 2007 and Exchange 2010. I have tried personally this short article numerous occasions along with other hybrid deployments coupled with positive results.
Remote public folders should be made discoverable. This requires developing a dedicated mailbox database on every public folder server. These databases have a single public folder proxy mailbox on all of them. This mailbox ought to be the only mailbox around the database, so make sure to exclude the database(s) from provisioning. For Exchange 2010 make sure to specify the RPCClient AccessServer because the corresponding public folder server using the CAS role installed.
Since DirSync doesn’t sync mail-enabled public folders, the Sync-MailPublicFolders script should be operate on-premises against Exchange Online. I suggest running this script from among the public folder servers. Essentially this script synchronizes mail-enabled public folder SMTP addresses to switch On the internet and hides them in the address list. Following the initial sync, a CSV file is generated.