![]() ![]() I hope this was the easy configuration for the integration of Office Online Server with Exchange Server 2016. Similarly, you can edit and view other office documents too like PowerPoint and Excel. If this kind of error appears, please follow the instruction on this blog to resolve it. If everything goes right, you will be able to read and edit the document.ĭuring the Edit of the document you might face this issue ‘Sorry, you don’t have a license to edit document with Word Online. If this happens again, try opening the document in Microsoft Word.’ To fix this error, get to this blog where I have posted the resolution for problem like this. Once you click on ‘View’, you document will start to get open on Word Online which has been hosted by OOS Server.īut sometime you might get this kind of error ‘Sorry, there was a problem and we can’t open this document. When I clicked on the dropdown of the attachment document, I can see two options ‘View’ and ‘Download’. Testing:įor the testing purpose, I have created two email here I have attached a Word Document on an email and send it to the DM01 to check it. Now let us move for the testing of the configuration. C : \ Windows \ System32 > Restart - WebAppPool MsExchangeOwaAppPoolĪnd it is all to bind the Office Online Server with Exchange Server 2016. To Configure the OOS, we just need to assign the newly created certificate for the OOS Farm with below cmdlet. Now you can see your newly certificate on you ‘Server Certificates’. On ‘Online Certificate Authority’, Select the Certificate Authority server and provide the ‘Friendly Name’ this could be anything and click on ‘Finish’. ( I have faced few problems year back with this issues, so sharing my experience on it). Else the certificate will not be valid and trusted. The most important thing over here is, on the ‘Common Name’ you need to provide FQDN of your server. On the ‘Server Certificates’ right side at Action Panel, click on ‘Create Domain Certificate’.Ī new window will get open, Provide the detail of Certificate on this window. To create the local certificate, Open IIS Manger-> Expand your hostname and open ‘Server Certificates’. For my demo lab, I just needed private certificate, hence created the one using Local CA. But if you want to use it on the External organization too, you need to have public SSL. Hence if your machine is in the domain and you just want the feature of OOS within your private intranet, it’s okay to use Local Certificate Authority (CA). Configuring OOS only contains the management of the certificate. Unlike other application, it was quite easy for us to install OOS. Once the installation is complete, click on ‘Close’. It will take around 10-15 minutes depending upon the specs of hardware to get complete the installation. On the ‘File Location’ provide the path where OOS is needed to be installed and click on ‘Install Now’. Once the preparation of files is complete, Check on EULA and click on ‘Continue’. Once the DVD is executed, it will prepare the necessary files that are required for the installation. To install OOS mount the download DVD from Volume License Service Center, and execute it. Install - WindowsFeature Web - Server, Web - Mgmt - Tools, Web - Mgmt - Console, Web - WebServer, Web - Common - Http, Web - Default - Doc, Web - Static - Content, Web - Performance, Web - Stat - Compression, Web - Dyn - Compression, Web - Security, Web - Filtering, Web - Windows - Auth, Web - App - Dev, Web - Net - Ext45, Web - Asp - Net45, Web - ISAPI - Ext, Web - ISAPI - Filter, Web - Includes, Windows - Identity - FoundationĪfter the installation of Windows Features, now it’s time to install the OOS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |