You must have the following administrator privileges to deploy Barracuda PST Enterprise:
Machine administration rights on the machines on which you are installing the PST Enterprise Server or Copy Agent Server; and
- Either Domain Administrator or Exchange Administrator rights; and
- Rights to create mail-enabled users and security groups in the domain so that you can create a service account and global security group.
Table 1 lists the minimum hardware and software requirements for each system.
Table 1. Minimum Hardware and Software Requirements.
|System||Minimum Hardware Requirements||Software Requirements|
|PST Enterprise Server|
SQL Server 2008 R2 Express SP2 can optionally be installed during PST Enterprise installation.
Barracuda Message Archiver integration
TLSv1 must be enabled in the SSL settings of the BMA if you wish to run Copy to BMA policies.
|Copy Agent Server|
Copy Agent Server is an optional component required only if you wish to move or copy PST files from client machines to a central server.
|PST Host Client|
You must install a supported version of Outlook on any client machines or file servers where you want to run the Client.
Outlook can connect to either on-premise Exchange or Exchange Online
For best results, do not use Firefox or IE in compatibility mode.
(1)Hard disk space includes SQL Express installation and storage.
Office 365 Deployments
Barracuda PST Enterprise supports both online-only and hybrid deployments with Microsoft 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 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.
- The Exchange Autodiscover web service is accessible and correctly configured.
For Office 365 deployments, it is advised that you first create the PST Enterprise service account in local AD and ensure this has synchronized to Office 365 before proceeding with installation.
If you have multiple domain suffixes, you must ensure that the domain suffix for the service account created in local AD is set to the same domain suffix which has been federated with O365. From the O365 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 (for example, PSTEnterpriseAdmin@barracuda.com, not PSTEnterpriseAdmin@barracuda.local)
Outlook Version Support
For more information on the supported actions for the different versions of Outlook refer to the compatibility matrix on PST Processing Actions Supported by Outlook Versions.
For installations in multi-domain environments, where you want to create the PST Enterprise service account and security group in a domain other than the PST Enterprise server, see How to Create a Service Account and Security Group in a Multi-Domain Infrastructure During Installation.
PST Enterprise uses the following ports for communication:
- TCP port 80 (HTTP)
- TCP port 389 (LDAP)
- TCP port 443 (HTTPS)
- TCP ports in the range 1024 to 5000 (SQL client)
- TCP port 1433 (SQL server)
Typically these ports are already open on a corporate firewall. Barracuda holds no responsibility for opening additional firewall ports. If in doubt consult your local firewall administrator for further advice who can review the local firewall logs to see if any traffic over specific firewall ports is blocked and act accordingly.
Continue to Step 2 - Install Barracuda PST Enterprise