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.

Barracuda PST Enterprise v5.1 Pre-Installation Package

  • Last updated on

This article refers to the Barracuda PST Enterprise version 5.1, and .Net Framework 4.5 or higher.

Verify your server meets the hardware and software requirements before installing PST Enterprise Pre-Installation Package. 

Pre-Installation

Run the pre-installation package PSTEnterprisePreInstall.exe on the server designated to host the PST Enterprise website. This process creates the PST Enterprise Admin user account, security group for PST Enterprise administrators and, if required, installs the database engine (SQL Express 2008 R2 instance). Note that you may be alerted to any prerequisites that are not installed.

During the installation process, you are prompted to provide the security group name and credentials for an account. Because the account and group may need to be created during the installation process, and because Exchange system permissions may need adjustment, you must log in as a domain user and have admin rights on these systems to complete the PST Enterprise Pre-Installation.

Download the Barracuda PST Enterprise Pre-Installation Package to your server, and follow the onscreen instructions.

Note that if you do not specify an AD Account or AD Group, Barracuda PST Enterprise creates them.

The PST Enterprise pre-installation process creates objects and grants appropriate permissions to allow smooth running of PST Enterprise, including:

Active Directory Account
  • If you do not specify an Active Directory (AD) account to act as the PST Enterprise service account, PST Enterprise creates one during pre-installation.
  • Account is granted owner rights on the PSTEnterprise database so that all required database tables are generated when the website starts up; there is no need to manually create tables.

  • Account is granted owner rights on all mailboxes in the Microsoft Exchange organization using the Pre-Installation PowerShell Command below.

  • Owner rights on all mailboxes allows the account to log in to any mailbox associated with an uncoupled PST when a PST Processor installation searches for uncoupled PSTs using the AD account.

  • During the pre-installation process, the AD account is granted rights over all Exchange mailboxes, using the Pre-Installation PowerShell Command below.

AD Pre-Installation PowerShell Command

During the pre-installation process, the AD Account is granted owner rights over all Microsoft Exchange mailboxes using the following PowerShell command:

Add-ADPermission -Identity "MyExchangeOrganization" -User
PSTEnterpriseAdmin -AccessRights
ReadProperty,GenericExecute,ExtendedRight -ExtendedRights
Receive-As,ms-Exch-Store-Visible,ms-Exch-Store-Admin
-InheritanceType All

Where MyExchangeOrganization is the name of the Exchange Organization and PSTEnterpriseAdmin is the name of the AD Account.

AD Group
  • If you do not specify an AD group, PST Enterprise creates one during pre-installation.
  • Users must be members of the AD group to log in to the PST Enterprise administrative website.
SQL Database Connection
  • If you do not specify database connection details, SQL Express is installed and used by default.
IIS Application Pool
  • IIS Application Pool used to run the PST Enterprise website uses the Integrated Pipeline mode.
  • IIS Application Pool process model identity is set to the specified AD account.

Run the Pre-Installation Package

Use the following steps to run the pre-installation package:

  1. Right-click PSTEnterprisePreInstall.exe, and click Run as administrator:
    PreInstall01.png
  2. The Wizard launches. In the Prerequisites page, verify the prerequisites are met; all tests must pass as True; correct any failures before proceeding using the Learn more about PST Enterprise Preinstallation tests link:
    Preinstall1.PNG 
  3. Click Next. In the Accounts page. By default, the Group Name is PSTEnterpriseUsers. If you created a security group, click Browse to navigate to and select the group from your Active Directory (AD), otherwise you can leave the default value or enter a new name to represent the PST Enterprise users security group.
    Preinstall2.PNG
  4. By default, the Account Name is PSTEnterpriseAdmin. If you created an account, click Browse to navigate to and select the account from your AD:
    Preinstall3.PNG 

    Otherwise you can leave the default value or enter a new name to represent the PST Enterprise Exchange account. 
  5. Click Next. In the SQL Server Configuration page, If an existing SQL Server instance is detected on the local server, the pre-install is complete; click Next and then Finish:
    Preinstall4.PNG
  6. If no local SQL Server instance is detected, you are prompted to install SQL Server. To install SQL Express 2008 R2 on the local server, click Install:
    Preinstall5.PNG

    If you plan to use a SQL Server on a remote server, it is not necessary to install it locally; simply click Next. The remote server configuration is completed during the main PST Enterprise Installation.

  7. Click Install. In the Local SQL Configuration page, by default the SQL Server installation path is set to C:\Program Files (x86)\Microsoft SQL Server. To change the folder path, click Browse and navigate to and select the new folder path:
    Preinstall6.PNG
  8. Click Install. Allow the SQL installation to complete; this may take several minutes to complete:
    PreInstall08.png
  9. Once the installation successfully completes, the confirmation dialog displays:
    PreInstall09.png
  10. Click OK to close the dialog. The Completion page displays:
    Preinstall8.PNG 
  11. Click Finish.

Deployments with Office 365

Once you have created the PST Enterprise Admin user account in local AD you should ensure this has synchronised to Office 365 before proceeding.

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 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')

Last updated on