Post Update: If you are installing Office Web Apps 2013 RTM on Windows 2012 follow the instruction here http://wellytonian.com/2012/10/office-web-apps-2013-rtm/

This one gave me a few sleepless nights. I was getting a lot of errors when trying to get this to work. But due to the wider SharePoint community and lot of digging around, I was able to finally nail it and would like to share how to get Office Web Apps working with SharePoint 2013 (Public Beta).

Prerequisites

Anyways let’s get into it.

Preparing the Office Web Apps Server

Install all the pre-requisite software listed above.

Run the following script to enable all the required roles within the Office Web Apps Server

1
2
3
##Turning on Features for Office Web Apps = Win 2k8R2
Import-Module ServerManager
Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,Web-Security,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Console,Ink-Handwriting,IH-Ink-Support

Restart the server.
Run the office Web Apps Installer and accept all the default values.
Restart the server.
Next run the following script to register your server as an Office Web Apps Server

1
2
3
4
5
6
7
8
9
10
11
12
13
##Office Web Apps Registration Script

Import-Module OfficeWebApps

$domainID = [System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain()

$domainName=$domainID.name

$Domain=$domainName

$OffWebAppServer="$env:COMPUTERNAME"

New-OfficeWebAppsFarm –InternalURL http://$OffWebAppServer –AllowHttp –EditingEnabled

To get more bang for the buck you can also go down this path

1
New-OfficeWebAppsFarm -Verbose -InternalURL http://<machinename> -ExternalUrl http://<fully.qualified.machine.name> -AllowHttp -ClipartEnabled –TranslationEnabled

From the above script it is clear that I would be enabling HTTP instead of HTTPS. For scenarios of deployment wherein you would be using Office Web Apps to be externally utilized , the recommendation would be to go down the path of HTTPS. The following procedure would need to be followed for the same:

Create an SSL certificate that will be used with the fully qualified domain name of the server; make note of the friendly name you use when you create the certificate. You should use IIS to request the certificate to ensure that it gets created in the correct certificate store.

Provision the WAC farm with this PowerShell command:

1
New-OfficeWebAppsFarm -Verbose -InternalUrl https://<machinename> -ExternalUrl https://<fully.qualified.machine.name> -CertificateName <FriendlyNameOfCertificateFromPreviousStep> -ClipartEnabled –TranslationEnable

For the sake of testing, I went down the HTTP path for obvious reasons. Ran out of coffee.

RESTART THE SERVER.

This pretty much completes all the requirements on the Office Web Apps Server.

SharePoint 2013 Server integration

Run the following script to connect your SharePoint 2013 server to Office Web Apps

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
##Connecting SharePoint Farm to Office Web App Server

Add-PsSnapin Microsoft.SharePoint.PowerShell

##Variables

$OffWebAppSrv="NAME_OFYOUR_OFFWEBAPP_SERVER"

#####DO Not Edit Below this line

"Connecting to $OffWebAppSrv"

New-SPWOPIBinding -ServerName $OffWebAppSrv -AllowHTTP

"Setting Zone"

Set-SPWopiZone internal-http

"Script Completed"

Web Application

SharePoint 2013 is all about Claims and you better have your AD, ADFS guys on your speed dial from now on.

For the web application, I have got the following working within my environment

  • ADFS 2.0 running on Windows 2008 R2 Domain Level.
  • Web Application created using Claims Based Provider.

That’s pretty much it. You should be running to the banks with your Office Web Apps Deployment any time now J

Action Screenshots J

Have fun J