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).
- Office Web Apps require a separate server / farm of servers based on your requirement.
- Currently tested on Windows 2008 R2 SP1
- PowerShell V3.0 – Download Link
- .net 4.5 – Download Link
- Few Hotfixes – http://www.microsoft.com/download/en/details.aspx?id=27928 , http://hotfixv4.microsoft.com/Windows 7/Windows Server2008 R2 SP1/sp2/Fix354400/7600/free/427087_intl_x64_zip.exe , http://hotfixv4.microsoft.com/Windows 7/Windows Server2008 R2 SP1/sp2/Fix368051/7600/free/433385_intl_x64_zip.exe
- ADFS 2.0
- Claims based Web Application
- Some coffee – try Flat white speciality of New Zealand … and Australia J
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
##Turning on Features for Office Web Apps = Win 2k8R2
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
##Office Web Apps Registration Script
$domainID = [System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain()
New-OfficeWebAppsFarm –InternalURL http://$OffWebAppServer –AllowHttp –EditingEnabled
To get more bang for the buck you can also go down this path
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:
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
##Connecting SharePoint Farm to Office Web App Server
#####DO Not Edit Below this line
"Connecting to $OffWebAppSrv"
New-SPWOPIBinding -ServerName $OffWebAppSrv -AllowHTTP
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