Associate Troublemaker Apprentice
Registered: 1451575798 Posts: 887
Reply with quote #1
Read something last night and the penny dropped.
Older unsupported instances of Exchange 2013/ 2016 will be difficult to bring into a supported state. The links I read through. https://practical365.com/exchange-server/fixing-outdate-cumulative-updates-net-framework/ https://eightwone.com/2017/12/21/upgrade-paths-for-cus-net/ https://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx So the .NET frameworks are available. Exchange 2016 CU8, CU7 and CU6 as well as RTM are available. Exchange 2013 CU19, CU18 and CU17 are available. I also have a copy of Exchange 2013 CU15 - which appears to be the key to a lot of the .NET dependencies. Thanks to Michel de Rooij for the picture.
__________________ Have you tried turning it off and walking away? The next person can fix it!
New to the forum? Read this
Registered: 1451592353 Posts: 288
Reply with quote #2
Well, to make this as clear as it gets: Up until now, there hasn't been anything in the Exchange or .NET installer to prevent you from having an unsupported (and, often enough, not working) combination of .NET and Exchange CU.
So in a DAG, you can just take the risk and upgrade .NET to the latest, reboot and then upgrade Exchange to the latest, node for node. This is also what the product group seems to be telling people who talk to them unofficially. You can't expect the node to be working in the interim, but in my testing, the end result is OK. If you have a single server then, well, that's another story. __________________ Evgenij Smirnov My personal blog (German): http://www.it-pro-berlin.de/ My stuff on PSGallery: https://www.powershellgallery.com/profiles/it-pro-berlin.de/