PSA: Block the latest .NET update on your Exchange Servers

[Arthur]

From the Exchange Team blog...

 

http://blogs.technet.com/b/exchange/archive/2016/02/10/on-net-framework-4-6-1-and-exchange-compatibility.aspx

 

On .NET Framework 4.6.1 and Exchange compatibility

We wanted to post a quick note to call out that since yesterday, the .NET Framework 4.6.1 has been made a recommended update on WU (Windows Update).

 

As we have already stated in the Exchange Supportability Matrix, at this time, this version of .NET framework is not supported by Exchange. In fact, we know of some issues if it is installed.

 

We are working with the .NET team to ensure that Exchange customers have a smooth transition to .NET Framework 4.6.1, but in the meantime, delay this particular .NET update on your Exchange servers (information on how this can be accomplished can be found in the KB article 3133990, How to temporarily block the installation of the .NET Framework 4.6.1).

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\WU]
"BlockNetFramework461"=dword:00000001

[Michael]

By the looks of things, this isn't just a server issue, but a client issue also.

 

Makes you wonder why Microsoft didn't delay recommending .NET 4.6.1 and release a fix for Exchange 2013 at the same time?

[JonThompson]

.…Makes you wonder why Microsoft didn't delay recommending .NET 4.6.1 and release a fix for Exchange 2013 at the same time?

 

It's like the left hand doesn't know what the right hands doing!

[Michael]

It's like the left hand doesn't know what the right hands doing!

 

It just bugs me how in less than 24 hours, an article has been published detailing the problems it creates. A bit laughable really, but on a serious note this could create problems for some Exchange admins.

 

Details of .NET 4.6.1 can be found here.

 

This line made me chuckle -

 

The .NET Framework 4.6.1 builds on the .NET Framework 4.6 by adding many new fixes and several new features while remaining a very stable product.

 

Yeah, but it'll take down your Exchange server, but that's OK

[JonThompson]

Let's just hope MS don't install it on there Office 365 Exchange servers. Now that would be funny, in a really bad kinda way.