Menu
When used with SharePoint Server 2013, Office Web Apps Server provides updated versions of Word Web App, Excel Web App, PowerPoint Web App, and OneNote Web App. Users can view and, in some cases, edit Office documents in SharePoint libraries by using a supported web browser on computers and on many mobile devices, such as Windows Phones, iPhones, iPads, and Windows 8 tablets. Office Web Apps Versions Office Web Apps Server 2013 (on-premises). OneDrive/SkyDrive/Office 365 (cloud). The Office Web Apps is the Word, PowerPoint, Excel and OneNote engine that allows users to work with Office content using the web browser. A single-server Office Web Apps Server can support users of Exchange Server 2013, Lync Server 2013 and SharePoint Server 2013 viewing files stored on network shares enabling greater server utilization on the existing infrastructure. Office Web Apps Server 2013 & Office Online Server Support Blog Office Web Apps Server 2013 & Office Online Server Support Blog Office Web Apps Server 2013 – Determining the build. Tom Schauer - MSFT January 10, 2014 4.
- Office Web Apps Server 2013 Versions Download
- Office Web Apps Server 2010
- Microsoft Office Web Apps Server
- Office Web Apps Server 2013 Versions For Pc
- Microsoft Office Web Apps Server 2013 Version Numbers
Provided you are armed with knowledge of the appropriate 'gotchas,' installing Office Web Apps Server 2013 in a SharePoint Server 2013 isn't too difficult.
Timothy Warner
Timothy Warner is a Microsoft Cloud and Datacenter Management Most Valuable Professional (MVP) who is based in Nashville, TN. Check out his Azure and Windows Server video training at Pluralsight, and feel free to reach out to Tim via Twitter.
Latest posts by Timothy Warner (see all)
- Specops Password Auditor v7.2: New features - Thu, Sep 12 2019
- EMCO Ping Monitor Enterprise v7 new features - Tue, Sep 10 2019
- Specops password policy v7.2: New features - Mon, Sep 2 2019
As you probably know, Office Web Apps Server is a SharePoint add-on product that gives you Web browser-based versions of the following Office applications:
In my experience, Office Web Apps (confusingly referred to as OWA in Microsoft product documentation--don't you think of 'Outlook Web App'?) is a no-brainer for on-premises SharePoint deployments because your users can view, edit, and create Office documents without having to rely upon locally installed Office software.
![Microsoft office web apps server 2013 version numbers Microsoft office web apps server 2013 version numbers](/uploads/1/3/3/8/133865557/368374444.png)
Wifi router password hacking software. What you might not yet know is that the current version of the product, Office Web Apps Server 2013, is quite changed from its previous iteration. Here are the major changes:
- OWA 2013 is no longer a service application that is directly integrated into SharePoint. Now OWA runs as a separate server
- OWA 2013 cannot be installed on the same server running (a) SharePoint; (b) SQL Server; (c) AD DS. Also, you can't have a local installation of Office on your OWA server.
- OWA 2013 now supports multi-author editing
- OWA 2013 now supports Adobe PDF conversion from Word (Didn't see that one coming, did you?)
- OWA 2013 requires Windows PowerShell for all aspects of installation and management
Office Web Apps Server 2013 Versions Download
I'm sure that my final bullet point may strike a bit of fear into the hearts of Windows administrators who have not yet taken the plunge into Windows PowerShell. Look at it this way: Deploying OWA 2013 to your SharePoint farm gives you the perfect excuse to dive into master Windows PowerShell!
One more preliminary note--about licensing. OWA 2013 is free to download, and the product may be installed on as many servers as you need to run the service. The cost comes in user licensing, and the details on this depend upon (a) whether your users will read documents or read and write; and (b) whether your OWA faces only your internal environment or if it will be exposed to the Internet.
I'll spend the remainder of this blog post giving you the high-level overview of how to set up OWA 2013 in your SharePoint farm. For better or for worse, I assume that your servers all run Windows Server 2012 and your SharePoint environment is based in SharePoint Server 2013.
For those who love summaries, here are the steps from a bird's eye perspective:
- Manually install the prerequisite software
- Download and install the OWA 2013 binaries
- Download and install the latest Public Update
- Create the OWA farm
- Configure the SharePoint-OWA binding
Let's begin!
Download and installation ^
As I said already, you can download the Office Web Apps Server 2013 for free from the Microsoft Download center. Again, when you pick out your candidate server to run OWA 2013, remember that the server can't have SharePoint, SQL, or Office installed locally.
Office Web Apps Server 2010
You know how SharePoint has a prerequisite installer that automates the installation of prerequisite software? Yeah, well OWA 2013 doesn't include any of that. If you try to install the OWA binaries by running Setup.exe from the downloaded bits, you'll see the uninformative error message that is shown below.
Setup is unable to proceed due to the following error(s)
What exactly are the OWA 2013 prerequisites? Check the documentation, and in the meantime, let's go ahead and manually configure the prerequisites proactively. Fire up an administrative PowerShell session, run Import-Module ServerManager, and then issue the following statement:
Once you're back from the reboot, run Setup.exe again and accept all defaults. Microsoft office beta version free download. When you are finished laying down the binaries you'll see equally content-free message box shown in the next screenshot.
Thank you for installing Microsoft Office Wet Apps Server 2013.
Before we create our OWA farm and connect OWA to our existing SharePoint farm, download the latest Office Web Apps Server 2013 public update from the Microsoft Download Center. There's no magic here--download, install, and reboot.
With that out of the way, let's remain on the OWA server and create our OWA farm.
Configuration ^
Okay. Believe it or not, we need only a single PowerShell statement to set up the OWA farm on our OWA server. Check it out:
Microsoft Office Web Apps Server
- Internal-HTTP
- Internal-HTTPS
- External-HTTP
- External-HTTPS
If you use OWA in an HTTP environment like I'm doing here, then you also need to set the AllowOAuthOverHttp property of the SharePoint Security Token Service (STS) object to True. Here's the formula:
You can see what a document looks like when it's open for editing in Word Web App by inspecting in the next screenshot and a browser-based PowerPoint deck after that.
The editing experience in Office Web Apps is excellent, on par with that of Office 365.
Office Web Apps makes it convenient to display PowerPoint content without requiring the presence of a local PowerPoint installation. https://iloveclever491.weebly.com/podcasts-free-serial.html.
Deactivate adobe id. That wasn't too difficult, was it?
There are multiple ways to find the OWA 2013 patch or build level:
Use PowerShell
- Check the X-OfficeVersion header value, on an Office Web Apps (OWA) or SharePoint server, replace the highlighted owa01 in red with your owa server url and run
Office Web Apps Server 2013 Versions For Pc
(Invoke-WebRequesthttp://owa01/op/servicebusy.htm).Headers
Microsoft Office Web Apps Server 2013 Version Numbers
- On Office Web Apps server
Get-Content 'C:ProgramDataMicrosoftOfficeWebAppsDatalocalOfficeVersion.inc'
On an Office Web Apps Server, check the OfficeVersion.inc file located here
C:ProgramDataMicrosoftOfficeWebAppsDatalocalOfficeVersion.inc
You can also check the X-OfficeVersion header valueright from the browser. Please head over to my colleagueTom's blog post here.