Don’t let your Exchange Hybrid to stop on April 15th

If you’re running Exchange 2013 and you’ve configured a hybrid deployment with Office 365, this post contains important information that might impact you. Please evaluate this information and take any necessary action before April 15, 2016.

On April 15 2016, the Office 365 TLS certificate will be renewed. This certificate is used by Office 365 to provide TLS encryption between Office 365 and external SMTP servers. The new certificate, which will help improve the security of mail sent to and from Office 365, will be issued by a new Certificate Authority and it will have a new Issuer and Subject.

This change has the potential to stop hybrid mailflow between Office 365 and your on-premises Exchange servers if one of the following conditions applies to you:

  • Your on-premises Exchange servers are running Exchange 2013 Cumulative Update 8 (CU8) or lower.
  • You’ve upgraded the Exchange 2013 servers that handle hybrid mailflow to Exchange 2013 CU9 or higher. However, since upgrading to CU9, you HAVE NOT re-run the Hybrid Configuration wizard (either from the Exchange Admin Center or via the direct download link).

If one of the previous conditions applies to your organization, hybrid mailflow between Office 365 and your organization will stop working after April 15, 2016 unless you complete the steps below.

Note: This only affects hybrid mailflow. Regular mailflow and TLS encryption is NOT affected.

How to keep hybrid mail flowing (MUST be completed before 4/15/2016) Continue reading Don’t let your Exchange Hybrid to stop on April 15th

Exchange development, a view from 2 years ago

Two years ago Tony Redmond spoke with Perry Clarke, the development chief for Exchange (both on-premises and cloud) to discuss the current state of Exchange and how its technology was likely to evolve. We know how the influence of the cloud has affected the way that product development occurs and how quickly things now happen. Indeed it is interesting to look back on how Exchange has evolved in the period.

Evening Club #21

As we settled a good tradition to get together nearly every 15th of each month – let’s go on.
October 15th, kl.1630-1830 is the next Club’s meeting date, and I propose to run it in my office.

Meeting topics:

  • Exchange 2016 wow!s 😀
  • Mail encryption in Office 365
  • How did you spend your summer (joke)

I guess Steinar is going to tell the story of their recent achievements with Windows Azure, I’ve heard they nearly committed the project. I will try to invite online a new member and our colleague – an Exchange Architect from Netherlands, would be nice if he can join us. And yeah, of course – bring your questions and challenges, it turned we often have utterly useful discussions all together. Welcome, pals!

Clone Exchange 2013 SMTP Receive connectors

It’s a Microsoft’s best practice to run every Exchange server role on 2 servers at least. So when you deploy a new HubTransport, or HubTransport+Mailbox server – you face a task to duplicate SMTP receive connectors for printers, devices and other services like MSSQL, monitoring and reporting, etc. Medium to large organizations can use several such connectors with dozens of IP addresses and ranges, so copying it manually from server to server is an ungrateful burden.

Here is a nice and sharp method to clone such connectors with all its configuration en masse. God bless Powershell 🙂
UPDATE: A full PS1 script is available for download in the TechNet Scripts Gallery.

Just a few Exchange Management Shell one-liners, that you can copy and run in your environment: Continue reading Clone Exchange 2013 SMTP Receive connectors