Exchange Server 2019 Now Available

We’re pleased to announce the final build of Exchange Server 2019 is now available and can be downloaded from the Volume Licensing Service Center.

Exchange Server 2019 is designed to deliver security, performance and improved administration and management capabilities; attributes our largest on-premises customers expect from Exchange.


If you haven’t yet seen the session delivered at Microsoft Ignite 2018 we suggest you watch the video and download the slides here. During that session we talked for the first time about how the code paths between on-premises and online have separated, and the impact to on-premises customers – in short, less code churn and more stability.

Here is a selection of other key features in Exchange Server 2019:

Security: Exchange Server 2019 requires Windows Server 2019. In fact, we recommend installing Exchange Server 2019 onto Windows Server 2019 Server Core. Exchange Server 2019 installed on Windows Server 2019 Core provides the most secure platform for Exchange. You also have the option of installing Exchange 2019 onto Windows Server 2019 with Desktop Experience, but we have worked hard to make sure running Exchange on Server Core is the best choice for our code.

We’re aware all media for Windows Server 2019 and Windows Server, version 1809 has been temporarily removed and Microsoft will provide an update when refreshed media is available. Exchange Server 2019 will be fully compatible with version 1809, and the refreshed version.

We also built Exchange Server 2019 to only use TLS 1.2 out of the box, and to remove legacy ciphers and hashing algorithms. To understand how this affects coexistence with earlier versions, please reference our previous series of posts on TLS.

Performance: We’ve done significant work to allow Exchange Server to take advantage of larger core and memory packed systems available in market today. With our improvements, Exchange Server can use up to 48 processor cores and 256GB of RAM.

We’ve re-engineered search using Bing technology to make it even faster and provide better results, and in doing so have made database failovers much faster, and administration easier.

We’re adding dual storage read/write capabilities to Exchange Server 2019 using Solid State Drive (SSD) technology to provide a super-fast cache of key data for improving end user experience. We also talked about this in our Email Search in a Flash! Accelerating Exchange 2019 with SSDs session at Ignite.

We also changed the way database caching works to allocate more memory to active database copies, again improving the end user experience. You can learn more about Dynamic Database Cache from Welcome to Exchange Server 2019! video and slides.

The improvements we have made to Exchange Server 2019 will enable you to scale to a larger number of users per server than ever before, use much larger disks, and see the latency of many client operations being cut in half.

End user experience: We all rely on Exchange for calendaring, and we know large enterprises are heavy calendar users. We are bringing a few key features such as restricting the forwarding of meeting requests and better control over OOF settings to Exchange Server 2019. Administrators get some new calendaring features too, as we’re adding the ability to manage events on user’s calendars and assign delegate permissions more easily.

We are also adding support for routing mail to and from EAI/IDN recipients and hope to add additional capabilities in this area in the future.

The session recording also goes into some of the other features we have plans for, so make sure you watch it to the very end.

As we mentioned in the Preview post in July, the Unified Messaging role will not be available in Exchange Server 2019. Customers who currently connect either a 3rd party PBX or Skype for Business Server to Exchange Server won’t be able to do so with Exchange Server 2019 mailboxes. Those customers considering an upgrade to Exchange Server 2019 should consider migrating to Skype for Business Server 2019 and using Cloud Voicemail, or migrating to Office 365 with Cloud Voicemail.

Our official product documentation is now live, and we’ll be publishing the updated Preferred Architecture documentation soon.

We’re also pleased to also announce there are even more Office Server products releasing today! You can read more about those releases here.

We look forward to your feedback and thank you for your continued support and love of Exchange.

The Exchange Team

Comments (85)
  1. @ExchangeTeam Would you please provide guidance on when to upgrade from Exchange 2016 CU11 to Exchange 2019 in an Office 365 hybrid environment? Thanks.

  2. @Jeffry – Both Exchange Server 2016 Cumulative Update 11 and Exchange Server 2019 are fully supported with Office 365 hybrid today. We will continue to support both Exchange versions over their respective lifecycles using latest cumulative updates. The decision to upgrade to a particular version of Exchange is based upon the needs of your organization.

    1. Dmitry Alferov says:

      Is any trouble with coexistence with Exchange 2013 ?

      1. @Dmitry – As long as you are running the latest cumulative update for Exchange Server 2013, there are no problems co-existing with Exchange Server 2019 or Office 365 Hybrid.

  3. Michael says:

    Is there a trial version available

    1. @Michael – Right now there is no trial download available. Customers who download theproduct from the Volume License Center can install the product in evaluation mode prior to licensing the server.

  4. Simon says:

    According to the documentation, the Mailbox role still doesn’t support the Connection Filtering anti-spam agent. Sincerely hope this will be supported with a future update…

  5. Euclid says:

    On Windows Server 2019 Core, Unified Communications Managed API 4.0 Runtime fails to install. The error log says:
    0320.08A8::10/23/2018-14:43:43.024 Log file opened.
    0320.08A8::10/23/2018-14:43:43.024 LOGGING STARTED
    0320.08A8::10/23/2018-14:43:43.024 Creating data folder.
    0320.08A8::10/23/2018-14:43:43.040 64 Bit Setup is running, checking for NOX86
    0320.08A8::10/23/2018-14:43:43.040 NOX86 length : ‘0’
    0320.08A8::10/23/2018-14:43:43.040 Checking preconditions.
    0320.08A8::10/23/2018-14:43:43.055 GetLibraryVersion for shdocvw.dll failed.
    0320.08A8::10/23/2018-14:43:43.055 Getting ready to exit.
    0320.08A8::10/23/2018-14:43:43.055 Deleting temporary setup files
    0320.08A8::10/23/2018-14:43:45.014 ENDED LOGGING

    This can clearly not work because shdocvw.dll is not part of the Windows Core product.

    1. @euclid Are you installing UCMA 4.0 from the Exchange Server 2019 media?

      1. Euclid says:

        No. I used the url from the error message during the Exchange Setup. Maybe the url/message in the prerequisite check should be corrected then.

        1. @Euclid – We have this called out in our documentation at We have heard your feedback on the URL being provided, which is accurate for Desktop Edition but not Server Core. We will look to improve the experience here.

  6. supcxc says:

    I tried to install it on Win2019 preview version. It reported error:
    “An unsupported operating system was detected. Exchange Server 2019 Mailbox and Edge Transport server roles support Windows Server 2019 or later.”

    Win2019 official version is not available yet. How can we try Ex2019? Do we have to wait for Win2019?

    1. @supcxc – Yes we require the RTM version of Windows Server 2019. Windows Server 2019 availability will be announced at

  7. EinmalIM says:

    When will the download be available for MSDN subscribers?

    1. EinmalIM says:

      Arrived at MSDN. Thank you.

  8. Coert K says:

    Hi great release! Is it already supported to deploy a hybrid configuration on a single Exchange 2019 Core installation?

    1. @Coert – It is fully supported to establish an Office 365 hybrid relationship with machines running Windows Server Core. You will need to run the Hybrid Configuration Wizard from a Windows 10 client or server with Desktop Edition installed as the wizard requires a browser to launch.

  9. Christian Schindler says:

    Hello, somehow I’m unable to find Information in the Docs about MCDB deployment and planing. Is this already available or something that takes a while to appear? Thanks Christian

    1. @Christian – Thanks for your interest in Exchange Server 2019. We are still putting the finishing touches on the cmdlet reference topics and guidance. We should have this available soon.

  10. Dean Scully says:

    I’d recommend better timing with your software releases.

    Without Windows Server 2019, whats the point of releasing Exchange 2019!

    1. Spadster says:

      OK…. my apologies.

      Windows Server 2019 was released on October 2, and was removed due to the 1809 update issue.

      No issues with Exchange 2019 release dates, just an issue with me.

  11. Ashish says:

    Wow…Exchange 2019 only supported on Windows 2019. But where is Windows 2019. Also what is point of having it downloaded only from VLSC.

    Here is update on windows 2019 from Microsoft site.

    We have temporarily removed all media for Windows Server 2019 and Windows Server, version 1809. We have also paused the rollout of the latest feature update to Windows 10 inclusive of versions 1809, as we are investigating isolated reports of users missing some files after updating. If you have already downloaded media, please don’t install it and wait until more information is available to proceed. We apologize for any inconvenience this may have caused. We will provide an update when refreshed media is available. For reference, we also have a support article with additional information.

  12. Pierre Maier says:

    Bloody brilliant.

    Cant wait to get my hands on some of that action.


  13. Michael Walker says:

    Just completed a phased migration from Exchange 2007 on Windows Server 2008, to Exchange 2016 on Windows Server 2016. Just purchased licenses/cals in April. Any upgrade incentives? Utilities to automate the migration from Exchange 2016?

  14. Michael Walker says:

    Just completed a phased migration from Exchange 2007 on Windows Server 2008, to Exchange 2016 on Windows Server 2016. Just purchased licenses/cals in April. Any upgrade incentives? Utilities to automate the migration from Exchange 2016?

    1. Martin Aigner says:

      Exchange 2019 will be available only to Volume License customers Michael. As Exchange 2016 is still fully supported for several years now is the right time starting your planning activities moving to O365.

      1. Trevor says:

        Unless we have no plans to migrate to Office 365…

        1. MarcK4096 says:

          Then you can start planning your migration to a Linux mail server and Open Office for when Microsoft stops releasing Exchange and Office perpetual.

  15. Donald Bensen says:

    I’m considering moving from Exchange 2010 on premises to a Exchange 2019 hybrid model. Can you point me to documentation to implement such a configuration? Thank you.

    1. @Donald – Exchange 2010 and Exchange 2019 cannot co-exist in the same Active Directory forest. Your path forward is going to be a two-step migration. The first would be to move from Exchange 2010 to 2016 and then Exchange 2016 to 2019. I would recommend completing the Exchange 2016 migration before implementing hybrid. Overlapping migrations is not a great place to be in. The following link is a good starting point for understanding hybrid deployment,

  16. Hamdy Marzouk says:

    When you can install ?

  17. Grimson says:

    Varies depending on Exchange roles that are installed:
    • Mailbox: 128GB minimum recommended
    Uhm what about this??

    1. @Grimson – As we discussed at Ignite 2018, we have made many enhancements in memory allocation and usage in Exchange Server 2019. In order to realize all of those we are recommending 128GB as the minimum for the mailbox role. The product will not enable all of the new functionality if less memory is used.

      1. umaplu says:

        Hello, can you please clarify ” will not enable all of the new functionality if less memory is used.” ?
        Is 128GB ram needed for anything else then new garbage collector?
        We are planing deployment with 20GB of RAM for forty users …Thanks

        1. @UMAPLU – Below 128GB you will not get any of the benefits of garbage collection improvements. You will also likely not derive any benefits from cache improvements with such a low memory footprint.

      2. Marc K 4096 says:

        128 GB seems quite reasonable for an Exchange server for a large organization. What makes the 128 GB minimum shocking is that the Exchange 2016 minimum recommended memory is only 8 GB.

        128 GB would be way overkill for an organization with 10 mailboxes. But, I guess the official recommendation would probably be for a customer like that to use Exchange Online.

  18. Joerg Schwerdtfeger says:

    When will the download be available for MAPS subscribers?

    1. @Joerg – There are no plans to distribute via this channel at this time.

    1. MitchMG says:

      Hybrid Configuration Wizard says I have Exchange “ beta”! ;-)

      1. @MitchMG – Thank you for the feedback. We will follow up with the HCW team.

  19. EinmalIM says:

    I was able to upgrade my Exchange 2019 preview installation which I installed on Windows Server 2016 – so for me Exchange 2019 works on Windows Server 2016. Strange prereq…

    1. @EinmalIM – What you are doing is not supported. You will need to redeploy this server onto Windows Server 2019 to be in a supported state.

      1. EinmalIM says:

        It is just a test server. Will I be able to upgrade the Windows Server 2016 to 2019 inplace?

        1. @Einmallm – In place upgrade of the OS while Exchange installed is a new feature that will be supported with Windows Server 2019 to later OS’es only.

    2. Thank You for this workaround. Brilliant.

  20. Logan Burt says:

    The admin tools for calendar management sound great!

    Are there also any tools to simplify Exchange admins managing user permissions to mailbox folders?

    1. @Logan – Thanks for the feedback. At this time there are no investments in this area.

  21. Yoda says:

    when there will be support for Windows Server 2016?

    Our investment of 100.000 bucks and more is gone now, 2016 is crap from now on?

    Support lifecycle states some years left for 2016.

    Ok, at least we can still install notepad++ on our expensive on premises licenses for W2016, great deal!

    1. Aaron R says:

      Exactly. This is pure CRAP – We literally mortgaged our company to upgrade to 2016 and their extortionate per-core gouging model last year, plus exchange 2016 with software assurance, but I find it very convenient that a 2 year old OS isn’t supported for this? And 128gb ram requirements for MB servers? You must be joking.

      All this, the bungled timing of releasing it prior to the required OS, not being available in trial or to MAPS, losing UCM, and the “new” crippled version of on prem Office are clear indications that Microsoft is deliberately forcing everyone out of “you own it” infrastructure, and in the process killing the IT industry that supported and built them up in the first place.

      We are not amused.

  22. Seth Killey says:

    Hi Brent, thanks so much for your excellent presentation at MS Ignite. As a non-profit, SMB, I’d love to move to Office 365 for Exchange Online, especially with the upcoming 128 GB minimum recommended RAM for Exchange 2019 which is a budget buster for us. We’re only 118 mailboxes on Exchange 2013. I really hate the idea of having anything on-prem, but would love to have synced identities and passwords via Azure AD Connect. My understanding is this is not possible with cutover migration which would allow me to decommission my lone Exchange on-prem server. Is there any hope this can or will be changed? Like a selective Azure AD Connect that only views the on-prem AD as authoritative for identity and password, but let’s Exchange Online manage the Exchange Attributes? Thanks for your help from an itty bitty customer who works for an awesome non-profit. I really hate the idea of doing an unsupported ADSI edit

    1. @Seth – Thanks for the feedback. We are constantly trying to improve the experience for pure cloud management where customers transition from on-prem and want to remove on-prem dependencies. Nothing to share at this point, but we have heard your concern, are aware and looking for solutions.

      1. yoda says:

        hehe, care for cloud customers, but not for on prem customers, which paid a lot of money, too?

        That is the gift for true customers since 20 years, made you great.

        OK, when there will be support for Windows Server 2016?

        As a large IT company we could also consider skipping MS products for our customers and us, and Domino is still alive.

        Cloud is no alternative, it never will be for many. So we still demand support from a company we pay.

  23. Jim Kuterbach says:

    Can someone provide a link to CU1 for Exchange 2019
    I have been running it since D+1 and am still fighting my way through with all the powershell it requires.
    I cannot RDP into this server.

  24. So in scenario where all mailboxes are hosted in 365, and with AD sync in place, for customers who wanted to get rid of their on-prem Exchange infrastructure I normally recommended to build single Exchange 2016 server with minimum spec purely for user management (with Hybrid licence provided by MS). With 128GB RAM minimum requirement for 2019 i guess that is out of the window and I would have to recommend them to stick to 2016 instead of “latest and greatest” ?

  25. mark49808 says:

    Any word on the Preferred Architecture and Exchange Server Role Requirements Calculator? Very difficult to start to plan for this without those available.

  26. Now just release a new version of the calculator.. … And Windows Server 2019…

  27. VOND says:

    Product lifecycle web site is showing extended support until 10/14/2025. Only 7 years instead of 10 years? Is this a typo or is there a reason for the shorter lifecycle?

  28. Sandheep says:

    When will you release Exchange 2019 Storage Calculator ?

  29. Ajikps says:

    Any word on the PA and sizing calculator?

      1. Ajikps says:

        There it is! Thanks Mark, for the draft.

  30. JuhaAaaaaaa says:


    Could you ask your team to fix for “requirements” of the OS/system locale to be set to US-english for the exchange 2019 installation to start?

    1. We’re not aware of any issues in this area – we test this and haven’t seen issues. Are you sure your locale support is correctly set up? If you are we suggest you open a case.

  31. Cannot get a Hybrid Edition Product Key for Exchange Server 2019 using HCW, just get an error message that “Failed to get product key for Version 15.2 (Build 221.12)”

    1. We are not providing a free key for Hybrid purposes for 2019. You need a full server license, or to use 2016 for Hybrid.

      1. I have heard about the Azure App Proxy based solution coming called Hybrid Agent in Hybrid Configuration Wizard which is good for easing publishing on premises Exchange for Hybrid, but if Exchange 2016 is the last version of to get Hybrid key benefit, what happens when in 2020 at the end of Exchange 2016 mainstream support? Are Microsoft going to address Hybrid somehow with a way to manage things without an Exchange server with management from online, or even on premises? Hybrid Exchange management with an on premises connector integrated with AADConnect functionality (possibly)… Or is Exchange 2016 support going to be extended for Hybrid use, or are customers going to have to licence Exchange 2019 to continue with Hybrid? I understand that you probably don’t have the answers to all these questions yet. I am just wondering what is the strategy going forward for Hybrid.

        1. Exchange 2016 extended support lasts until 2025, so there’s some ways to go on that yet. And of course 2019 can be used for Hybrid connectivity with a license – the only change here is that we’re not giving away a free license for 2019 as we did for earlier versions – but a paid license will work fine.

          We’re doing lots of work on the Agent, and the long term management story, and we’ll explain that in time, the comments section of this post probably isn’t the best way to communicate that story – we’ll have more on the Agent early in the next year.

  32. Ted Wagner says:

    This makes no sense to me, “Exchange Server 2019 requires Windows Server 2019. In fact, we recommend installing Exchange Server 2019 onto Windows Server 2019 Server Core. ”

    If Exchange server 2019 is available NOW, and Windows Server is NOT available now….

    1. Ted, Windows Server 2019 is available now.

      1. Satyajit321 says:

        But neither Windows 2019 or Exchange 2019 download\evaluation\preview links works.
        Any options for standalone downloads.

        1. Both are available via VLSC, and should also be on MSDN too.

  33. JanF3 says:

    @ExchangeTeam – I tried to install Exchange 2019 RTM on Server 2019 Core Windows_InsiderPreview_Server_en-us_18282 – But I cant install UcmaRuntimeSetup – Error – GetLibraryVersion for shdocvw.dll failed.
    Any suggestions? The file is completely missing on the Server Core build.
    thx in advance!

    1. When you install Exchange on Windows Server Core, you must use the installation package located in \UCMARedist on distributed media.
      Explain here:

  34. PowerofGods says:

    Hi All, we have a n1-standard-4 with 15GB Memory included, can we deploy an Exchange Server 2019 for training purposes?

  35. Ken Brussel says:

    Can you post the Exchange 2019 Preferred Architecture as a blog post?

  36. Ghanendra says:

    After a long time finally got it. Is there any trial version?

  37. CHI-LTD says:

    To confirm (as we are running exchange hybrid with exchange 2010), we can upgrade to exchange 2019 without migrating to 2016 first? Also are you offering the free exchange on premise licences still? NB all mailboxes are in exchange online.

  38. slvrfxms says:

    How will the support model work for those loading Windows Server 1809 versus Windows Server 2019 LTSB? Will Exchange be fully supported in the new Windows Server servicing model with the semi-annual channel updates or will LTSB be required?


  39. v.bohatikov says:

    I’ve got a question about new options for Out of Office feature. They are already works on Exchange Online, but on Exchange 2019 they are unavailable. Microsoft’s documentary says that new options are available in Exchange 2019, you can see this in “Calendar – Better Out of Office” section on
    When I say that they are unavailable I mean that documentation of Set-MailboxAutoReplyConfiguration says that new options are available only on Exchange Online and when I try to use these options I get next error: “A parameter cannot be found that matches parameter name “.
    Do you know some thing about that? Or maybe I do somesing wrong?

  40. Hexamail Guard Antispam for Exchange 2019 will still operate with this version using Powershell integration.

  41. Hi gentlements,
    Do you have any news about Exchange role requirements calculator for Exchange 2019?

  42. Hello,

    can you give an approximate release date for a new version of the Exchange Server Role Requirements Calculator, that will cover Exchange 2019?

    Thank you in advance for your reply & best regards,


    1. Ken Brussel says:

      @ExchangeTeam – any chance of the updated calculator being released? I can’t possibly plan my deployment effectively considering MCDB and other requirements without it! :(

Comments are closed.

Skip to main content