ArchiveOne must be deployed in a Microsoft Exchange mail environment. It is not possible to perform a standalone deployment without an active Exchange environment. Multiple versions of Exchange correctly configured with coexistence as per the documented Microsoft process are also supported (for example, Exchange 2010 and 2013 coexistence). ArchiveOne will connect to the CAS running the highest version of Exchange to ensure backwards compatibility with older Exchange versions.
It is assumed that Autodiscover is configured for use in the Exchange environment. This is utilized by ArchiveOne to obtain configuration information about the ArchiveOne service account and mailboxes configured for archiving.
Exchange is supported in both cross forest and resource forest configurations. For more information on the installation process in these environments, refer to How to deploy ArchiveOne in a Microsoft Exchange cross forest deployment or How to deploy ArchiveOne in a Microsoft Exchange resource forest deployment.
There is no requirement that Outlook Web Access (OWA) must be in use. However, if you do make use of OWA then you should consider carefully the deployment of the ArchiveOne Search & Retrieval Websites component to ensure that external users have sufficient access to retrieve archived mail. This is discussed in Step 1 - Prepare for installation.
Office 365 Deployments
ArchiveOne supports both online-only and hybrid deployments with Office 365 where:
- You have configured synchronization of your local on-premises Active Directory (AD) with Office 365 using Active Directory Federation Services (ADFS) or another tool such as DirSync. Cloud identities are not supported; for more information, see the Microsoft Office article Understanding Office 365 identity and Azure Active Directory.
- You have a licence plan which supports MAPI connections. Kiosk and Enterprise K1 licences are not supported as these plans do not allow MAPI connections to the Office 365 Exchange environment.
- If you have multiple domain suffixes, you should ensure that the domain suffix for the user account created in local AD is set to the same domain suffix which has been registered with Office 365. From the 365 administration portal, you can confirm that the account is listed with the correct domain suffix - not one containing 'onmicrosoft.com'. From local AD, you can confirm the account's 'User logon name' property is against the correct domain suffix (e.g. 'ArchiveOneAdmin@barracuda.com', not 'ArchiveOneAdmin@barracuda.local')
- If your Exchange system is a hybrid environment where some users have their primary mailboxes hosted on-premises and only Exchange Archive mailboxes are hosted online, mailbox archiving in Office 365 is not supported.
- Public folder archiving is not supported for public folders hosted in Office 365.