An Interesting thing that we are going to setup Office Web Apps 2013 for SharePoint 2013. as you know Office Web apps provides the capabilities of rendering, Opening, and rich editing of Microsoft office document formats such as Word, PowerPoint, Excel and One Note. By having Office web apps it just simplifies the rendering and editing of documents which are stored in SharePoint through Client browser therefore it’s not mandatory to have office client on client PCs.
Before we begin, make sure that you have an isolated server for Office web apps as 2013 version doesn’t support to install in a server running SharePoint and it has to be an isolated server.
Low Hardware (Such as Memory/Number of Processor Cores Minimum is two) can Cause interruptions on rendering and other Web apps Activities. So make sure that you have allocated better sized hardware based on number of concurrent users who will use web apps when you perform Production Deployments. This server I’m installing is just in a test lab which has 2 Gb of memory which is good enough for testing purpose.
Unlike Web Apps 2010, You cannot Experience the web apps 2013 functionality with the System Account as it’s not supported. you must always use another account for web apps testing.
So Let’s Do this. As usual first to Install prerequisites.
For Windows Server 2008 R2
Windows Server 2008 R2 SP 1 – http://go.microsoft.com/fwlink/p/?LinkId=252370
.Net Framework 4.5 http://go.microsoft.com/fwlink/p/?LinkId=256560
Windows PowerShell 3.0 http://go.microsoft.com/fwlink/p/?LinkID=244693
Then Open up PowerShell as administrator, paste this portion and run
Give it a moment
You need to restart your server once you got above screen.
For Windows Server 2012/R2
Simply run below line by opening up powershell as administrator. And you are done on prerequisites installation.
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, InkAndHandwritingServices, Web-Net-Ext45, Web-Asp-Net45
Install Web Apps Server
Go ahead in Web Apps server, launch the Setup from your media.
Accept the License Agreement and hit "Continue"
Choose the path that you want to locate the program. And install
Woof ! Error.
As I stated above, you will get an error saying that ‘Microsoft Office Web apps Server 2013 encountered an error during setup" if your Server having only one Processor Core. Same thing happened to me and allocating two Virtual Processors for my Web Apps VM fixed the problem.
This will take only few Minutes. A Coffee Time !
If everything went well you will get below Screen.
Alright we got the product installed now. Let’s move ahead with configurations. First in Web Apps Server.
Customize below lines according to your environment and run it on PowerShell. To Pass the SSLOffloaded parameter is additional if requires for HTTPS Scenarios.
For me it’s just HTTP
New-OfficeWebAppsFarm –InternalURL "http://APP3.northwind.int" –AllowHttp -EditingEnabled
Since we need to enable editing, Key in "Y" and hit enter to proceed.
To Register our domain run the below line (we are still in Web Apps Server)
New-OfficeWebAppsHost -Domain northwind.int
Try to access the Discovery URL from web Apps Server – http://Servername.domain.int/hosting/discovery (
It should open up below page for you.
With that we are completing of Web Apps Server. Now let’s move to SharePoint Server Side.
Configuring a SharePoint 2013 Farm for Office Web Apps
Log in to the SharePoint application server that hosts Central Administration and open the SharePoint 2013 Management Shell as an administrator. Next, enter the following line:
New-SPWOPIBinding -ServerName “Your Web Apps ServerName” -AllowHTTP
New-SPWOPIBinding -ServerName “app3.northwind.int” -AllowHTTP
It will Result as below
Now to Set the Zone Execute – Set-SPWopiZone –zone “internal-http” from SharePoint Server Shell
If you are using HTTP, you need to allow OAuth over HTTP by using the following commands:
$config = (get-spsecuritytokenserviceconfig)
$config.allowoauthoverhttp = $true
That’s all on the configurations. let’s upload document to a library and test the functionality.
if you are getting below error, refer to my previous post here which describes the resolution.