Update on Windows Server 2016 and Exchange Server 2016


Update 12/13/2016: Please see the December 2016 Quarterly Exchange Updates blog post for updates on this subject.

We wanted to raise your attention to an issue that some customers have reported running Exchange Server 2016 on Windows Server 2016. Crashes of the IIS (W3WP.exe) process have been reported causing instability of Exchange Server on Windows Server 2016. The Exchange team has worked with the Windows team to isolate the source of the problem. An update for Windows Server 2016 will be made available to resolve this issue. Microsoft recommends that customers delay deploying Exchange Server on Windows Server 2016 until this update is made available. For the latest guidance on known issues, please consult the Windows Server release notes on TechNet.

When there are updates on this, we will update this blog post.

The Exchange Team

Comments (40)
  1. Benoit Boudeville says:

    Gotcha! Nice to see that some our feedbacks may be useful sometimes… :)

  2. sime3000 says:

    Hello Exchange Team,

    Thanks for this informative post. While we’re on the subject of Exchange 2016 on Windows 2016 …

    UCMA 4.0 is listed as a prerequisite for Exchange 2016 on Windows 2016 https://technet.microsoft.com/en-us/library/bb691354(v=exchg.160).aspx

    However UCMA 4.0 was released four years ago and is clearly not supported on Windows 2016 according to the UCMA 4.0 requirements on this page https://www.microsoft.com/en-us/download/details.aspx?id=34992

    So how is UCMA 4.0 a supported prerequisite for Exchange 2016 on Windows 2016 ?

    Looking forward to your timely response Exchange Team.

    1. The link that you referenced is indicative of the operating systems which were available at the time the download was created. It is noteworthy that it does not reference Windows Server 2012R2, also a supported operating system for Exchange Server 2013 and 2016. The Exchange team has confirmed that UCMA installations meet the requirements of Exchange on all supported operating systems. The Lync team, which creates the UCMA package, has not informed us of any problems supporting UCMA with Exchange on any of our supported operating systems.

  3. Thanks for the heads up. Any guidance for customers who are impacted by this issue?

    1. Benoit Boudeville says:

      @Jetze: I’m not Microsoft, but a workaround I used (and worked in my case) was to stop and disable the MSExchangeHM service. Since there is now a MSExchangeHMRecovery service, you’d need to also stop and disable this one before, or it will re-enable the MSExchangeHM again (and then kaboom again).

      1. Disabling the MSExchangeHM service is not recommended

        1. yacoob says:

          Neither is w3wp crash. But what else to do while waiting for a fix?

        2. Hi Frank,
          thanks for the information that disabling the MSExchangeHM service is not recommended. But what is the guidance on customers who are impacted by the issue – this was the initial question!

    2. Rob Hardman says:

      The official advice (currently) is to run on WS2012R2 until the patch becomes available. I recommend you migrate your mailboxes away until that time. (NB: I’m not Microsoft.)

      Technet discussion: https://social.technet.microsoft.com/Forums/office/en-US/142ff1ab-242c-4436-a870-068720b5580f/exchange-server-2016-windows-server-2016-datacenter-iis-apppools-constantly-crashing?forum=Exch2016PS

    3. There currently is no workaround for this problem. Exchange Server will install on Windows Server 2016 cleanly and appear healthy until the first reboot after creating/joining a DAG. Customers should avoid installing Exchange Server on Windows Server 2016 until a supported update for Windows Server 2016 is available. Customers whose production environment is impacted are encouraged to replace Windows Server 2016 with Windows Server 2012R2 if they cannot wait for the update.

      1. We have the exact same issue and a support ticket open with you. Everything works till I reboot. We eagerly await an update on this issue.

  4. This is significantly impacting our High Availability Deployment.

  5. Thank you for the update.

  6. Magnus says:

    If running a standalone Exchange 2016 on WS2016 without DAG, there should be no issues?

    1. Eliseo Villafuerte says:

      Yes, no issue when Windows 2016 is used to deploy Exchange 2016 CU3 in non-DAG configuration. So I deployed on WS2012R2 to enable HA. Will wait patiently for the fix.

  7. sime3000 says:

    Hello Exchange Team,

    Thanks for this informative post. While we’re on the subject of Exchange 2016 on Windows 2016 …
    UCMA 4.0 is listed as a prerequisite for Exchange 2016 on Windows 2016 https://technet.microsoft.com/en-us/library/bb691354(v=exchg.160).aspx

    However UCMA 4.0 was released four years ago and is clearly not supported on Windows 2016 according to the UCMA 4.0 requirements on this page https://www.microsoft.com/en-us/download/details.aspx?id=34992

    So how is UCMA 4.0 a supported prerequisite for Exchange 2016 on Windows 2016 ?

    Looking forward to your timely response Exchange Team.

  8. H Shakir says:

    Thanks, this will resolve many customers issues, people are reluctant to start new deployments.

    1. grant says:

      testing =(

  9. Brian H Laws says:

    Thank you for the alert! We were just about to deploy Exchange Server 2016 on Windows Server 2016, so this was perfect timing. We’re eagerly waiting for the patch.

  10. Troubleshooter_73 says:

    Tested and we can confirm the issue, like mentioned above, only if we deployed a DAG.
    We fixed it by deploy another Exchange (because we don’t get back any access to the Org by EMC nor EAC) and removed the DAG completely from the third Stand Alone Exchange Server. After Reboot the old DAG Master, we was able to access the Exchange Management and we balanced the mailboxes between two Exchange Servers without DAG. Just a workaround but it works hopefully until the fix is online…

  11. Michael says:

    Hi Exchange Team. Any update on this one? Timeline you can share with us? Can we expect a fix to be included in the Dec rollup for Windows Server 2016? Thanks and BR Michael

  12. DominikP says:

    Hello Guys,

    is there an update on this issue?

    Will the fix come in Dec. 2016?

    Thanks and kind regards,
    Dominik

  13. D.Paebst says:

    Good Morning,

    is there anything new on this issue.

    Can we count on a Patch in December?

    Thanks and kind regards,
    Dominik

  14. Ole says:

    Still now news on this topic?

  15. Eric says:

    Hello Team,
    do you have any news for us, who need to migrate many mailboxes to EX2016 on Server 2016 until mid December? :-)
    Thanks and regards

  16. sime3000 says:

    Speaking of Windows Server 2016 and Exchange Server 2016…

    The current version of Jetstress clearly does not list Windows 2016 as a supported operating system. https://www.microsoft.com/en-us/download/details.aspx?id=36849

    For those of us that are currently deploying this combination, when exactly should we expect the version of Jetstress that will officially support Windows 2016 ?

  17. CHDV-LWAG says:

    Hi Exchange-Team,

    is there any Update on this topic? Any date for a fix?

  18. Ben says:

    Is there an update on this issue, I find it concerning that a number of people have asked for an update and there hasn’t been one.

  19. Jan Bukal says:

    One month is gone and no one info or update?
    (Info like “no patch until Q2 2017” would be a very helping info!)

  20. Marcos says:

    Waiting the update !!

    1. mahabub alam says:

      windows bakup

  21. sime3000 says:

    Hello Exchange Team (second request),

    Speaking of Windows Server 2016 and Exchange Server 2016…

    The current version of Jetstress clearly does not list Windows 2016 as a supported operating system. https://www.microsoft.com/en-us/download/details.aspx?id=36849
    For those of us that are currently deploying this combination, when exactly should we expect the version of Jetstress that will officially support Windows 2016 ?
    Thanks!

  22. LukeF says:

    any estimated time frame when the update fix will be made available? 1 month, 3 months? need this info to determine our next course of action

  23. rdexch says:

    Exchange Team: Where do we stand here? Christmas present ready?

  24. sime3000 says:

    Hello Exchange Team (third request),

    Speaking of Windows Server 2016 and Exchange Server 2016…
    The current version of Jetstress clearly does not list Windows 2016 as a supported operating system. https://www.microsoft.com/en-us/download/details.aspx?id=36849
    For those of us that are currently deploying this combination, when exactly should we expect the version of Jetstress that will officially support Windows 2016 ?

    Thanks!

    1. paolod says:

      We’re considering Server 2016 for our Exchange 2016 installation. Did the update resolve the issues?

Comments are closed.

Skip to main content