This is a really neat feature, especially when reviewing search results. It allows users to peer into a document and check that it’s the right one before loading it up into a client application for editing. I digress, this post is about getting OOS up and running with SP2013 where, thankfully, we don’t have to deal with the inadequacies of the new experience (do I sound cynical)! What use is OOS?Īpart from being just cool, OOS is actually useful. They seem to have done away with this in the “New Experience” in O365 – why? Or at least that’s what happens with the so called “Classic Experience” of a document library. What is Office Online Server?įor those of you who don’t know what OOS is then why are you reading this article? Just kidding, OOS is the new shiny replacement for Office Web Apps (OWA) which is that really cool thing you see in SharePoint Online/O365 whereby when you click on an Office format document (or web page, or if you’ve set it up a PDF) it opens up a sort of in-page dialog viewer thingy called a Callout. So this time around, I thought I’d actually document the process and follow the SP2016 guidance as best as I could to get this baby up and running for SP2013.
SETUP OFFICE ONLINE SERVER SHAREPOINT 2016 HOW TO
The Microsoft blurb says that this is a supported deployment scenario but I could find nothing more on how to actually do it as everything was aimed at SP2016. Of course I was in a rush and didn’t take any notes at the time.Īnyway, I now have reason to install OOS in an on-prem test environment and hook it up to SharePoint 2013. As far as I can remember the process went fairly smoothly but I do faintly remember that getting the Windows 2012 R2 server that hosts OOS up and running was a bit tricky with some missing dependencies and the like. On a test machine up in Azure I recently installed Office Online Server (OOS) and successfully hooked it up with a SharePoint 2016 server, also in Azure.
0 kommentar(er)
