Buenos tardes hermanos (Yeah, we are all sad that Brazil won the game last night playing at the Bombonera!)
In Today’s post we going over the last step of the Office Web Apps Server which is the integration with Exchange Server 2013 (we will work on the integration with other products down the road as well).
Integrating with Exchange Server 2013
It’s a piece of cake and we configure the integration using the same URL that we used yesterday to test the Office Web Apps Server. The following cmdlet can be used (where <server-name> should be the same name assigned to the certificate).
Set-OrganizationalConfig –WACDiscoveryEndPoint /hosting/Discovery”>https://<server-name>/hosting/Discovery
We need to enable OWA WebReady and we can do that using either PowerShell or EAC. In this post we are going to use EAC and it all depends if you have a single Outlook Web App Policy or a bunch of them. If you have just one just double click on the Default one and change it however if you have several you can go on each one of them and change as you want to.
In order to configure the Outlook Web Policy, open EAC, then click on Permissions and then on the last item on the right side which is Outlook Web App Policies and edit the desired entry. Click on File Access item on the left and you can enable WebReady for either Public or Private computer. We can also force the users to use WebReady before downloading the file by clicking on Force WebReady Document Viewing when a converter is available. Click on Save.
Now on any message that has a Microsoft Office file supported by Office Web Apps Server, click on Preview
Here you go, the file will be displayed in the new Microsoft World Web App, as shown in the figure below.
It’s that simple!