EV 10.0.3 Feature Briefing Exchange Server 2013 OWA Support This document is one of a set of Feature Briefings which detail major new or changed features in Enterprise Vault 10. This document covers the support for OWA on Exchange Server 2013. If you have any feedback or questions about this document please email them to IIG-TFE@symantec.com stating the document title. This document is provided for informational purposes only. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice. Copyright 2013 Symantec Corporation. All rights reserved. Symantec, the Symantec logo and NetBackup are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
Feature Description Microsoft released Exchange Server 2013 in late 2012. OWA for Exchange Server 2013 has been completely changed compared to Exchange 2010. These changes required the development of new Enterprise Vault OWA extensions for Exchange Server 2013. The new extensions are included with Enterprise Vault 10.0.3. Exchange Server 2013 OWA has been rewritten to make greater use of JavaScript rendering on the client and has introduced Office Mail Apps as a way of extending web apps and Office 2013. Enterprise Vault 10.0.3 has been designed to work with Office Mail Apps for Exchange Server 2013. Underlying Principles Enterprise Vault integrates with Exchange Server 2013 OWA as an Office Mail App. Office Mail Apps appear in the mail clients based on the combination of the current item that is selected and the activation rules of the installed Office Mail App. Figure 1 illustrates Office Mail Apps (in the lower right corner). Figure 1 - Office Mail Apps in OWA Page 1
Deployment of the Enterprise Vault Office Mail App can be made available to the whole organization or for an individual mailbox. The App is designed to allow deployment at the organizational level, but the preferred method of deployment is to each individual mailbox. See the Test Drive section for more information on deployment methods. When the Office Mail App is deployed to a user, it can be configured to appear in desktop applications (Outlook 2013 and OWA 2013), tablet devices, and mobile devices 1. The Enterprise Vault Office Mail App will only be visible when the user clicks on a mail or calendar item. The only exception to this is when a user clicks on an item in Virtual Vault within Outlook. Table 1 details the user actions available in the Enterprise Vault Office Mail App when displayed in various different contexts. Due to browser compatibility issues: 1) The Archive Explorer button will be absent if the browser in use is not Internet Explorer. 2) If the policy for the search button is to use integrated search (the simple EV search page traditionally offered inside Outlook by the EV Outlook Add-in) then the search button will be absent if the browser in use is not Internet Explorer. Type of Item Selected by User Archive Explorer EV Search View Original Manual Archive Manual Restore from Archive Delete from Archive Cancel Non Archived Item Shortcut Item Pending Archive Pending Restore Pending Delete Original Content opened from the EV Office Mail App Original Content opened by EV Outlook Add-In Table 1 - Enterprise Vault Office Mail App Options Help 1 Tablet and mobile devices will not be supported in the initial Enterprise Vault Office Mail App. A message will be displayed when the App is used on an unsupported device. Page 2
Note: Cancel has two uses: 1. It can stop the current active manual operation that was directly initiated by the user. These manual operations will normally have associated user progress feedback and will progress through various states until the operation is complete. When used like this, cancel will interrupt the current flow if that is possible, and reset the UI appropriately. The message class of the item may be restored if that is appropriate. 2. It can be used on an item that has been put into the archive pending state by the EV server. User options for the Enterprise Vault Office Mail App will be controlled by the Desktop policy. Users will have the same functionality as with previous versions of OWA. Figure 2 shows the options available for an item that has not been archived. Figure 2 - Non-Archived item Figure 3 and Figure 4 show the options when a user selects an item to be manually archived. Figure 3 Selecting Retention Category Figure 4 - After Retention Category has been selected Figure 5, Figure 6, and Figure 7 show the options available to the user on an archived item. Figure 5 illustrates that the user has clicked on the View button and the item is being retrieved from Enterprise Vault. Figure 6 shows an archived item being restored back to the mailbox. Figure 7 shows a user deleting an archived item. Page 3
Figure 5 - Viewing an item (when View has been clicked) Figure 6 - Archived item being restored Figure 7 - Clicking on the Delete button Figure 8 shows the options available to the user when an item is in an archive pending state. The user can cancel the operation by clicking on Cancel. Figure 8 - Pending archive item options Figure 9 shows that the user has not been enabled for archiving. Keep in mind that the Enterprise Vault Office Mail App can be deployed at the organizational level and to individual mailboxes. A user does not have to be enabled for archiving for the App to show up. Figure 9 - Mailbox not enabled for archiving Page 4
Test Drive Office Mail Apps can be installed at the organizational level or into individual mailboxes. At the organizational level the App is installed once and is available to all users. This deployment method does not completely fit with normal Enterprise Vault provisioning methods as users will be able to see the Enterprise Vault Office Mail App even if they are not enabled for archiving. Reasons for deploying the EV Office Mail App at the organization level: Simple deployment using a single PowerShell command No need to integrate Mail App deployment into existing user provisioning scripts Reasons for deploying the EV Office Mail App at the mailbox level: Only those users who have been enabled for Enterprise Vault will see the App Simple deployment using a PowerShell command Customized URLs can be used to ensure that the App is loaded from the appropriate EV server. Particularly important where more than one EV deployment is archiving different sets of users from the same Exchange server. The Exchange Server 2013 management UI is completely web based and only supports the configuration of organizational Apps by the administrator. It is not be possible for the administrator to use the UI to see if an individual user has the EV Office Mail App at the mailbox level. There are a set of PowerShell command-lets that can be used to manage Office Mail Apps which provide much greater information about installed Apps and control over them: Get-App New-App Remove-App Set-App Enable-App Disable-App The recommended method of deployment of the Enterprise Vault Office Mail App will be via PowerShell. The following is an example of how the Enterprise Vault administrator would deploy the App to an individual mailbox using PowerShell: Page 5
get-mailbox -identity [user] # For each user ForEach-Object { $legacymbxdn = $_.LegacyExchangeDN; # Install Enterprise Vault Office App $url="http://[evserver]/enterprisevault/officemailappmanifest.aspx?legacymbxdn =" + $legacymbxdn; $webclient = new-object Net.Webclient $webclient.usedefaultcredentials = $true $bytes = $webclient.downloaddata($url) new-app -mailbox $legacymbxdn -filedata $bytes } A new advanced section will be available in the Exchange Desktop Policy named Office Mail App. Table 2 shows the different options available. The existing OWA advanced section in the Exchange Desktop policy will be renamed to OWA versions before 2013. Setting Possible Values Default Availability OWA 2013 only, Outlook 2013 only, OWA and Outlook 2013 OWA 2013 and Outlook 2013 Mode Light, Full Light Behavior of Mail App Bar Search Application Show Options, Open immediately and show options Browser Search, Integrated Search (IE only) Show Options Browser Search Table 2 - Desktop Policy Advanced Settings for the EV Office Mail App Licensing and support considerations OWA functionality for Exchange Server 2013 is available when the Enterprise Vault environment is properly licensed for Exchange archiving. The EV Office Mail App can only be supported in Outlook 2013 and OWA2013 (when connecting to an Exchange Server 2013 mailbox) as it relies on the introduction of the Apps for Office feature that Microsoft introduced in these products. Although Office Mail Apps do support mobile and tablet devices, Enterprise Vault 10.0.3 will not support these devices. Support is planned for a future release of Enterprise Vault. Page 6
Due to Microsoft constraints, the EV Office Mail App will be limited to: Premium OWA clients only and will not be visible in the Basic OWA client. Normal Mail messages and Appointments. Individual items only. Multi item functionality cannot be archived with an Office Mail App. Support only IE9 and above (although it may work it is unsupported on other HTML5 compatible browsers) Not supported for items in Public Folders. Microsoft does not support Public Folders in OWA with the initial Exchange Server 2013 release. Page 7
About Symantec: Symantec is a global leader in providing storage, security and systems management solutions to help consumers and organizations secure and manage their information-driven world. Our software and services protect against more risks at more points, more completely and efficiently, enabling confidence wherever information is used or stored. For specific country offices and contact numbers, please visit our Web site: www.symantec.com Symantec Corporation World Headquarters 350 Ellis Street Mountain View, CA 94043 USA +1 (650) 527 8000 +1 (800) 721 3934 Copyright 2013 Symantec Corporation. All rights reserved. Symantec and the Symantec logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.