To install OWA 2010 Extension:
1.Find the Disc \ Metalogix \ Archive Manager Installation Package \ 64bit Extension \ 64bit Extensions Setup.exe.
2.Run it on the Exchange 2010 Server with the CAS role.
3.To continue read and accept the license agreement.
4.The install folder is by default set to C:\ Program Files \ Metalogix.
NOTE: It is a 64-bit application, so the 64-bit Program Files folder is selected as default. In case of custom folder, the full path will always be Metalogix\MAM4Exchange.
5.Select the OWA 2010 Extension option in the Select Features dialog. Exchange Server Tools option is checked automatically. Click Next.
6.In the background the setup checks if all pre-requisites are installed. If not, the error message is displayed and the setup aborts.
7.In the next dialog enter your Archive Manager Archive server in the text box. You can use the Browse button to locate the relevant server. To verify the connection to the Archive server click Test server button. Click Next.
8.When asked to specify a user, enter the super-user credentials (DOMAIN\UserName and password). Superuser is the user under which Archive Manager is running. It was specified during the installation of Archive Manager.
NOTE: Super-user must be local admin on your MS Exchange server.
9.Next you may be asked to allow Archive Manager for Exchange 64bit Extensions service to be added to the Exception list of the Windows Firewall. In this way the Archive service will be allowed to communicate through Windows Firewall. Click Next.
10.Finally click Install and then Finish.
The setup continues with the Archive Manager OWA extension configuration:
1.If not started, you can launch the OWAInstaller2010.exe located under C:\Program Files \ Metalogix \ MAM4Exchange \ Tools \ OWA.
2.Select the Install/repair option and then click Next.
3.On the next screen you will see the installation path displayed. If the path is not correct, click Change to locate the Archive Manager installation folder.
Then click Next.
4.Now click the applicable radio button - Local MS Exchange or Office 365 based on your environment. Then specify relevant set.
If applicable, in the OWA Server Name URL text box enter the server name where OWA is installed.
In the OWA alias name URL text box you need to provide the URL used to access OWA from internet. If you are using multiple URLs to access OWA, please use the one which is accessible to most of the users.
IMPORTANT NOTE: When installing OWA extension for Office 365 environment, PUBLIC ALIAS has to be filled in here.
In the ExchangePamWS service text box enter the ExchangePamWS service URL, i.e. address where this service is installed on the Archive Server (it should be filled in automatically).
If applicable, in Exchange Web service URL text box enter the Exchange web service URL. The Exchange Web Service is a set of web services to access the mailboxes on Exchange Server. This webservice is normally installed on Exchange Servers with the CAS role, so in most cases you can use this url:
5.In the Credentials dialog fill in the credentials of your super-user under which Archive Manager is running. It was specified during the installation of the Archive Manager. Then click Next.
6.On this page, enter the name of your Archive Manager Archive Server machine in the Primary Archive Server text box. Should you have only one archive server, the same name can be written in the Secondary Archive Server text box, too. However, if you have more servers, fill in another Archive Manager server in this text box. The secondary server will be used if the primary is not available.
Enter the OWA cache path in the OWA cache folder path text box. By default, the cache folder is created under the Web folder. Use the Browse button to change the OWA cache path, if necessary.
8.When the installation and configuration was successful, click Finish.
NOTE: The new settings will not be applied immediately. Either you will have to wait until the system recognizes the changes (done approximately every hour) or you will have to reset the owa application pool: either by recycling the application pool or by resetting IIS. In the latter case connected users will be disconnected and will have to log on again.
When OWA 2010 Extension is installed and configured correctly, users can access and retrieve their archived emails via Outlook Web Access. The special icon let the user know that the email was archived ().
As default, attachments in the preview pane appear just as a link. When double-clicked, the archived email opens and attachments are also accessible. Note that some features available for non-archived emails are not available for archived ones.
When OWA extension is installed, users can archive, restore or delete emails in OWA (depending on what rights they are assigned in Enterprise Manager / Settings / Outlook Addin permissions).
To archive an email in OWA, right-click it and from the context menu select Archive. In the pop-up window select the Retention category under which you want to archive the email and click Archive.
By using the context menu, email that is already archived can be restored or mark for deletion in the archive.
Should you wish to delete an archived email, use the Archive Manager Delete context menu option. After clicking the Delete option from the context menu, a pop-up dialog appears. Check the Delete from archive check box. In this way the email will be deleted from the Exchange server and it will be marked for deletion in the archive. Consequently it will be deleted when the retention period expires.
By not selecting the Delete from archive check box the respective e-mail/shortcut will be deleted from the Exchange Server. However, it will not be marked for deletion in the HSM store. Such item is displayed as lost in the Enterprise Manager. It can be restored by the administrator during its retention period until the Shortcut synchronization job runs (see the Archive Manager for Exchange Administration Guide).
Metalogix makes every effort to perform comprehensive testing but cannot guarantee, due to environmental differences, that all functions will work in every environment. It is always recommended that testing be conducted within your own environment to confirm functionality and compatibility.