Transport routing in Exchange hybrid deployments

What is centralized transport?

If you already have heavily invested in your on-premise mail gateways and other infrastructure and you plan on moving to Office 365, Exchange Hybrid is the way to go in a long haul. When you have Exchange 2016 configured for Hybrid Setup with Office this where it come. 

So Why Centralized Transport?

It all depends on your business requirements, and if you don’t then you are good with regular setup routing via Office 365 , let’s cloud manage it for you. IF YOU DO HAVE such as regulatory and compliance requirements and even for other purpose where you want you emails MUST  route through your on-premises infrastructure then you need to configure it this way. In this video I will walk you over how does it really work.

Route mail through the on-premises organization for both on-premises and Exchange Online organizations

Outbound Messages from on-premises to Internet recipients

Exchange 2013/2016 Installation will be BLOCKED If?

Yes this will happen in Jun ’18 release of Exchange cumulative update and after that If your system does not meet requirements which included .NET Framework 4.7.1 it would not allow to you install either exchange 2013 or Exchange 2016.

So make sure in the next few months you do testing in your lab environment and make sure it goes through you change management process (if any) and get the system ready. This is major update. At this point it not clear how or what will happen if you have existing Exchange 2013/2016 without .NET Framework 4.7.1 and new Servers installed after June ’18 with .NET 4.7.1.

I will update this post as soon as I hear back from Exchange product team, till then stay tuned.

Exchange Team Blog

https://blogs.technet.microsoft.com/exchange/2017/12/19/released-december-2017-quarterly-exchange-updates/

Recent Release

KB articles that describe the fixes in each release are available as follows:

Reminder for Hybrid

In hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the most current (e.g., 2013 CU19, 2016 CU8) or the prior (e.g., 2013 CU18, 2016 CU7) Cumulative Update release.

Hybrid free/busy lookups fail between Exchange Server 2016 CU8 and O365

Microsoft has identified a condition where Free/Busy lookups from On-Premises to O365 in a hybrid configuration may fail.

 

Symptoms

After you install Microsoft Exchange Server 2016 Cumulative Update 8 (CU8), free/busy queries from Microsoft Office 365 users to on-premises mailboxes in hybrid environments fail if the cloud mailboxes are not archive-enabled.

Cauase

This problem occurs because of a known issue that affects OAuth connectivity in Exchange Sever 2016 CU8.

Workaround

To work around this issue, create personal archive mailboxes for each cloud mailbox.

Status

This problem is scheduled to be fixed in Microsoft Exchange Server 2016 Cumulative Update 9 (CU9). For a supported fix for CU8, contact Microsoft Support.

It is time to upgrade – End of life Exchange 2007

Exchange 2007 End of Life Roadmap

Do you know that April 11 2017 is the date when Exchange 2007 will no longer be supported by Microsoft.

If you haven’t already begun your migration from Exchange 2007 to Exchange 2016 or Office 365 now’s the time to start your planning.

What does End of Life mean?

Exchange Server, like almost all Microsoft products, has a support lifecycle during which we provide new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the date of the product’s initial release, and the end of this lifecycle is known as the product’s End of Life. When Exchange 2007 reaches its End of Life on April 11, 2017, Microsoft will no longer provide:

  • Technical support for problems that may occur;
  • Bug fixes for issues that are discovered and that may impact the stability and usability of the server;
  • Security fixes for vulnerabilities that are discovered and that may make the server vulnerable to security breaches;
  • Time zone updates.

Your installation of Exchange 2007 will continue to run after this date. However, because of the changes listed above, we strongly recommend that you migrate from Exchange 2007 as soon as possible.

Benefits of upgrading to Exchange 2016

Simpler and Better Server Architecture – Single Server Role
Better Collaboration
Saving files to OneDrive for Business
Uploading a file to OneDrive for Business.
Most Recently Used lists populated with both local and online files.
Office 365 hybrid
Messaging policy and compliance
In-place Archiving, retention, and eDiscovery
Improved performance and scalability
Auditing
Antimalware protection
Integration with SharePoint and Skype for Business

What are upgrade options?
#1-You can migrate to Office 365
#2- If you don’t want to migrate to cloud then you can upgrade to either Exchange 2010, Exchange 2013 or Exchange 2016.

I still have more questions, where do I get more details?
Follow this url – https://support.office.com/en-us/article/Exchange-2007-End-of-Life-Roadmap-c3024358-326b-404e-9fe6-b618e54d977d

 

 

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