Exchange 2010 DAG has a weakness and it's Public Folders

Ehlo All,

One of Exchange Server 2010's best new features is Database Availability Groups. This is a high availability solution for mailbox servers. So, while Microsoft advertises how you can use JBOD and no RAID for disk subsystems for Exchange Server 2010 Mailbox Servers (see the Microsoft User Group presentation on this topic), there is one weakness with this. DAG does not work for Public Folders. So, do not put your Public Folder database on a non-RAID Mailbox Server. Plan on deploying a mailbox server that runs the Public Folder database with a well protected and appropriate disk subsystem. This is unfortunate especially since every Exchange environment deployment I've seen and worked on uses Public Folders. Maybe a future service pack or E15 can fix this. This isn't an easy fix though due to how Outlook clients communicate with Exchange 2010 though. Stay tuned.

-Ben

They are back from the dead... Exchange's next version will "re-emphasis" Public Folders

Hello Exchange Folks,

Microsoft reversed course and now Exchange's Public Folders will stay a major component in Exchange Server. This is good news for all. I was a bit worried about the loss of such and the removal of the GUI for Public Folders management in Exchange 2007. Microsoft fixed this in SP1, adding such functionality. Now, Microsoft outlined the following at the URL below... (fyi: this is the Exchange team blog, and has a wealth of great information).

http://msexchangeteam.com/archive/2008/03/31/448537.aspx

Scenario
Use Public Folders Currently?
Document Sharing - SharePoint may be better option.
Calendar Sharing - No need to move
Contact Sharing - No need to move
Discussion Forums - No need to move
Distribution Group Archive - No need to move
Custom Applications - SharePoint may be better option
Organizational Forms - No need to move (or look into use of InfoPath)

From my experience, Public Folders are most frequently used at companies for Calendar Sharing, Contact Sharing, and Distribution Group Archive. So, the need to add SharePoint with it's entire line of support applications (e.g. backup agents [that's plural for SQL and SharePoint], anti-virus, server(s), is a great thing for everyone. Exchange is a great product, so obviously removing and then trying to convince existing users to add more products (e.g. SharePoint) and increase TCO (total cost of ownership) to have the same functionality was a bad idea. Thank you Microsoft for seeing this and making sure Public Folders stayed in Exchange Server.

-Ben