With the coming version of Office server products, Microsoft has split Office Web Application, used to render Office document in a web browser, from SharePoint.

This means Office Web Apps can now be used by other server products, such as Lync 2013 or Exchange 2013.

in this post, we will see how to configure Exchange 203 to use Office Web Apps to render attachment (apply only to Office document; PDF files will continue to be render with WebReady).

Also, RMS document won’t be render using Office Web Apps.

NOTE WebReady is still present and can still be used to render attachment in a web browser. This is the default option.

Prerequisites

  • Exchange 2013
  • Office Web Apps 2013

I won’t go deeper on the deployment operations; you can read my previous post for Office Web Apps deployment (http://blog.hametbenoit.info/Lists/Posts/Post.aspx?ID=392)

Configure Exchange to use Office Web Apps

  • From an Exchange 2013 server, open the Exchange Management Console (EMS)
  • Type the command get-owavirtualdirectory | fl name,identity to get the OWA virtual directory identity
  • Type the command Set-OrganizationConfig –WACDiscoveryEndPoint http://<wac server>/hosting/discovery ; such as http://wacserver/hosting/discovery

image

    • to check if the setting has been set correctly you can use the command Get-OrganizationConfig | Format-List WACDiscoveryEndPoint, as result you should have something like WACDiscoveryEndpoint : http://<your WAC server>/hosting/discovery

image

  • Then type set-owavirtualdirectory -WacViewingOnPublicComputersEnabled $true -WacViewingOnPrivateComputersEnabled $true –identity <OWA virtual directory identity>

This command enable the use of Office Web Apps on both private and public computers; off course, if you want to enable it only to one type, use the related parameter only

    • to check if the setting has been set correctly, use the command Get-OwaVirtualDirectory "<OWA virtual directory identity" | Format-List Name,WacViewing*, as result you should have something like
    • Name                                   : owa (Default Web Site)
      Identity                               : <Exchange 2013 CAS server>\owa (Default Web Site)
      WacViewingOnPublicComputersEnabled     : True
      WacViewingOnPrivateComputersEnabled    : True
      ForceWacViewingFirstOnPublicComputers  : True
      ForceWacViewingFirstOnPrivateComputers : True

image

  • You also have the option to force Office Web Apps rendering before downloading the attachments using the command set-owavirtualdirectory -ForceWacViewingFirstOnPublicComputers $true -ForceWacViewingFirstOnPrivateComputers $true –identity <OWA virtual directory identity>

Et voilà, your Exchange server has been configured to use Office Web Apps to render attachment with a browser.