Microsoft released Office Online Server (OOS) to its MSDN subscribers. OOS is useful for running browser-based versions of Word, Excel, PowerPoint and OneNote. If you are running SharePoint Server 2016, you may have some uncommon enthusiasm for the release of OOS. We should investigate the OOS prerequisites distributed by Microsoft.
To introduce OOS, take after these guidelines on TechNet wiki or the accompanying definite directions on Microsoft TechNet. Be that as it may, before you go too far, I urge you to peruse the checklist later in this article to check whether OOS is a suitable solution in your surroundings.
Compatibility with Office Version
If you have a 32-bit version of office introduced on the PC, you won't have the capacity to introduce the 64-bit Office Online Server (see screenshot underneath). You would need to uninstall the 32-bit version of Office first and afterward introduce the 64-bit version of Office Online Server. This is somewhat fascinating because I didn't see the option to download a 32-bit version of Office Online Server (you can just download 64-bit version) and regardless of the fact that you could, Microsoft doesn't prescribe introducing 64-bit version of Office. So you have two options.
To begin with evacuate 32-bit Office and after that introduce Office Online Server, or if you require Office applications on the server then first expel 32-bit Office, download and introduce a 64-bit version of Office and afterward introduce Office Online Server. This may not be a major ordeal because for security reasons a great deal of administrators, including me, would prefer not to introduce Office applications on servers however I thought it merits saying.
Checklist for Configuring SharePoint Server for OOS
Before you start, SoftwareDepot.co advises that you should ensure that you remember the following checklist.
1. Make sure your SharePoint Server 2016 Web applications are using claims-based validation. If you are using great mode verification, Office Online rendering and editing won't work.
2. You will require an editing permit to ensure users can edit Office documents in their Web browsers. Without the permit, users can just read Office documents in their Web browsers. Bear in mind to enable editing on the OOS ranch because you are going to need it to edit documents in the browser.
3. Don't login to the SharePoint Server 2016 with a System Account if you need to test the association between the SharePoint Server 2016 and OOS. Use a different record.
4. The Office document sneak peak may come up short in OOS if low memory condition is experienced.