#MSiGnite 2016 Post Keynote Day2 Sessions

The day 2 has just started and I’m going post more blog post but short post and it will cover the highlight to give you (readers) the idea what’s going here 🙂

The first session i attended was on Collaboration with Office 365. 
Speaker – Kady Dundas – and Dan Holmes

This Office 365 sessions explained how can an organization be more effective and productive leveraging features such as Office 365 Group/OutlookYammer, Smart File Attachment using OD4b. One of the most use case of Office 365 Group v/s Distribution Group where Distribution Groups members email back and forth and there no conversation history other than the mailboxes of the distribution group members and users end up using really all in some cases. Also a tedious task if someone new joins the team, Office 365 Group solves that issue.

Office 365 groups were also covered #Millennial , where these groups can be leveraged for contractor and Millennial , since Millennial like social networking and Office 365 are work very well with Yammer too.  Office 365 Group can be configured Public and Private.

Smart attachment of a document using OD4B, Document co-authring and Chat feature in the document (possible with Skype) and Sharepoint Dashboard were also the part of this session. I’m not sure if this event is going to be repeated and if not then watch a recorded session

http://ignite.microsoft.com

Collaboration with Microsoft Office 365

 

Online Document Editing (Office Online Server 2016) Failed with On-Prem Exchange 2016 Server

Screen Shot 2016-07-22 at 4.44.30 PM

If you have setup an Office Online Server 2016 with Exchange Server 2016 CU2, and if you are getting this error then there is something wrong with the configuration. It does not mean that your installation was wrong but during the configuration of Office WebApp Farm you forgotten to mention the Edit Option. So re-run the command with the Editing Enable and you will be done.

Screen Shot 2016-07-22 at 5.39.52 PM

PS C:> New-OfficeWebAppsFarm -InternalURL "https://oos.office365sme.com" -ExternalURL "https://oos.office365sme.com" -CertificateName "The Office 365 SME" -EditingEnabled -EditingEnabled

Screen Shot 2016-07-22 at 4.40.22 PM
Screen Shot 2016-07-22 at 4.55.30 PM


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

  • Windows Server 2008/2008R2 – KB3146716
  • Windows Server 2012 – KB3146714
  • Windows Server 2012R2 – KB3146715

(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

Thursday, August 17th 2017

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.