Comments on: March 2018 Updates Released for Exchange Server

By: Tim

Tim — Wed, 25 Apr 2018 14:17:27 +0000

sorry about that, we’re currently on CU7. I’ll re-read the link again.

Thanks

By: Paul Cunningham

Paul Cunningham — Tue, 24 Apr 2018 22:45:01 +0000

In reply to Tim.

You don’t mention the CU you’re currently on, but this article should help answer your question:
https://www.practical365.com/exchange-server/fixing-outdate-cumulative-updates-net-framework/

By: Tim

Tim — Tue, 24 Apr 2018 14:23:24 +0000

I’m getting ready to apply Ex2016 CU9 (on 2012R2 OS) and I’d like to be ahead of the curve by also installing .NET 4.7.1. Is there a particular order to follow here? Does the .NET update/upgrade install with no problems or are there things I need to be looking out for?

the support matrix indicates CU8 & 9 are the only CU’s that support .NET 4.7.1, I guess I should install one of those first, then the .NET update. correct?

Thank you

By: Tu Nguyen

Tu Nguyen — Sun, 22 Apr 2018 03:44:34 +0000

Hi Paul,

We are facing a very strange issue. After installing the Security Patch for Exchange 2016 CU8 unsuccessfully, all Exchange services were disabled and stopped working. We had to enable and start them manually. Starting that moment, the %Systemroot%\Temp folder being filled up quickly with .TMP files. Their names starting with 0*.tmp –> 9*.tmp, a*.tmp –> f*.tmp. They are also growing in size, starting with 400KB each file now nearly 40MB each after 5 days. Only about 1/3 or 1/4 of the TMP files are that big, the others that are still being generated now are still only few KB in size.

Both Exchange Server team and Windows Server team from Microsoft Partner Technical Support service took a look at our server and could not identify the cause, or whether we could delete those TMP files safely. We have to keep extending the C: partition in order to keep Back Pressure not kicks in. The original size was only 150GB and now reaching 1TB.

Any idea or educated guess is very welcome and appreciated. Thanks!