Office Document Editing using Office Online Server 2016 with On-Prem Exchange 2016

Product covered – Office Online Server 2016 and Exchange 2016 CU2

Summary/Goal – Achieve document editing using a web browser without having desktop version of MS Office 2016

 

Like Office 365 document editing, you can also setup your infrastructure for the on-prem document editing . The end-user does not require desktop version of Microsoft Office.

In this lab, I’m using a 3rd party ssl certificate and all the domain name are FQDN.
Exchange URLS  https://mail.office365sme.com, auto discover.office365sme.com 
OOS Server URL https://oos.office365sme.com 
Friendly Certificate name The Office 365 SME

 

Begin Installation

Office Online Server 2016

If you see the same error as I did then install the particular KB, once installed it will dis-appeared as below

Screen Shot 2016-07-22 at 3.00.49 PM

Screen Shot 2016-07-22 at 4.08.16 PM

 

Now setup your OfficeWebApp Farm as below – As mentioned above I’m using the same url. These are my lab urls–

Screen Shot 2016-07-22 at 4.10.32 PM

It FAILED, because the certificate name was type incorrectly. I ran the same cmdlet agains with the correct Certificate Name ‘The Office 365 SME’

Screen Shot 2016-07-22 at 4.29.04 PM

Setting up Exchange 2016 Server to integrate with Office Online Server 2016

Screen Shot 2016-07-22 at 4.36.06 PM

Verifying the above integration –

https://oos.office365sme.com/hosting/discovery

Screen Shot 2016-07-22 at 5.24.57 PM

 

Viewing / Editing the Document Online via browser on your On-Prem Exchange 2016

Screen Shot 2016-07-22 at 4.37.54 PM

 

Screen Shot 2016-07-22 at 4.38.24 PM

 

Cheers 🙂

Now your on-prem Exchange 2016 offers you the same feature (one of them) as Office 365.

Office Online Server 2016 Install and Update for Universal C Runtime in Windows

You may get this error if you are installing Office Online Server 2016 on Windows 2012 R2 Data center.

There are two ways to fix it, either install the below KB or do the full server update if you are setting up a new server , like in this example.

Office Online Server 2016

As soon as I’ve done the server update and ran the setup again I don’t see this error anymore and the installation goes smooth.

https://support.microsoft.com/en-us/kb/2999226

Screen Shot 2016-07-22 at 12.19.25 PM

Now you are good to go with the installation of OOS 16.

Exchange 2013/2016 Cumulative Updates and Hybrid Environment.

Exchange 2016 CU2 and Exchange 2013 CU13 now supports .NET Framework 4.6.1

Today Microsoft Exchange Team made announcement of not one but two cumulative updates, one for Exchange 2013 which is Cumulative update 13 and Cumulative CU2 for Exchange 2016.  With these CU updates .NET 4.6.1 is officially supported now.

I’d like to start with Hybrid Deployment first

Minimum CU For Hybrid environments

So if you are and Exchange 2013 or Exchange 2016 or mix of both then you have no choice EXCEPT  upgrade to either CU12 minimum (.NET 4.6.1 is not supported on CU12) or CU1 at minimum (.NET 4.6.1 is not supported on CU1) respectively. So if you on hybrid and want to be at the upgrade to  .NET 4.6.1 then you have to be on the latest CU Levels.

How to proceed?

Do not install .NET 4.6.1 directly on your existing CU, first you need to upgrade to CU13 for Exchange 2013 and CU2 for Exchange 2016, this is the recommendation as per #msexchange team.

  • Exchange Server 2016 Cumulative Update 2 does include updates to Active Directory Schema

Post CU installation

(these three KB article solves the same issue of course you need separate hot fix for all the OS)

Migration to Modern Public Folder Resolved

The issue reported in KB3161916 has been resolved.

To prevent any installation issue
make sure that Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded to.

SHA-2 Support for Self-Signed Certificates

The New-ExchangeCertificate cmdlet has been updated to produce a SHA-2 certificate for all self-signed certificates created by Exchange. Customers may opt to replace existing non-SHA2 certificates generated by previous releases as they see fit.

Support for Exchange 2010 ???

Exchange 2010 is still not support and will never be as per Jeff Guillet – http://www.expta.com/2016/06/exchange-2016-cu2-and-exchange-2013.html (read his own comment at the bottom of this post)

For full details checkout #msExchange Team Blog

Removing Add-ins from Outlook in Office 365 – 3rd Party Data Sharing and your corporate network

Saturday, July 30th 2016

In my last post I’ve talked about installing the 3rd party Add-ins in Outlook for Office 365. As I said there are many Add-ins from embedding google search into Word, printing email as a PDF etc. I’m more concerned about Add-ins in #Outlook because you don’t what these 3rd party reads your data , I mean your email data unless you read each 3rd part’s privacy terms and condition. So if you are concerned about security like me or dealing with a an enterprise environment then these add-ins may not work you. some of them will such as Bing , Google but printing email as print etc may not work.

So I’ll walk through here removing these add-ins

Screen Shot 2016-04-12 at 4.25.53 PM

Office365

Office365

Screen Shot 2016-04-12 at 4.50.56 PM

If you notice that Uber add-ins is not there.

 

Announcing Exchange ActiveSync version 16.1

Saturday, July 30th 2016

Microsoft Exchange has just announced support for EAS Protocol version 16.1 on their blog.

They have introduced three new major capabilities

  1. Improved Keyword Search – Get quicker, more relevant results when searching your inbox. Clients can now perform Keyword Query Language searches (from, to, subject, etc.) by using the new Find command.
  2. Propose New Time – Users have asked for the ability to propose a new time for a meeting while on the go, and we have added full support for new time proposals in EAS 16.1.
  3. Account-Only Remote Wipe – Administrators can now request clients using EAS 16.1 to wipe only Exchange data from a user’s device.

Customers with their mailbox in Office 365 can take advantage of these new features when their favorite EAS client is updated.

How do you know your mailbox is supported with the new EAS Protocol?

As an end user, how can you tell if your mailbox is enabled for EAS version 16.1? The simplest way is to run an “Exchange ActiveSync” test at https://testconnectivity.microsoft.com and look for version 16.1 listed as one of the supported protocol versions (MS-ASProtocolVersions header in the OPTIONS command response) in the test results. Note that you need a valid Office 365 email address and password in order to run that test, and the results are specific to that mailbox only (not the entire tenant).

Checking EAS Version using Exchange Remote Connectivity Analyzer

Office 365

 

Screen Shot 2016-06-14 at 9.20.21 PM

 

Screen Shot 2016-06-14 at 9.20.32 PM

 

Screen Shot 2016-06-14 at 9.21.59 PM

If you see here (above), it show that the my mailbox has the EAS 16.1 version.

How to Check EAS 16.1 on you Mobile Device? 

In my case I’m using iPhone 6.0, and the app below shows that these capabilities are available.

Office 365

 

Outlook APP

If you only OWA APP for Exchange is capable of doing these new feature. Outlook App and iOS default Exchange and Outlook can’t perform these features. I believe #Apple will have to support it. But i wonder why only one OWA APP is supporting EAS 16.1 and why not Outlook APP.

Office 365

Photo 5

In my opinion it would have been  perfect if it supports the native client on iOS which dominate most of the mobile market. I’m not sure about Windows Phone and Android Phones. I believe Apple will get it fixed while I still have to hear from someone if these new capabilities are possible on Windows Phone.

Microsoft Blog URL for EAS 16.1 

And this is how you can also verify your EAS Version of you mailbox using Office 365 Admin Panel

Office365

 

Exchange Server 2013/2016 Components in an Inactive State

Saturday, July 30th 2016

updated – I  made this post more than a year go when I encountered an issue doing maintenance on Exchange Server 2013. Coming from Exchange 2010 maintenance experience it was a quite a different change and for some time I was not sure why the service were not coming backup online. And then it was all related to Exchange 2013/2016 Managed Availability. When I looked it up (only possible via Powershell) I fond that all the services were in InActive State.

You can also use the script to bring the component state back to active state
http://gallery.technet.microsoft.com/exchange/SetExchangeComponentToActiv-874bcd4b

Original post from 08/7/2014
After applying update or patches on Exchange 2013/2016 and bringing back to out of maintenance you notice that server components are still Inactive as shown below.  In a situation like this you need to go extra mile to bring the server as is before maintenance. Below is the set of cmdlet when you put the server on maintenance where requester is calling for maintenance.

cmdlets/ script is bringing the server out of the maintenance but the component state is still Inactive
Set-ServerComponentState $Server -Component ServerWideOffline -State Active -Requester Maintenance
Set-ServerComponentState $Server -Component UMCallRouter –State Active –Requester Maintenance
Resume-ClusterNode $Serve
Set-MailboxServer $Server -DatabaseCopyActivationDisabledAndMoveNow $False
Set-MailboxServer $Server -DatabaseCopyAutoActivationPolicy Unrestricted
Set-ServerComponentState $Server -Component HubTransport -State Active -Requester Maintenance

maint1

In addition to the single components which can be managed individually, there’s also a component called “ServerWideOffline”, which is used to manage the state of all components together, with the exception of “Monitoring” and “RecoveryActionsEnabled”. For this purpose, “ServerWideOffline” overrides individual settings for all other components. It doesn’t touch “Monitoring” and “RecoveryActionsEnabled” because these two components need to stay active in order to keep MA going. Without them, no “OnlineResponder” could bring “ServerWideOffline” back to “Active” automatically. But in this case both Monitoring and RecoveryActionEnabled are Inactive which will not bring the ServerWideOffline back to Active.

 So the server is not 100% functional even though you took it out of maintenance. You will need to perform  the following cmdlet to bring the server in ACTIVE State

Set-ServerComponentState -Component ServerWideOffline -State Active -Requester Functional
Set-ServerComponentState -Component Monitoring -State Active -Requester Functional
Set-ServerComponentState -Component RecoveryActionsEnabled -State Active -Requester Functional

maint2

 

You can also get  the Get-ServerComponentState cmdlet from the Shell to retrieve these settings along with timestamp

maint7

You can also use the script to bring the component state back to active state

http://gallery.technet.microsoft.com/exchange/SetExchangeComponentToActiv-874bcd4b