#OFFICE ONLINE SERVER 2019 INSTALL#
#OFFICE ONLINE SERVER 2019 SOFTWARE#

After installing those new features, a restart of the server is recommended before moving forward with the next step.

#OFFICE ONLINE SERVER 2019 INSTALL#

The first step is to install Windows Server features, and that can be done using the following cmdlet listed below (Figure 02). Install the Office Online Server (OOS) Preview bits.Install Visual C++ Redistributable for Visual Studio 2005.Install Windows Features required by Office Online Server.The future Office Online Server should have all Windows Updates in place before moving to the next topic.We are going over each component in this section.

#OFFICE ONLINE SERVER 2019 SOFTWARE#

The process to install the Office Online Server requires a few software components and the following list has a summary of the required software and is using the proper installation order.

If you already have a valid FQDN, then it is just matter of adding new entries for the new services that you defined on your certificate.

After creating the new zone that matches your valid FQDN, just add the names that will be used by Exchange Services, OOS, ADFS, and so forth as hosts on that new zone.

If you have an invalid FQDN (e.g.: company.local, rp) you can create a valid FQDN zone at the DNS level (create as Primary Zone and store in Active Directory to guarantee the replication to all Domain Controllers), this format is also known as split-brain DNS.

Your current environment is in one of the situations below, so use the scenarios below to define where to configure your DNS to support Office Online Server. There are a couple of reasons, one of the most compelling is that Public Certificates are issued only to valid FQDN, and in that case it is easier to point all Exchange Web Services to valid FQDN and use DNS (Internal and Public) to point the clients to the right server. If you have an invalid FQDN (e.g.: company.local) you may want to use a split-brain DNS where your public domain is created internally and the name resolution of that public zone internally is using internal servers.Д®xchange Server 2016 and transition processД«ased on MicrosoftвЂ™s recommendations it is easier to play with a valid FQDN when using products from Unified Communications family, such as: Skype for Business, Exchange Server and Office Online Server.

Active Directory is able to resolve your public domain internally.Just keep adding names and it will be cheaper and it will reduce the hassle of maintaining several individual certs for each service/application. Depending of your environment you can use the same Public Certificate for several services, such as SharePoint, Exchange Server, Skype for Business, Active Directory Federation Services, Office Online Server and so forth.Most likely you will use a Subject Alternative Name (SAN) certificate which will support several names, and for Exchange you can start asВ simple as 2 names to support a single site (you may need additional names based on your Disaster Recovery, or in case of having multiple sites).

Use a Public Certificate (you can use SAN or wildcard certificates) although the preference is to use SAN (Subject Alternative Names).

Here are some recommendations that will help you to design your Office Online Server environment, as follows: A good thing is that we can find synergies on all those products and they can share the same certificate if we plan well. The Certificate is always a discussion topic on any design for Exchange and Skype for Business, and the same applies for Office Online Server.

Office online server 2019