Home > Office Web Apps, SharePoint, SharePoint 2013 > SharePoint 2013 and Office Web Apps 2013 resources

SharePoint 2013 and Office Web Apps 2013 resources

November 17, 2012 Leave a comment Go to comments

I just thought that it would  be a nice thing to have key links to getting started with Office Web Apps 2013 all in one place:

Download Microsoft Office Web Apps Server

Download Language Packs for Microsoft Office Web Apps Server

TechNet: Deploy the infrastructure: Office Web Apps Server

TechNet: Plan Office Web Apps (Used with SharePoint 2013)

TechNet: Overview of Office Web Apps and how they work on-premises with SharePoint 2013

The Licensing for Office Web Apps is all new:

Licensing Office Web Apps for editing Office files

          Office Web Apps licensing offers two options:

  • View-only. By default, Office Web Apps is view-only. View-only functionality is provided for free.
  • Edit and view. You must purchase an editing license to use the editing features of Office Web Apps with SharePoint 2013. You enable editing when you create the Office Web Apps Server farm.

Enterprise customers who are licensed for Office 2013 through a Volume Licensing program can enable Office Web Apps editing for SharePoint 2013 on-premises. This helps make sure that users have Office editing capabilities at home or in other locations where Office clients might not be installed. Editing licenses for Office Web Apps are not available for separate purchase.

For exact details about your license, refer to the Microsoft Software License Terms that is shown when you install Office Web Apps Server.

SharePoint 2013 provides new license enforcement that works with Office Web Apps. If you enable SharePoint licensing and then enable Office Web Apps editing, only the users who have the appropriate license, which is known as OfficeWebAppsEdit, can actually edit Office files in a browser. If no Office Web Apps editing licenses are applied for users, only viewing is supported. For more information about how licensing works in SharePoint 2013, see Configure licensing in SharePoint Server 2013. The EditingEnabled parameter that enables editing is described in New-OfficeWebAppsFarm and Set-OfficeWebAppsFarm.

Read more here: Licensing Office Web Apps for editing Office files

Remember also, that in 2013 the Office Web Apps server/farm is a shared resource between SharePoint Server 2013, Lync Server 2013 and Exchange Server 2013.

Browser support, see image:

As you can see, owa now supports most common browsers


_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Advertisements
  1. September 20, 2013 at 10:25

    Hi I have installed OWA 2013 via an MSDN download a couple of times now but all is not well Yes I can discover WAC server on my SharePoint server by the “http://myowa2013.mydomain.com/hosting/discovery” .and my bindings are internal-http. I notice the install does not request a license key which I suspect maybe my issue

    • September 20, 2013 at 16:47

      Hi Ed.
      I did not get what the issue was?
      Did you set it all up properly on the WAC as well as in SharePoint?
      Follow these two ‘Steve Peschka’ links which are great:
      http://blogs.technet.com/b/speschka/archive/2012/07/23/configuring-office-web-apps-in-sharepoint-2013.aspx
      http://blogs.technet.com/b/speschka/archive/2012/12/31/enabling-licensing-and-editing-for-office-web-apps-in-sharepoint-2013.aspx

      Hope that helps
      // Thomas

      • September 20, 2013 at 16:58

        Hi Thomas

        Good to hear from you again. Since posting my comment I have discovered that OWA works fine in My HSNC default web app but not in my host header defined Web App intranet.mydomain.com. Hence It has to be something to do with default zones and protocols. I have gone through the Technet loads of times but will check the resources you mention. Remember OWA 2013 is working.

      • September 20, 2013 at 17:09

        🙂
        Ed was a bad guess, I saw that now.

        My best tip, check ULS, even on the OWA, if memory serves you have a ULS on that as well.
        What do you see instead of the owa? An error?

        // Thomas

      • September 20, 2013 at 17:25

        No worries ( Ed was a nice change!)

        Really weird issue given my OWA install does actually work when looking a docs in the http://defaultWeb HNSC. So what can be the difference with these other site collections and the comms with OWAs

        Get-SPWOPIBinding shows all ‘internal-http’
        (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp returns True
        http://sp2013wac02.wsldev.com/hosting/discovery gives the desired output xml stream.

        On my OWA ULS logs I do see this helpful message

        FileUnknownException while loading the app. [FileSourceId: -1088102096] [ClusterId: 0] [ExtraErrorInfo: ]

        WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.FileUnknownException: WOPI 404 at Microsoft.Office.Web.Apps.Common.WopiDocument.LogAndThrowWireException(HttpRequestAsyncResult result, HttpRequestAsyncException delayedException) at Microsoft.Office.Web.Apps.Common.HttpRequestAsync.End() at Microsoft.Office.Web.Apps.Common.WopiDocument.GetWopiRequestResultWithRetry(Int32 maxSize, MemoryStream ms, WopiRequest wopiRequest) at Microsoft.Office.Web.Apps.Common.WopiDocument.CheckWopiFile()]

        (well you did ask!)

        Daniel

      • September 20, 2013 at 17:33

        Thomas

        No worries ( Ed was a nice change of label!)

        Well on my sp2013 dev server

        Get-SPWOPIZONE = internal-http
        (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp = True

        In the ULS logs in my OWA server I see this error
        http://sp2013wac02.mydomain.com/hosting/discovery shows the valid xml

        FileUnknownException while loading the app. [FileSourceId: -1088102096] [ClusterId: 0] [ExtraErrorInfo: ]

        WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.FileUnknownException: WOPI 404 at Microsoft.Office.Web.Apps.Common.WopiDocument.LogAndThrowWireException(HttpRequestAsyncResult result, HttpRequestAsyncException delayedException) at Microsoft.Office.Web.Apps.Common.HttpRequestAsync.End() at Microsoft.Office.Web.Apps.Common.WopiDocument.GetWopiRequestResultWithRetry(Int32 maxSize, MemoryStream ms, WopiRequest wopiRequest) at Microsoft.Office.Web.Apps.Common.WopiDocument.CheckWopiFile()]

        ( you did ask!)

        I have also put this on the technet forum: Word Web App: FileUnknownException while loading the app . (Office Web Apps)

        Daniel

      • September 21, 2013 at 07:56

        Hi Daniel.
        (It was the Westerdal Ed in my mind…)
        Sorry for the late answer, in a way different TZ…

        One thing that came to mind, you said HNSC(right?) and Host Header…
        A HNSC prepped Web App needs to be * 80 right?
        If that binds to all calls to port 80, how can you still have a host header Web? Different port?
        Could all that be a reason for the issues?
        A assume here they are in the same farm…

        Have you tried to set it all up using https instead? Use a selfsigned cert to test? (Have a post on that)
        Steves post uses https.

        Regards
        // Thomas

  2. September 23, 2013 at 14:01

    Hi Thomas

    Just to give an update on my bizarre issue.
    Firstly, my mistake none of web apps hosted are HNSC, the default web app http://servername is created with empty host header but I understand SharePoint does not currently allow this to host a root hnsc. Anyway these are the steps
    – turned off my current WAC server 02 (wac02) which was configured for internal-http
    – Start another OWA server: WAC Server 02 ( wac01) & created a self-signedcert
    – I remove the old WAC farm on this server and run
    New-OfficeWebAppsFarm –InternalUrl https://sp2013wac01 -ExternalUrl https://sp2013wac01.wsldev.com –CertificateName $certificateName –EditingEnabled -verbose
    -exported the cert and on my spdev01 server I import the cert to trusted Root Authority
    -check it can see the wac01 farm with https://sp2013wac01.wsldev.com/hosting/discovery
    – New-SPWOPIBinding -ServerName “sp2013wac01.wsldev.com” then Set-SPWOPIBinding -zone “external-https”
    – check AllowAuthOverHttp is set to $false, it wasn’t, so changed and rechecked
    – on my wac01 server I set New-OfficeWebAppsHost “wsldev.com”
    — go to any of my managed path site collections in the farm and the error is still there “Sorry this a problem….”
    – go back to default web app http://sp2013dev01/. and root sc and open a word doc ….again no issues ( even though I am now using HTTPS to connect to another WAC farm
    – Create a HNSC in the farm using the – HostHeaderWebApplication http://sp2013dev01 … go and upload/view a word doc an the issue is there.aaaahhhhhhhh!

    To conclude … it doesn’t seem to matter whether I use internal-http or external-https to on my WAC server, this not the issue.
    I think the zones in both the wac and sp2013 servers are correct.

  3. September 23, 2013 at 17:36

    Thomas, I have cracked it: wac01 sever could not ‘see’ the spdev01 server so I added a host entry. Also I note that since my sharepoint server is running over http ….. I have set AllowAuthOverHttp = $true…. Man that was painful

    • September 24, 2013 at 12:52

      🙂
      Nicely done. Sorry I could not be of more assistance, I hope you felt my mental support and that it helped some 🙂
      Thanks for the info. I had an issue a way back with externala ccess, turned out that the client needs to have access directly to both SP and WAC servers…it toll me a TMG server to fix that.

      // Thomas

  4. September 25, 2013 at 13:17

    Thomas . Actually you were the catalyst as you made me approach this from a different angle. Thanks again.

    • September 25, 2013 at 15:35

      Great I could be of help, if only little.
      Take care Daniel! 🙂

      Regards
      // Thomas

  1. May 6, 2013 at 12:55

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: