Deploying Office Web Apps Server with Exchange Server 2013 SP1

In the series of articles on deploying Exchange 2013SP1 (Part1, Part2, Part3, Part4, Part5) we went through setting up the two fault-tolerant multirole Exchange servers. Now I’d like to show you how to add an Office Web Apps Server to this Exchange organization – starting from Exchange 2013 we must use the separate server product to provide Exchange users with browser-based file viewing and editing services. Only MSDN subscribers are now eligible for downloading Office Web Apps Server.

In my testing environment the Office Web Apps server will be installed on the host named OffWeb, OS = Windwos Server 2012R2, ip = 20.1.1.3

First of all, some prerequisites must be met before we can proceed to installation (for Windows Server 2012R2):

1) Install .NET Framework 4.5.2
(can be downloaded here: https://www.microsoft.com/en-us/download/details.aspx?id=42642 )

2) Run these two commands in Windows PS as Administrator to install the required roles and services:

a)  Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices

b) Add-WindowsFeature NET-Framework-Features,NET-Framework-Core,NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-HTTP-Activation45 -source D:\sources\sxs

Please replace “D:” to whatever disk you’re using for your Window Server 2012R2 installation files.

Now I can run the Ofice Web Apps Server setup from the distribution iso-file:

W11 W12

The next step is to create the Office Web Serverserver farm, but again, before I proceed to creating a server farm I need to install a SSL certificate on my OffWeb machine as I’d like my Exchange users utilize SSL connections to Office Web Server:

W15 W16 W17W43W18 W19

W44

W42

I will uncheck ipv6 from OffWeb’s Nic settings as I’ve choosen to bind port 443 to 20.1.1.3 only:

W22

Now I can create an “SSL” farm: let’s run the following commands in the PS:

Import-Module -Name OfficeWebApps

New-OfficeWebAppsFarm -InternalUrl “https://OffWeb.TestCompany.com” -ExternalUrl “https://OffWeb.TestCompany.com” -CertificateName “OffWeb” -EditingEnabled

W25

To check the farm has been created successfully I open this page:

http://OffWeb.TestCompany.com/hosting/discovery

W30– that means the farm works properly.

The next step is to configure the Exchange server – in the Exchange PS we must run:

1) Set-OrganizationConfig -WACDiscoveryEndPoint https://OffWeb.TestCompany.com/hosting/discovery

2) Get-OrganizationConfig | Format-List WACDiscoveryEndPoint

W31-2

If you need more granular control over what users may or may not use web-based file browsing you would use these commands to allow/deny document viewing from public/private computers:

Set-OwaVirtualDirectory “Exch1\owa (Default Web Site)” -WacViewingOnPrivateComputersEnabled $true ($false)

Set-OwaVirtualDirectory “Exch1\owa (Default Web Site)” -WacViewingOnPublicComputersEnabled $true ($false)

It’s time to test Office Web Apps server capabilities in viewing – for example – docx attachments:

W32 W34

W36

As we can see a user can open a MS Office document (.docx) even when there’s no MS Office installed on a user’s PC (of course, MS Office is not installed on OffWeb either).

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: