All 3 servers are running Windows Server 2012 R2. There is an existing Exchange hybrid configuration with my Office 365 tenant. All servers have been configured to be on the same VLAN. I have 3 servers (One DC/Azure AD Connect server, One Exchange 2016 server, and one OOS server). If not, maybe I am in the future too and I have updated this article.įor this deployment I will be using my Exchange hybrid lab hosted in Azure. Hopefully it is pretty close to the preview version I am using for this article. If you are currently in the future, you are likely to be deploying the final release version of Office Online Server. Please note the publish date of this article. Office Online Server Preview is available at this link. It was “sort of” used for Exchange 2013, but I never ran into an Exchange 2013 deployment that made use of WAC 2013. WAC 2013 was a separate server that was used for Lync and SharePoint 2013.
WAC 2010 was a SharePoint add-on used exclusively with SharePoint. Don’t ask.) and WAC 2013 were earlier versions of OOS. WAC 2010 (WAC was the acronym for Office Web Apps Server. That way we'll all stay a little bit saner. Let’s just pretend that Microsoft has not renamed a whole bunch of products, and go with the current names. I had originally written an explanation of all the different names and acronyms for different products here, but it made no sense when I was done. You may know this product by several acronyms (WAC, OWAS), but it is now called OOS.
To enable Modern Attachments in Exchange 2016, we are going to have to deploy Office Online Server. Modern Attachments are a great step forward in that they allow users to continue to use attachments in the way they are used to while removing those files from your Exchange 2016 servers. Modern Attachments are not attachments at all, but links to Office documents that are stored within SharePoint sites but presented to look like attachments within email messages. One of the new features of Exchange 2016 is the inclusion of “Modern Attachments”.