Remkomplekty.ru

IT Новости из мира ПК
0 просмотров
Рейтинг статьи
1 звезда2 звезды3 звезды4 звезды5 звезд
Загрузка...

Office online server

Office online server

Вопрос

Доброе время суток!

Есть определенный интерес к продукту Office Online Server (OOS). Но мне как простому обывателю показалась весьма запутанной политика лицензирования.

Был бы рад, если бы прояснились некоторые моменты, а именно:

Прочитав некоторую вводную информацию, насколько я понял необходима подписка на Office 365, только при таком условии будет возможность скачать OOS c Microsoft Volume Licensing Service Center (VLSC). Так ли это? А если я работаю в организации численностью, например, 100 человек, то подписка должна оформляться на каждого пользователя? Или достаточно только одной подписки и в таком случае функции по редактированию также будут доступны?

OOS предполагается использовать для совместного редактирования и просмотра Office документов внутри организации численностью 100 человек. Основной вопрос: какой продукт из линейки Office’a необходимо купить, чтобы решить данную задачу?

Все ответы

Прочитав некоторую вводную информацию, насколько я понял необходима подписка на Office 365, только при таком условии будет возможность скачать OOS c Microsoft Volume Licensing Service Center (VLSC). Так ли это? А если я работаю в организации численностью, например, 100 человек, то подписка должна оформляться на каждого пользователя? Или достаточно только одной подписки и в таком случае функции по редактированию также будут доступны?

В действующей редакции MPT (May.2017.Rus) серверный продукт под названием Office Online Server упоминается только в одном месте — в Приложении В, посвященном платным преимуществам программы Software Assurance (SA). Скачайте свежий MPT и откройте на 91 странице. Там вы увидите упоминание об этом продукте. А рядом, на странице 92, среди прочего, сказано следующее:

В свежем OST (May.2017.Rus) в разделе «Приложения Office 365» на странице 23 сказано следующее:

Право использования OOS предоставляют лицензии:

  1. Office Std + SA
  2. Office Pro Plus + SA
  3. Office 365 Pro Plus

Лицензию Office Std + SA (или Office Pro Plus + SA) нужно приобрести на каждое устройство, с помощью которого люди будут использовать функционал OOS. При этом, «основной пользователь» лицензированного устройства, получает право использовать OOS с любого устройства на планете. Эта юридическая формулировка с большим скрипом укладывается в голове. Но другой нет и не будет, пока лицензии Office Std и Office Pro Plus назначаются по старинке — на устройства, а не на людей.

Лицензию Office 365 Pro Plus нужно приобрести на каждого живого человека, использующего OOS. Тут все просто.

OOS — это софт, который ставится на сервер клиента, но право его использования нужно поддерживать периодическими платежами, продлевая подписку SA или продлевая подписку Office 365 Pro Plus. Не забывайте об этом важном моменте, развивая свой интерес к этому замечательному продукту.

Installing & configuring Office Online Server with Exchange 2016 / 2019

In this blog, I will review the installation and configuration process of Office Online Server 2016 (OOS) with Exchange 2016 / 2019 environment.
Using Office Online Server 2016 with Exchange 2016 or Exchange 2019, you will be able to view and even edit Office documents via Outlook on the Web (OWA).
Office Online Server is a very good solution for places where a full Office distribution is a challenge because of old hardware, slow internet connections and other technological challenges.

You to enable In my environment I’m using:

  • 2 Exchange 2019 servers running on Windows 2019 Core servers.
  • 2 Exchange 2016 servers.
  • 1 Office Online Server 2016 running on Windows 2016 Server (November 2018 Version).

  • Please pay attention, that only Exchange 2019 & Exchange 2016 can work with Office online Server 2016.

Except for the OOS installation and configuration, we will review the steps that needs to be taken within the Exchange 2019 environment and the ways to verify that the collaboration between OOS & Exchange is working.

Preparing for Office Online Server 2016 deployment

Office Online Server can be download from VLSC or MSDN (depends on your needs) in many languages:

There are many things that should be considered before deploying OOS, like Sizing, Virtualization, Ports, Load Balancing for high availability, Firewall and other security considerations.
In this blog I will not review all of those, but you can find all of them at the next link:
https://docs.microsoft.com/en-us/officeonlineserver/plan-office-online-server

Prerequisites:

  • Office Online Server can run (for now) on Windows server 2012 R2 and Windows 2016 only.
  • From Windows PowerShell, use this command to install the required roles and services (for Windows 2016 Server):

Add-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,NET-Framework-Features,NET-Framework-45-Features,NET-Framework-Core,NET-Framework-45-Core,NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-HTTP-Activation45,Windows-Identity-Foundation,Server-Media-Foundation

  • In addition, install the following prerequisites software:

Installing Office Online Server 2016:

After installing the prerequisites, you can continue with the OOS installation, which is very simple and short, just run the ISO file as the next example:

Now choose the installation location in case you would like to change it:

Click on Install Now:

Now click Close to exit the installation:

Configuring Office Online Server 2016:

After installing was completed, you should consider a common name that will be used on your environment, in order to access the OOS “Farm”.
OOS farm is the location where all users will be directed to (behind the scenes) to view and edit Office documents,
In real life you should consider working with a load balancer that will provide high availability to the OOS services.
In my environment, I will use a DNS record named OOS.msft.net that will point to my OOS server named OOS1. In case I would have more OOS servers, I would have created more DNS records that would point the name OOS.msft.net to the other servers.

Certificate:

In order to access OOS services via SSL 443, we need to issue and install a certificate, according to the name we have chosen earlier (OOS.msft.net).
I have already included at my Exchange’s servers certificate the name OOS.msft.net therefore in this example I don’t need to issue a new dedicated certificate, although it is the most recommended way in real life.
In this example, I will install the certificate named mail.msft.net from the PFX (private key) that I prepared in advanced (cert.pfx):

  • Verify that you choose Local Computer and NOT Current User

  • Choose the pfx location, than click Next:

  • Enter the password for the pfx and click Next:

  • Click Next:

  • Click Finish:

  • Click OK

In order to verify that the certificate was installed successfully, open the Certificates on the local computer and check that the certificate is located under the Certificates (Local Computer)PersonalCertificates

Читать еще:  Активатор для office 365 2020

OOS Farm configuration:

In order to configure the OOS farm, open the Windows PowerShell on the OOS server as an Administrator and run the following command, according to the common name you have chosen for internal and external URLs for OOS services and the certificate name you have installed earlier:

New-OfficeWebAppsFarm -InternalURL “https://oos.msft.net» -ExternalURL “https://oos.msft.net» -CertificateName “mail.msft.net”

You can see that the default configuration for editing is set to false (marked with yellow).
For now, I will leave this configuration as is.

Configure Exchange Server 2019 with OOS services

After we have set and configured OOS farm, we need to set the Exchange servers to “discover” the new farm.
We can configure it in two ways:

  • Configure each server (Exchange 2016 / Exchange 2019):
    We will use this option in case we are having Exchange 2013 servers in our environment and not only Exchange 2016 / Exchange 2019.
    Since Exchange 2013 is not able to work with OOS 2016 (and it is not supported as well), we will have to rune the following command on every Exchange 2016 / Exchange 2019 and not at the organizational level (like the next example)
    Set-MailboxServer MBX -WacDiscoveryEndpoint “https://oos.msft.net/hosting/discovery«
  • Configure the Exchange organization:
    We will use this option in case we are having only Exchange 2016 / Exchange 2019 servers.
    Since Exchange 2013 is not able to work with OOS 2016, we will have to rune the following command on every Exchange 2016 / Exchange 2019 and not at the organizational level (like the next example)
    Set-OrganizationConfig -WacDiscoveryEndpoint “https://oos.msft.net/hosting/discovery«

As I mentioned earlier, we will run the second option against our Exchange organization:

After you have configured the OOS “discovery” URL at the organizational level, we must refresh the new configuration on ALL Exchange servers using the next command:

Restart-WebAppPool MsExchangeOwaAppPool

Verify that Exchange Servers are able to access & discover OOS services correctly:

After we have set and configured the Exchange organization with OOS services, we must check that the Exchange servers can access & discover the new services.

  • Check that we can access the WAC discovery end point correctly from the Exchange servers: https://oos.msft.net/hosting/discovery
    WAC discovery endpoint is very similar to Exchange’s Autodiscover service which allows other systems to get the information that the server is delivering.
    In order to so we should open a browser (On Exchange 2016 / Exchange 2019 with Desktop).
    This option is not available on Exchange 2019 which installed on Windows 2019 Core server…..

It is very important to get the discovery output WITHOUT any certificate errors!
In case you are having an issue with a certificate on the OOS servers, you will not be able to access the OOS services!

  • Check the event viewer of the Exchange servers and verify that events 140 and 140 and 142 exists at the Application event log.

[Step by Step] Installing and Configuring Office Online Server on Windows Server 2016 for Exchange 2016

Office Online Server (OOS) is successor of Office Web Apps Server (OWA), which allows organizations to deliver browser-based versions of Word, PowerPoint, Excel and OneNote, among other capabilities. Microsoft recognizes that many organizations still value running server products on-premises for a variety of reasons. Just want to update over here, Office Web Apps Server is not supportable for Windows Server 2016.

OOS scales well for your enterprise whether you have 100 employees or 100,000. The architecture enables one OOS farm to serve multiple SharePoint, Exchange and Skype for Business instances. OOS is designed to work with SharePoint Server 2016, Exchange Server 2016 and Skype for Business Server 2015. It is also backwards compatible with SharePoint Server 2013, Lync Server 2013 and, in some scenarios, with Exchange Server 2013. You can also integrate other products with OOS through our public API.

Today, we are releasing our first significant update to Office Online Server that includes:

So, the question will be how can I get Office Online Server. The answer would be you need to get download it from your Volume License Service Center. Customers with a Volume Licensing account can download Office Online Server from the Volume License Servicing Center at no cost and will have view-only functionality, which includes PowerPoint sharing in Skype for Business.

Lab Environment:

Here is the architecture I am using for my Lab environment of OOS installation and configuration for Exchange 2016

Installing Prerequisites:

Before installing the OOS, we need to install the pre-requisites. Below is the Windows feature that are mandatory to install for the OOS in Windows Server 2016.

Installing OOS:

After the installation of Windows Features, now it’s time to install the OOS. To install OOS mount the download DVD from Volume License Service Center, and execute it.

Once the DVD is executed, it will prepare the necessary files that are required for the installation.

Once the preparation of files is complete, Check on EULA and click on ‘Continue’.

On the ‘File Location’ provide the path where OOS is needed to be installed and click on ‘Install Now’.

It will take around 10-15 minutes depending upon the specs of hardware to get complete the installation.

Once the installation is complete, click on ‘Close’.

Configuring OOS:

Unlike other application, it was quite easy for us to install OOS. Now the time is to configure it. Configuring OOS only contains the management of the certificate. 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). But if you want to use it on the External organization too, you need to have public SSL. For my demo lab, I just needed private certificate, hence created the one using Local CA.

To create the local certificate, Open IIS Manger-> Expand your hostname and open ‘Server Certificates’.

On the ‘Server Certificates’ right side at Action Panel, click on ‘Create Domain Certificate’.

A new window will get open, Provide the detail of Certificate on this window. The most important thing over here is, on the ‘Common Name’ you need to provide FQDN of your server. Else the certificate will not be valid and trusted. ( I have faced few problems year back with this issues, so sharing my experience on it).

Читать еще:  Office 2020 2020 c2r

On ‘Online Certificate Authority’, Select the Certificate Authority server and provide the ‘Friendly Name’ this could be anything and click on ‘Finish’.

Now you can see your newly certificate on you ‘Server Certificates’.

To Configure the OOS, we just need to assign the newly created certificate for the OOS Farm with below cmdlet.

Eli Shlomo

Cloud | Security | DevOps

Home Other Office Online Server Installation Guide

Office Online Server Installation Guide

Office Online Server or in a short OOS is the next version of Office Web Apps Server, as you know the Office Web App Server provided browser-based versions of Word, PowerPoint, Excel and OneNote.

Now the OOS brings the cloud to your On-Premises environment with new features and improvements, the OOS can work with Skype for Business, Exchange 2016 and SharePoint 2016.

The OOS can work with products that support WOPI (Web Application Open Platform Interface) and allow to view and edit documents with new improvements:

Improved co-authoring support

Significant additions to authoring features

Heavy investments in performance and stability

In a short WOPI is host that configured to use OOS or Office Web Apps Server, users are able to view and edit documents stored on the WOPI host by using OOS or Office Web Apps.

WOPI provides web-based services a way to view and edit documents in the Office Web Apps, with all the high-fidelity and richness that you expect from an Office document and is more or less a callback interface that operates over REST.

As a WOPI host, you expose a number of endpoints, in the form of URLs, and then you load a WOPI application, passing it the URL to your endpoint.

Get started with the OOS

You can download Office Online Server from Microsoft Download Center.

Once downloading the OOS we need to prepare the hardware, software, license and other systems.

Supported Operating System

Windows Server 2012

Windows Server 2012 R2

Internet Explorer 11

Apple Safari (Latest)

Google Chrome (Latest)

Mozilla Firefox (Latest)

The OOS can deploy into few scenario, such: Development , Web server, Application server and more.

On each environment we need prepare the hardware with the specific Memory, CPU and disk. To install for pilot, user acceptance test, or production deployment we need the following requirements:

RAM 12 GB, CPU 64-bit, 4 cores, Disk 80 GB for system drive.

How to Install

Deploying Office Online Server involves installing some prerequisite software and running Windows PowerShell command, but overall the process is designed to be pretty straightforward. This article walks you through the procedures to get your servers ready.

Install IIS prerequisites

To install prerequisite software for Office Online Server make sure that you’ve installed Windows Server 2012 and higher with the latest update.

On Windows Server 2012 or Windows Server 2012 R2 open PowerShell console and type the following PowerShell Command:

Once it done the installation reboot your server.

Install .NET Framework 4.5.2

Download .NET Framework 4.5.2 from Microsoft Download Center

Install .NET Framework 4.5.2

Once it down reboot your server again.

Install OOS

Note: You cannot install the Office Online Server on the SharePoint Server.

Download Office Online Server from Microsoft Download Center

Mount the ISO and run Setup

On the wizard choose “Read the Microsoft Software License Terms” page, select I accept the terms of this agreement and click Continue

Make sure that you’ve digital certificate for the IIS (for the Farm), if not create certificate using IIS manager console, Certificate MMC or PowerShell.

In the certificate make sure that you’ve the correct domain for OOS farm.

Create OOS Farm

For most production environments, its recommend the use of HTTPS for its security features, for Exchange 2016 and Skype for Business you must use HTTPS.

Open PowerShell in admin mode

Type the following PowerShell command (change to your domain name and certificate name)

New-OfficeWebAppsFarm -InternalUrl “ https://oos.lab.local ” -CertificateName “OOS”

Make sure that you’ve retrieve the farm with the relevant settings

Check OOS and Farm

After installing and configuring farm make sure that you’ve the following settings:

Office Online Service

Make sure that Office Online service is up and running

Make sure that the virtual directory for HTTP80 is created with the path for hosting and discovery.aspx

Make sure that you can browse to the server (In accordance with settings), you must receive the site with no certificate warning

Deploying Office Online Server (OOS) (Part 2)

If you would like to read the other parts in this article series please go to:

Introduction

In the previous article we defined a DNS name for the Office Online Server (OOS), and we defined it as oos.montreallab.info. In this article series, we are going to use a simple scenario (Figure 01) where the Active Directory FQDN is an invalid FQDN and the Public Domain is montreallab.info. The Exchange Server is using the names webmail.montreallab.info and autodiscover.montreallab.info, and on the same certificate we will be adding the additional name oos.montreallab.info.

Public Certificate to support Exchange and Office Online Server (OOS)

In this section we will cover the basic steps using Exchange Admin Center (EAC) to create a new certificate request for Exchange Server 2016 including the Office Online Server name.

  1. Open Exchange Admin Center (EAC)
  2. Click on servers and then certificates
  3. Click on + to start a new certificate request
  4. On the initial page, select Create a request for a certificate from a certificate authority and click Next
  5. Define a friendly name for the certificate, we will use MontrealLAB – Public Certificate, click next
  6. In the next page (wildcard certificate), just click next. We will use a SAN (Subject Alternative Name) certificate and define up to four (4) names instead of a wildcard certificate.
  7. In the next page define the Exchange Server that will host the certificate request, and click Next.
  8. In the page listing Access and URLs, just click Next
  9. Define the names that will be used by the new certificate and we are going to use a name for webmail/Outlook Anywhere (webmail), autodiscover services (autodiscover), Active Directory Federation Services (adfs), and the role that we are covering on this article which is Office Online Server (oos), as shown in Figure 02. After that click next.
  10. Fill out the information about the company, and click next.
  11. In the last page of the wizard, type in the UNC location to save the new exchange certificate request file.
    If the shared folder hasn’t been created yet, the following MSExchange.org Article describes the entire process and the additional steps to complete the certificate: http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/managing-certificates-exchange-server-2013-part3.html
Читать еще:  Office online server 64 bit russian

After creating the new certificate, we need to export the Public Certificate from Exchange Server to the new Office Online Server (OOS), these following steps can be used when logged on Exchange Server:

  1. Open Exchange Admin Center (EAC)
  2. Click on servers and then certificates
  3. Select the server that has the Public Certificate from Select Server field, and then select the certificate from the list. Click on and then Export Exchange Certificate item
  4. In the page provide the UNC path to the certificate (Figure 03) that we are exporting and a password that will be used during the import process on the Office Online Server.

The final step is to move the exported certificate (in this Article, the name used was cert-export.pfx) to a folder on the Office Online Server (OOS). Logged on Office Online Server (OOS), right-click on windows button and click on Run, type mmc.

  1. Click on File, and then Add/Remove snap-ins, select Certificates and click on Add. In the new window, select Computer account and click Next, and Finish. Back to the Add or Remove Snap-ins window, just click on OK.
  2. Expand Certificates, right-click on Personal, click on All Tasks and then Import…
  3. In the Welcome to the Certificate Import Wizard page, click Next.
  4. In the File to Import page, click on Browse… select the certificate that we copied over to the server (Figure 04).
    Note: Make sure to select All Files (*.*) to find the file exported on the Exchange Server.

  • In the Private Key protection Type in the password defined during the export process in Exchange, leave default settings under Import options and click Next.
  • In the Certificate Store Leave default settings which is Place all certificates in the following store and Personal is listed underneath, click on Next.
  • In the final page of the wizard just click on Finish, a new dialog box saying The import was successful will be displayed, just click OK.

Just to make sure that the proper certificate was installed (Figure 05), double click on the new certificate (2) listed under Certificates Personal (1), click on Details tab (3), and then click on Subject Alternative Names (4) and the OOS name that we defined for this article series oos.montreallab.info should be listed there.

OOS Server – Initial configuration

The Office Online Server was deployed on the previous article, and now it is time to configure it and start performing the initial tests. The cmdlet to configure the Office Online Server accepts several properties to be configured, however we will start simple with just a few parameters and we will be configuring the server as part of this series.

For starters, there is no Graphical User Interface (GUI) to configure the Office Online Server (OOS) at this point, and all management is done through PowerShell.

The first step is to identify the Certificate Friendly name and that information can be retrieved using either the properties of the certificate and looking for the Friendly Name field, as shown on the right side of Figure 06, or using the following PowerShell cmdlet also shown on the same figure 06.

Get-ChildItem cert:localmachineMy | FL FriendlyName,Subject,NotBefore,NotAfter

The initial configuration to get Office Online Server running requires the definition of the internal, external URLS, and the certificate that is going to be used by the server. The simplest way to configure Office Online Server is using the following cmdlet (Figure 07).

Note: The Friendly Name will require “” when defining it on PowerShell.

By default, if we try to test the Office Online Server by typing in the URL we will get a 404 error, as shown in Figure 08.

The 404 error above is not a misconfiguration during the installation, just standard settings, in order to display an initial page for Office Online Server the OpenFromURLEnabled must be changed to $True, and we can do that using the following cmdlet. In the Figure 09, we list the current settings before changing it.

After that change, an user can try to access the Office Online Server and the initial page will be displayed (Figure 10), and from that point on a link can be created for an Internet location or UNC.

A simple test is to provide a UNC path of a document on a file share, for this exercise we downloaded the first .docx document that we could find at Microsoft website (the document name was Microsoft Access 2010 Product Guide.docx) and we placed the file on a shared folder (\mtloos01share). In order to test, just enter the UNC path (including the document) on the first field of the Office Online Server main page, and then click on Create link (Figure 11), and as result an URL will be created and that can be send to another user that does not have office installed to test it.

The administrator can click on Test this link on the same page, and the Word Online will show the contents of the file, as shown in Figure 12.

Conclusion

In this second article we worked on the Certificate configuration on both Exchange and Office Online Server sides, and configured the Office Online Server initial page and some testing using UNC.

If you would like to read the other parts in this article series please go to:

Ссылка на основную публикацию
Adblock
detector