Most notably this fixes an issue I had run into myself in both Exchange 2016 CU13 and CU14. You can read more about those in KBs 45221150.
#Exchange 2019 cu4 series#
In this series of cumulative updates, Microsoft has resolved a number of security and non-security issues. From there you can migrate to 2019.įor more information on migrating from Exchange 2010 to 2016, check out this recent blog article from the Exchange Team: Exchange On-Premises Best Practices for Migrations from 2010 to 2016 So, what’s new in these Cumulative Updates? If you do plan to stay on-prem, you will need to migrate to either 2013 or 2016 (I’d recommend 2016 as 2013 is now in extended support). Unfortunately, there is no direct path to Exchange 2019 from 2010. The Exchange Team has provided this extension to allow companies more time to migrate to a newer email platform, such as Office 365, or, Exchange 2016. Server 2008 R2 will still go end of life on January 14th, 2020. While this extension allows for a little more breathing room, it does not extend support for Windows Server 2008 R2, which is the underlying operating system for many Exchange 2010 installations. Exchange 2010 now shares the same end-of-life date as Office 2010 and SharePoint 2010, which is October 13th, 2020.
#Exchange 2019 cu4 update#
Exchange 2016 Cumulative Update 15 | KB4522150 | UM Language Pack Exchange 2010 support extendedīack in September, the Exchange Team announced that is was extending support for Exchange 2010 by nine months.
0 kommentar(er)
