To configure SharePoint 2013 to use Office Web Apps Server, you must run one or more Windows PowerShell cmdlets from SharePoint 2013. After you run the necessary cmdlets, users can open Office files from SharePoint 2013 document libraries in a browser.

  • Verify that all SharePoint 2013 web applications use claims-based authentication. Office Web Apps rendering and editing will not work on SharePoint 2013 web applications that use classic mode authentication.
  • To enable users to edit (not just read) Office documents in a web browser, verify that you have the necessary editing licenses and that you have enabled editing on the Office Web Apps Server farm.
  • If you log into SharePoint 2013 by using the System Account, you will be unable to test the connection between SharePoint 2013 and Office Web Apps Server. You will have to log on by using a different account to test the connection.
  • Low memory conditions can cause Office document previews to fail in Office Web Apps. Verify that the server or servers that run Office Web Apps Server have sufficient memory by reviewing the Hardware requirements—web servers, application servers, and single server installations for SharePoint 2013, which are the same requirements that Office Web Apps Server uses.

Configure SharePoint 2013 to use Office Web Apps Server in a test environment that uses HTTP

Step1: Open the SharePoint 2013 Management Shell.
1.On the Start menu, select All Programs.
2.Select Microsoft SharePoint 2013 Products.
3.Choose (right-click) SharePoint 2013 Management Shell to display the short-cut menu.
4.From the short-cut menu, choose Run as administrator.

Step2: Create the binding between SharePoint 2013 and Office Web Apps Server
Type [ New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP ]
e.g: WacServerName (Office Web Server Name).
After you run this command, you should see a list of bindings displayed at the Windows PowerShell command prompt.

Step3: View the WOPI zones for the SharePoint bindings
Type [ Get-SPWOPIZone ]
After you run this command, you should see the WOPI zone displayed. It should be internal-https.

Step4: Change the WOPI zone to internal-http
If the result from Step 3 was internal-https, run the following command to change the zone to internal-http. You must make this change because the zone of SharePoint 2013 must match the zone of the Office Web Apps Server farm.
Type [ Set-SPWOPIZone –zone “internal-http” ]
Verify that the new zone is internal-http by running the following command:
Get-SPWOPIZone ]

Step5: Change the AllowOAuthOverHttp setting in SharePoint 2013 to True
To use Office Web Apps withSharePoint 2013 over HTTP in a test environment, you must set AllowOAuthOverHttp to True. Otherwise Office Web Apps will not work. You can check the current status by running the following example:
Type [ (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp ]
If this command returns False, run the following commands to set this to True.
Type [ $config = (Get-SPSecurityTokenServiceConfig) ]
Type [ $config.AllowOAuthOverHttp = $true ]
Type [ $config.Update() ]
Run the following command again to verify that the AllowOAuthOverHttp setting is now set to True.
Type [ (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp ]

Now Test your Browser Opening Office File in Browser…

Suggested Posts:

Leave a Reply