So October has been pretty quiet around here, but I have some cool stuff to share with you today.

Office 2013 RTM'd some time ago and so did all the server products. So with SharePoint 2013 available on TechNet I decided to set up some demo sites to get a feel for the product, after looking for a new version of the Office Web Apps I realized that there was some change coming here.

Office Web Apps Server

Office 2013 Web Apps are no longer installed on SharePoint servers directly, it became a stand-alone product instead. Not only does that stand-alone product bring new design and scalability possibilities, it is also possible to share the Web Apps with Exchange and Lync 2013.

Prerequisites

To install Office Web Apps Server on a Windows Server 2012 box the following roles and features must be installed as a prerequisite:

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


If you want to use https for the Web Apps a proper certificate must be available on the server, too. To display the certificates installed on a computer try the following command:

Get-ChildItem Cert:\LocalMachine\my | select Subject,FriendlyName

The Web Apps Server can also be installed on Windows Server 2008R2, find the prerequisites on TechNet.

Installing Office Web Apps Server and creating the farm

The actual installation of the Server is pretty straightforward, just download the ISO and double click it (love that…). The only thing you can choose during setup is the installation path.

Once done with the installation, you can go ahead and use PowerShell to create a new Web Apps Farm. Not surprisingly the cmdlet to be used is New-OfficeWebAppsFarm, the following parameters have to be used to create a farm:

-InternalUrl: the URL used for internal Clients

-ExternalUrl: the URL used for Clients on the Internet

-CertificateName: set the FriendlyName of the certificate to be used for the farm

-EditingEnabled: enable editing of files in the browser (SharePoint)


The following example creates a farm

New-OfficeWebAppsFarm -InternalUrl "https://myOWAserver.tomt.local" -ExternalUrl "https://office.ntsystems.it" –CertificateName "ntSystems OfficeWebApps" –EditingEnabled


To verify that the farm has been created successfully, open a browser and go to https://myowaserver.tomt.local/hosting/discovery you should see some XML information about your internal and external URLs.

SharePoint 2013

Now to connect your SharePoint 2013 farm to the brand new Web Apps farm, fire up an administrative SharePoint Management Shell and use the New-SPWOPIBinding cmdlet. Use the –ServerName parameter to specify the internal URL of the Web Apps farm:

New-SPWOPIBinding -ServerName https://myOWAserver.tomt.local

 

After that you can have a look at the WOPI Zone, if users are accessing the SharePoint from internal and external clients you might want to change the zone from its default value of "internal-https" to "external-https":

Set-SPWOPIZone –zone "external-https"

 

Almost done, if you are using https on your SharePoint web applications you should be ready to go. If you are using http for SharePoint you need to set AllowOAuthOverHttp to true. This needs to be done in the SharePoint Management Shell using the following commands:

$config = (Get-SPSecurityTokenServiceConfig)

$config.AllowOAuthOverHttp = $true

$config.Update()

 

To check if it worked, use:(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

Try it…

Ready to see it? Open a browser, go to your SharePoint 2013 sites and create a new Document or open an existing one, should be looking like that:

 

So long,
tom

This post has been migrated from our earlier blog based on BlogEngine.NET.