<div>
more info <br />
<br />
<a href="http://holyhandgrenade.org/blog/2010/12/exchange-2010-sp1-update-rollup-2-supports-multiple-public-folder-databases/" rel="ugc">http://holyhandgrenade.org/blog/2010/12/exchange-2010-sp1-update-rollup-2-supports-multiple-public-folder-databases/</a>
</div>


more info

http://holyhandgrenade.org/blog/2010/12/exchange-2010-sp1-update-rollup-2-supports-multiple-public-folder-databases/ [http://holyhandgrenade.org/blog/2010/12/exchange-2010-sp1-update-rollup-2-supports-multiple-public-folder-databases/]

<div>
Thanks. &nbsp;Good info. &nbsp;We have 200 public folders. &nbsp;Would I have to configure replication for each one? &nbsp;Or could I batch this using the Shell?
</div>


Thanks.  Good info.  We have 200 public folders.  Would I have to configure replication for each one?  Or could I batch this using the Shell?

<div>
no of course you can use the <br />
<br />
AddReplicaToPFRecursive.ps<wbr />1 -TopPublicFolder \ -ServerToAdd OtherServer 
</div>


no of course you can use the

AddReplicaToPFRecursive.ps1 -TopPublicFolder \ -ServerToAdd OtherServer

<div>
<div class="content wysiwyg-content">
We currently are running two CCR (continuous cluster replication) Exchange 2007 servers on Server 2008 R2. &nbsp;We also use mail-enabled public folders. &nbsp;We would like to upgrade to Exchange 2010 so we can lose the external Hub Transport / Client Access server, which I see as one additional point of failure. &nbsp;The problem is the new architecture of Exchange 2010 does not use CCR and its &quot;successor,&quot; DAG (database availability group) does not work with public folders. &nbsp;I assume this is part of Microsoft's continuing effort to force everyone onto Sharepoint. &nbsp;Anyway, the question is what would be the best configuration that would let me upgrade to Exchange 2010, keep my mail-enabled public folders and accommodate some form of high availability?<br />

</div>
</div>


We currently are running two CCR (continuous cluster replication) Exchange 2007 servers on Server 2008 R2.  We also use mail-enabled public folders.  We would like to upgrade to Exchange 2010 so we can lose the external Hub Transport / Client Access server, which I see as one additional point of failure.  The problem is the new architecture of Exchange 2010 does not use CCR and its "successor," DAG (database availability group) does not work with public folders.  I assume this is part of Microsoft's continuing effort to force everyone onto Sharepoint.  Anyway, the question is what would be the best configuration that would let me upgrade to Exchange 2010, keep my mail-enabled public folders and accommodate some form of high availability?


High Availability Options for Public Folders and Exchange 2010

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.