Answered by:
.NET version and a fresh install of Exchange 2013 CU17....

Question
-
I am a bit confused by all of the .NET 4.6.x and Exchange 2013\2016 talk. I have a server 2012 R2 DataCenter edition virtual server with .NET 4.6.2 already installed (not 4.7) that will act as my stand-alone Exchange 2013 server (it will co-exist with our stand-alone Exchange 2010 server). For the Exchange install I assume I can just download and install CU 17 for Exchange 2013, then make sure I do not install .NET 4.7?
Jason
- Moved by Edward van BiljonMVP Tuesday, August 22, 2017 4:39 AM Moved to correct Forum
Friday, August 18, 2017 12:04 AM
Answers
-
Yes.
You can use this technique to block .NET Framework 4.7.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Celebrating 20 years of providing Exchange peer support!- Proposed as answer by Edward van BiljonMVP Tuesday, August 22, 2017 4:38 AM
- Marked as answer by Jack Leidu Tuesday, August 22, 2017 2:11 PM
Friday, August 18, 2017 1:56 AM
All replies
-
Yes.
You can use this technique to block .NET Framework 4.7.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Celebrating 20 years of providing Exchange peer support!- Proposed as answer by Edward van BiljonMVP Tuesday, August 22, 2017 4:38 AM
- Marked as answer by Jack Leidu Tuesday, August 22, 2017 2:11 PM
Friday, August 18, 2017 1:56 AM -
Hi Jason,
Yes, you can install CU17 for Exchange 2013 directly, as CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one.
Best Regards,
Niko Cheng
TechNet Community Support
Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Friday, August 18, 2017 8:41 AM -
Thank you I will mark this as answered. Regarding patches released by MS, is there a site I can subscribe to so I am alerted about "bad" patches or issues caused by patches? I got lucky this time, I just stumbled across the .NET article.Monday, August 21, 2017 3:47 PM