Blog Post

Exchange Team Blog
1 MIN READ

Exchange Server 2019

The_Exchange_Team's avatar
Oct 02, 2017

We wanted to post a quick note on our blog to mention to all that at Microsoft Ignite 2017 we have announced that we will be releasing Exchange Server 2019 as an on-premises release to our customers.

We are looking forward to sharing more details about this release with you in calendar year (CY) 2018. We expect to release a preview in mid CY 2018 with the final release near the end of CY 2018. Please review our TAP program post, as we will be looking for more customers to help us validate this release!

The Exchange Team

Updated Jul 01, 2019
Version 2.0
  • we're still on Exchange 2013 and just planning to move to Exchange 2016 and then this!?

    can users jump directly from 2013 cu17 to 2019 when it's available?

    • Deleted's avatar
      Deleted
      I guess so (and I hope so), as microsoft has always done a 3 versions compatibility...
  • We're waiting for any events about Exchange 2016 and 19. May I know if there is any newsletter or other ways we can subscribe to get latest news ?
  • please lord no, we just moved to exchange 2016 and the head banging has been nothing if not monumental, were using onsite and linking with OneDrive for Document Collaboration has been well frankly impossible, a whole load of functionality was removed in 2016 what will 2019 be like, I sorry but we need time to heal.
  • I am all for on-prem. The Exchange Online is not cloud (virtualization) . It is SaaS. It has many regulatory shortcomings and is more costly to sustain for medium-sized and large businesses with large mailbox and realtime access to retired mailbox data. Also, good luck with managing backups. Overall, it costs more to run Exchange Online using full enterprise contigencies than on prem.
  • Oh god. This post means that at some point in the future, it won't be on premise software. Jesus god no. If that happens I'm leaving IT. I'm getting my forklift license and working in a warehouse for the rest of my life. I've already transitioned to mostly network engineering because of this kind of garbage. It all started when MS cut off TechNet. The moment they did that, I bought a couple books and got my CCNA about two months later. I guess I have to give Microsoft credit for not being at all subtle that if you're still invested in a career based on their technology, you're going to be out of a job before Trump is.