2.Configuration part for administrators
- Exchange 2013 or later version
- MS Outlook 2013 or later desktop version or OWA.
- Proxy installed over HTTPS connection.
- Default shortcut and a default retention must be set in contentACCESS Central Administration.
- On the System page (System tab => Services group => System button => External accessibility settings) a HTTPS alias must be configured.
- Roles Org Custom Apps, Org Marketplace Apps and User Options must be assigned for the EWS user on the Email archive System settings page in section EWS settings. These roles enable an administrator to install and manage custom apps for the organization (read more about the roles here).
If the user wants to use the contentACCESS MailApp in shared mailbox(es), the following is required:
- Office 1.8 API minimum. Supported Exchange and Outlook versions are described in this article (Supported API requirement sets column)
The following is NOT supported, therefore you won’t be able to use contentACCESS MailApp in these:
- Public folders
- Office365 group folders
The administrator is required to do the following configurations for manual email archiving. He has to
- configure a shortcut that contentACCESS MailApp will use and set this shortcut as default (refer to section Shortcuts in email archiving);
- configure a retention that contentACCESS MailApp will use and set this retention as default (refer to section Retentions);
- install the Proxy server with HTTPS connection;
- configure HTTPS based alias In Central Administration under System => Services => System => External accessibility settings;
- allow MailApp activation for selected mailboxes/groups/servers from Central Administration => Address book;
- run the Email archive Provisioning job to apply the changes.
To allow the MailApp activation, navigate to Email Archive ⇒ Archive ⇒ View address book on the ribbon.
In the column Enable mail app it is possible to see if the MailApp activation was allowed for the selected object (mailbox, group or server). By default, the objects inherit the MailApp activation from their parent, so if the parent has it set to allow/forbid, so will the child.
The MailApp activation can be set from the context menu of the selected object to:
- Inherit
- Explicitly allow
- Explicitly forbid.
If you selected Explicitly allow, the contentACCESS Portal user role pop-up will open. Here you need to specify the contentACCESS Portal user role (containing user permissions) to be assigned to the contentACCESS Portal user(s). It is possible to select a custom role from the dropdown list or you can use the role defined in the Email archive Provisioning job.
After the changes have been made, it is necessary to start the Provisioning job to apply them.
- https://[SERVERNAME]/contentACCESSWS/Mailapp/Mailapp.xml
- https://[SERVERNAME]/contentACCESSWS/Mailapp/Mailapp_no_ribbon_button.xml
The administrator should be able to browse the file using the links above without any issues.