We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

Attention

Starting May 1st, 2018, we will no longer offer the ArchiveOne family of products. This includes all editions of ArchiveOne, ArchiveOne for Files, Max Compression, and Access Security Manager. If you currently hold a maintenance and support contract, you will continue to receive our award-winning support until your contract expires, or until May 1st, 2019, whichever occurs first. The license for ArchiveOne is perpetual; therefore the software may continue to be used independently without any updates or support indefinitely.

How to Deploy ArchiveOne in a Microsoft Exchange Cross-Forest Topology

  • Last updated on

This article refers to the Barracuda ArchiveOne versions 6.5 and higher, and Microsoft Exchange 2010 and higher.

You can install Microsoft Exchange 2010 and 2013 in a cross-forest topology where Exchange is installed in each forest with synchronization between the forests. For details, see the Microsoft TechNet article Deploy Exchange 2010 in a Cross-Forest Topology or Deploy Exchange 2013 in a cross-forest topology.

Do not confuse the cross-forest topology with an Exchange resource forest topology where Exchange is only installed in one forest, as described in the Microsoft TechNet article Deploy Exchange 2010 in an Exchange Resource Forest Topology or Deploy Exchange 2013 in an Exchange Resource Forest Topology.

To deploy ArchiveOne in an Exchange cross-forest topology, you should install ArchiveOne in each forest. ArchiveOne should only process mailboxes in that forest.

For instructions on installing ArchiveOne, refer to Step 3 - Install the ArchiveOne Service and Components.

Last updated on