contentACCESS documentation – version 3.0

  1. Introduction to contentACCESS
    1. Services provided by contentACCESS
    2. Software requirements
  2. Installation of contentACCESS
  3. contentACCESS Tools
    1. Installing Virtual drive
    2. Installing the Proxy server (contentACCESSWS)
    3. Installing the Proxy web services
    4. Installing Outlook forms
    5. Legacy email archive connectors
    6. Legacy archive connector for Metalogix Archive Manager Exchange Edition (MAM EE)
    7. Legacy archive connector for Email Lifecycle Manager (ELM)
    8. Installing TECH-ARROW’s WinShortcutter
  4. contentACCESS Central Administration
    1. Central administration login
    2. contentACCESS Central Administration user interface
  5. Tenants in contentACCESS
    1. How to create a new tenant
    2. Tenant limitations
    3. How to provide access to a tenant (adding new tenant administrators)
    4. Tenant administrator invitation types
  6. General system configurations
    1. Connection
    2. User interface
    3. Users — role types, creating new users, adding user logins
    4. How to activate your license key
    5. How to create user logins to an already existing user?
    6. System administrators
    7. Login providers
      1. External login provider configuration
      2. Associating an enabled provider with a user login
      3. contentACCESS users in third party systems
    8. System
    9. Licensing
    10. Notifications
    11. Monitoring — how to find out possible misconfigurations / reasons of potential system/job failures
    12. Distributed environment in contentACCESS — Clusters
    13. Statistics
    14. How to create/configure databases — All databases
  7. Common features
    1. Databases
    2. Schedules
    3. Retentions
    4. Storages
    5. Exchange connections
    6. Importing contentACCESS configurations from files
      1. Manual import of Exchange servers/groups/mailboxes to the contentACCESS Address book
      2. Importing File Archive root folders to be archived
  8. Creating new jobs in contentACCESS
  9. Jobs’ page, jobs’ context menu
  10. File Archive
    1. Introduction to File system archive
    2. File Archive settings
    3. Databases
    4. System settings
    5. Retentions
    6. Storages
    7. Root folders
    8. Aliases
    9. Schedules
    10. Provisioning settings and managing access to contentWEB
    11. Configuring aliases
    12. Configuration of jobs available in contentACCESS File Archive
    13. Configuration of File system archive job
    14. Configuration of a File system restore job
    15. Configuration of File system recovery job
    16. Configuration of Remote shortcutting job
    17. Active/inactive documents in File system archive
  11. Email Archive
    1. Important settings before creating an Email Archive job
    2. Database settings
    3. System settings
    4. Provisioning settings
    5. Retention settings
    6. Shortcuts in email archiving
    7. Storing of archived emails
    8. Creating email archive schedulers
    9. User experience
    10. Exchange 2013+: Mail app in OWA 2013+ or on MS Outlook 2013+ desktop version
      1. Deployment in contentACCESS Central Administration
      2. How Mail app works in MS Outlook 2013+ and OWA 2013+
    11. Exchange 2010: OWA 2010 integration
    12. Address book objects
    13. Granting access rights for mailbox users and explicit users to view the mailbox archive?
    14. Creating contentWEB users (option 1)
    15. Manage access to a mailbox archive (option 2)
    16. How the end user logs in to contentWEB (archive)
    17. Database and store assignment in email archiving
    18. How to assign database and storage to an Exchange group?
    19. How to assign database and storage to a mailbox?
    20. How to move data from source database/storage into a second (target) database/storage?
    21. Creating Email archive jobs: archive, restore, recovery, mailbox move, shortcut synchronizaion
    22. Email archive job
      1. Email archive job configuration
    23. Email restore job
      1. Email restore job configuration
    24. Email recovery job
      1. Email recovery job configuration
    25. Mailbox move job
      1. Mailbox move job configration
    26. Shortcut synchronization job
      1. Shortcut synchronization job configuration
  12. Custom plugins
  13. Email management job configuration
  14. SharePoint archive plugin
  15. Storage replication plugin
  16. Sharing plugin
  17. Datengut plugin
  18. Email synchronizer plugin
  19. contentWEB
    1. Logging in to contentWEB
  20. officeGATE
  21. accessGATE Mobile
  22. Virtual drive
  23. Terms of use
  24. FAQ

7.5.Exchange connections

During the configuration of Exchange-based jobs it is obligatory to set the Exchange server connections, where the mailbox to be crawled is located. The Exchange connections can be configured:

  • By email based custom job instances with navigating to Custom plugins ⇒ General group Documentation197 Exchange connections button.


    Here select option + new and insert necessary data into the Exchange connection repository window. By the custom plugins it is possible to configure multiple Exchange connections.

  • By Email Archive jobs with navigating to Email Archive ⇒ Settings ⇒ System settings, under EWS settings section. In Email Archive only single (either Exchange online O365 or On-premise) Exchange connection can be configured.


    If you are configuring EWS connection to custom plugins, a Connection name must be also entered into the Exchange connection repository dialog. Under Exchange server type and Exchange server version select the type and version of the server, which is used by your email provider. Then enter the EWS URL, PowerShell URL and the PowerShell authentication into the dialog. These data must be requested from the email provider. Under Max. connection count option the user may define, how many parallel connections will be maintained by the system when connecting to PowerShell. It is also possible to disregard any SSL errors with checking the Ignore SSL errors checkbox.

    Keep connection alive: If it is turned on, then the connection between contentACCESS and the Exchange server is cached, which increases the performance. If the Exchange is load balanced, some requests can land on another Exchange which causes errors in contentACCESS. In these cases unchecking the keep alive option will destroy the connection after each request and will rebuild it on the next request. The recommended settings of “keep alive” option are as follows:

    • If you are communicating with one Exchange server: turn it on to increase the performance
    • If you have a load balanced Exchange environment and there are communication problems with the Exchange: it is recommended to turn it off

    If you want to use an explicit user for exchange connection, check Use explicit credentials and enter the User name and Password. It is also possible to log in under service-credentials. It this case the Use explicit credentials option must be unchecked. Run a test connection via Test button. Do not forget to save the changes.


    Exchange connection configurations for custom plugin type.


    Exchange connection configuration for Email Archive plugins.

    Important!!! The user set under Exchange connections must have a full access to the mailbox(es) that he/she would like to archive. Provisioning job requires to have “View-Only Organization Management” right on the Exchange. “Org Custom Apps” must be assigned for the EWS user on the Email Archive System settings page, in section EWS settings, if Mail app will be also used. This role enables an administrator to install and manage custom apps for the organization (read more about the role here).

    Note: To speed up the email archiving processes, TECH-ARROW has implemented MAPI protocol for communication with the Exchange server. MAPI can be used only in case that the customer has an on premise Exchange server (Exchange 2013 or earlier), and uses contentACCESS with Email archive licence (by custom plugins MAPI cannot be selected). MAPI can be selected on the email archive /restore/recovery job’s configuration page only. By default, contentACCESS uses EWS settings to connect to the Exchange. Some functionalities still require EWS settings. From this reason it is a must to configure EWS settings as well.

    Exchange performance settings – turning off the Exchange throttling policies

    Throttling is a mechanism of Exchange Server to distribute the Exchange resources evenly between the users. It gives every user the chance to access their emails. The users are limited for example to send max 5 emails in a minute. If this limit is reached, the user is throttled, forcing the user to wait a minute until a new mail can be sent.

    The archiving user requires more resources: it needs to access multiple mailboxes, process multiple messages. The standard throttling policy is not suitable for the archiving user (superuser).

    If you are experiencing problems that may be caused by these policies, you can turn them off. The commands below are turning off any limitations for the archiving user, allowing to use as many Exchange resources as needed.

    Exchange 2013

    New-ThrottlingPolicy -Name CAPolicy -ThrottlingPolicyScope Organization

    Set-ThrottlingPolicy CAPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited - EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited

    Set-Mailbox "Administrator" -ThrottlingPolicy CAPolicy

    Exchange 2010

    New-ThrottlingPolicy -Name CAPolicy

    Set-ThrottlingPolicy CAPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null -CPAMaxConcurrency $null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null -CPUStartPercent $null

    Set-Mailbox "Administrator" -ThrottlingPolicy CAPolicy

    There are 3 commands which must be run in PowerShell to apply the throttling for the superuser:

    #1 New-ThrottlingPolicy
    Creates a new policy, gives a name to the policy. It is created with default values.

    #2 Set-ThrottlingPolicy
    This changes the parameters of the policy – turning off any throttling for the contentACCESS user.

    This list should be discussed with the customer, they might not allow all these options. This is a matter of support.

    #3 Set-Mailbox
    Assign the policy to the user.

    The whole association can be verified by running this command: Get-Mailbox “Administrator” | fl ThrottlingPolicy

Yes No Suggest edit
Help Guide Powered by Documentor
Suggest Edit