«

»

Nov 26

Installing Office Web Apps For SharePoint 2013 – Part 1

With the introduction of SharePoint 2013 comes a new way of setting up Office Web Apps. With SharePoint 2010 imageyou installed Office Web Apps onto the web front ends for your server farm, with SharePoint 2013 Office Web Apps is a completely separate server and so needs to be installed on a server that is not running SharePoint 2013.

If you read the posts on Installing Workflow Manager for SharePoint 2013 you will know that in my farm I have that running on a separate server and this is the server that I also run Office Web Apps from as well.

Installation

Once you have downloaded the setup file from the link above installation is a simple process of running the setup file from the .img file.

image

Note

There are list of pre-requisites that need to be installed before running the installer for Office Web Apps, the easiest way to install them all is with a PowerShell script, the one below works for Windows Server 2012

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

Configuration

While setup is simple, configuration on the other hand is not.

As with the Workflow Manager, configuration is governed by what you want to do with Office Web Apps which are based on two real factors

Do you want internal use only or internal & External use of Office Web Apps

The following steps are going to explain how to create a single server farm using HTTPS. Using HTTPS allows for external use and is recommended for production environments, HTTP can be used but only allows for internal use.

Certificates

As I am going to use HTTPS I need to get a certificate from a trusted SSL source, in this case my onPrem domain certificate authority.

To get the certificate I just requested a domain certificate using IIS

image

Create Server Farm

Once the certificate is in place I need to create the server farm, to do this run the following PowerShell command

New-OfficeWebAppsFarm -InternalUrl https://yourserver.local -ExternalUrl https://webapp.yourdomain.com –CertificateName "OfficeWebApps Certificate" -EditingEnabled

The certificate name is the friendly name for the certificate you created using IIS and the EditingEnabled allows documents opened with Office Web Apps to be edited, the default is view only, assuming you have licensing for editing which I will cover in another post.

You only need the editing enabled if you are using Office Web Apps with SharePoint 2013. You can also use Office Web Apps with Exchange 2013 and Lync 2013 but they both only support view only not editing.

Verify Server Farm

Once the server farm has been created its always a good idea to verify it works. To do this navigate to the following web page

https://yourserver.local/hosting/discovery

If all is working then you should see an xml page in your web browser that looks something similar to this

image

So that’s Office Web Apps all installed the next post will explain how to configure SharePoint 2013 to use Office Web Apps and take a look at the licensing for editing using Office Web Apps.

4 pings

  1. Installing Office Web Apps For SharePoint 2013 – Part 2 » Edutech Now

    [...] « Installing Office Web Apps For SharePoint 2013 – Part 1 [...]

  2. Installing Office Web Apps For SharePoint 2013 – Part 2 » Edutech Now

    [...] « Installing Office Web Apps For SharePoint 2013 – Part 1 [...]

  3. What’s New in Office Web Apps 2013 « Nik Patel's SharePoint World

    [...] Installing Office Web Apps for SharePoint 2013 – Part I – http://www.edutechnow.com/?p=1903 [...]

  4. What’s New in Office Web Apps 2013 « Nik Patel's SharePoint World

    [...] Installing Office Web Apps for SharePoint 2013 – Part I – http://www.edutechnow.com/?p=1903 [...]

Leave a Reply