Home
%3CLINGO-SUB%20id%3D%22lingo-sub-606028%22%20slang%3D%22en-US%22%3EUpdate%20on%20Windows%20Server%202016%20and%20Exchange%20Server%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-606028%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%20class%3D%22alert%22%3E%3CSTRONG%3EUpdate%2012%2F13%2F2016%3C%2FSTRONG%3E%3A%20Please%20see%20the%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2016%2F12%2F13%2Freleased-december-2016-quarterly-exchange-updates%2F%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EDecember%202016%20Quarterly%20Exchange%20Updates%3C%2FA%3E%20blog%20post%20for%20updates%20on%20this%20subject.%3C%2FP%3EWe%20wanted%20to%20raise%20your%20attention%20to%20an%20issue%20that%20some%20customers%20have%20reported%20running%20Exchange%20Server%202016%20on%20Windows%20Server%202016.%20Crashes%20of%20the%20IIS%20(W3WP.exe)%20process%20have%20been%20reported%20causing%20instability%20of%20Exchange%20Server%20on%20Windows%20Server%202016.%20The%20Exchange%20team%20has%20worked%20with%20the%20Windows%20team%20to%20isolate%20the%20source%20of%20the%20problem.%20An%20update%20for%20Windows%20Server%202016%20will%20be%20made%20available%20to%20resolve%20this%20issue.%20Microsoft%20recommends%20that%20customers%20delay%20deploying%20Exchange%20Server%20on%20Windows%20Server%202016%20until%20this%20update%20is%20made%20available.%20For%20the%20latest%20guidance%20on%20known%20issues%2C%20please%20consult%20the%20Windows%20Server%20release%20notes%20on%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Fwindows-server-docs%2Fget-started%2Fwindows-server-2016-ga-release-notes%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ETechNet%3C%2FA%3E.%20When%20there%20are%20updates%20on%20this%2C%20we%20will%20update%20this%20blog%20post.%20%3CSPAN%20class%3D%22author%22%3EThe%20Exchange%20Team%3C%2FSPAN%3E%3C%2FLINGO-BODY%3E

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
40 Comments
Not applicable
Gotcha! Nice to see that some our feedbacks may be useful sometimes... :)
Not applicable
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.

Not applicable
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.
Not applicable
Thanks for the heads up. Any guidance for customers who are impacted by this issue?
Not applicable
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.
Not applicable
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

Not applicable
@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).
Not applicable
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.
Not applicable
Disabling the MSExchangeHM service is not recommended
Not applicable
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!

Not applicable
Neither is w3wp crash. But what else to do while waiting for a fix?
Not applicable
This is significantly impacting our High Availability Deployment.
Not applicable
Thank you for the update.
Not applicable
How ?
Not applicable
If running a standalone Exchange 2016 on WS2016 without DAG, there should be no issues?
Not applicable
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.
Not applicable
That's correct.
Not applicable
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.

Not applicable
Thanks, this will resolve many customers issues, people are reluctant to start new deployments.
Not applicable
testing =(
Not applicable
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.
Not applicable
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...

Not applicable
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
Not applicable
Hello Guys,

is there an update on this issue?

Will the fix come in Dec. 2016?

Thanks and kind regards,

Dominik

Not applicable
Good Morning,

is there anything new on this issue.

Can we count on a Patch in December?

Thanks and kind regards,

Dominik

Not applicable
Still now news on this topic?
Not applicable
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

Not applicable
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 ?

Not applicable
Hi Exchange-Team,

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

Not applicable
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.
Not applicable
One month is gone and no one info or update?

(Info like "no patch until Q2 2017" would be a very helping info!)

Not applicable
Waiting the update !!
Not applicable
windows bakup
Not applicable
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!

Not applicable
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
Not applicable
Exchange Team: Where do we stand here? Christmas present ready?
Not applicable
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!

Not applicable
YES! - fixed: https://blogs.technet.microsoft.com/exchange/2016/12/13/released-december-2016-quarterly-exchange-updates/
Not applicable
We're considering Server 2016 for our Exchange 2016 installation. Did the update resolve the issues?
Not applicable
comment