Exchange Server 2016 and the End of Mainstream Support

Published Aug 10 2020 07:59 AM 54.4K Views

UPDATE 2/12/21

The Exchange Sustained Engineering Team continued servicing all customer issues for Exchange 2016 that were opened with Microsoft by the end of Mainstream Support, which was Oct 13, 2020. Some of these cases were being worked on by customers and Microsoft into the new year, with fixes being approved though the end of January. As such, not all fixes will be in the soon-to-be-shipped March update (CU20), as code stabilization and quality targets do not allow us to take changes that late in the shipping cycle. Therefore, we have decided to extend out one more CU and we will be shipping CU21 in June 2021. New cases are not being considered for CU21; this is only to complete our commitment to fix what was approved from the cases that were logged prior to the end of Mainstream Support. Microsoft encourages Exchange Server 2016 customers to adopt CU21 as soon as possible after it’s released in June, 2021 to ensure uninterrupted delivery of any future security related fixes. After June 15, 2021, only CU21 or its successors will receive updates. During the Extended Support phase, only the latest CU is eligible to receive updates once the standard 3 month transition period of the prior CU has lapsed.

----------------------------------------------------------------------------------------------

As hopefully many of you already know Exchange Server 2016 enters the Extended Support phase of its product lifecycle on October 14th 2020. That’s just a few short months away.

During Extended Support, products receive only updates defined as by the Fixed Life Cycle. For Exchange Server 2016, Fixed Life Cycle will include any required product updates due to security and time zone definition changes. With the transition of Exchange Server 2016 to Extended Support, the quarterly release schedule of cumulative updates (CU) will end. The last planned CU for Exchange Server 2016, CU20, will be released in March 2021. This is a change from earlier blog notes because it became clear that CU19 in December 2020, was too close the end of Mainstream Support to process all of the cases that came in by Oct 13th.   

There is one more consideration for this change that we want to address here today, and that is the ongoing use of Exchange Server 2016 for recipient management for hybrid organizations that have moved all their mailboxes to the cloud.

As you probably also know we have historically provided a free license for these ‘management’ servers if their only use is to properly manage Exchange attributes when recipient objects are mastered on-premises. You also know that we never provided this free license type for Exchange Server 2019.

We want to assure you that we are still committed to delivering a solution that will allow these lingering servers to be removed, but it will not arrive before Exchange Server 2016 enters Extended Support.

For this reason, we want to make our recommendation for this scenario clear. Our broad recommendation is to keep Exchange Server 2016 in production use until such point as we release a solution that allows those servers to be removed. As explained earlier, Extended Support still provides security and time zone updates and so keeping them in production and ensuring they are properly patched does not increase your risk profile in any way.

If you can’t move your mailboxes to the cloud and you plan on keeping mailboxes on-premises, then you really should be moving to Exchange Server 2019, and using that for both mailboxes and hybrid connectivity. That way you get full support including non-critical bug fixes and get ongoing product improvements.

When we have a solution available to allow any management-only servers to be removed, it may require an update to Exchange Server 2016, and in that case we may release a future CU or patch. Currently there is no plan to release future updates for Exchange 2016, but we want to assure our customers that if we need to do this to support the removal of these ‘management only’ servers, we will.  

Microsoft encourages Exchange Server 2016 customers to adopt CU20 as soon as possible to ensure uninterrupted delivery of any future security related fixes. After March 16, 2021, only CU20 or its successors will receive updates. During the Extended Support phase, only the latest CU is eligible to receive updates once the standard 3 month transition period of the prior CU has lapsed.  

Updates will continue to be made available via Windows Update and the Microsoft Download Center. Additional lifecycle information for all Microsoft products is available on docs.microsoft.com.

We hope this update was informative and we look forward to hearing your feedback and answering any questions you may still have.

The Exchange Team

28 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-1587468%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1587468%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EGreat%20information.%20Thank%20you%20for%20the%20update.%20%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EWe%20have%20just%20completed%20our%20migration%20from%202010%20to%20cloud%20with%20a%202016%20management%20server.%20In%20our%20case%20our%202016%20management%20server%20has%20just%20the%208%20system%20mailboxes%20left%20and%20is%20also%20used%20for%20internal%20applications%20to%20relay%20mail.%20In%20this%20case%20would%20the%20recommendation%20be%20to%20move%20to%202019%2C%20stay%20on%202016%20or%20something%20else%3F%20We%20are%20not%20sure%20when%20we%20can%20move%20our%20internal%20applications%20to%20send%20using%20365.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EThank%20you.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1588847%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1588847%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20issue%20with%20Hybrid%20is%20that%20there%20is%20a%20free%20license%20key%20available%20for%202016%20but%20not%20for%202019.%20You%20need%20to%20update%20the%20HCW%20so%20we%20can%20use%202019%20for%20Hybrid%20without%20paying%20for%20a%20license%20when%20it%20is%20just%20used%20for%20management.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1590166%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1590166%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F61268%22%20target%3D%22_blank%22%3E%40Jerry%20Szczepanski%3C%2FA%3E%26nbsp%3B-%20in%20your%20case%20I'd%20say%20just%20stick%20with%202016%2C%20keep%20it%20up%20to%20date%20with%20security%20patches%20and%20figure%20out%20how%20to%20move%20those%20apps.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F464343%22%20target%3D%22_blank%22%3E%40halbp%3C%2FA%3E%26nbsp%3B-%20did%20you%20read%20the%20article%3F%20We're%20not%20going%20to%20do%20that.%20You%20can%20keep%20using%202016.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1591066%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1591066%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3BThanks%20Greg.%26nbsp%3B%20I%20read%20the%20article%20to%20set%20up%20relay%20through%20365%2C%20option%203%2C%20but%20it's%20so%20confusing.%26nbsp%3B%20There%20was%20also%20no%20mention%20if%20that%20scenario%20would%20work%20if%20our%20current%20situation%20required%20adding%20the%20ms-Exch-SMTP-Accept-Any-Recipient%20permission%20for%20anonymous%20relay.%26nbsp%3B%20If%20not%2C%20I%20don't%20know%20how%20we'll%20ever%20get%20off%20the%20on-premise%20server.%26nbsp%3B%20For%20now%20since%20we%20need%20that%20box%20anyway%20it%20hasn't%20been%20an%20issue%20but%20certainly%20could%20be%20once%20the%20management%20server%20is%20no%20longer%20needed.%26nbsp%3B%20Thanks%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1591247%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1591247%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3Byes%20but%20why%20not%20just%20allow%20use%20of%202019%20which%20will%20still%20be%20in%20mainstream%20support%2C%20given%20that%20it%20also%20supports%20hybrid%3F%20I%20don%E2%80%99t%20understand%20why%202016%20would%20be%20free%20and%202019%20wouldn%E2%80%99t%20be%2C%20it%E2%80%99s%20a%20pointless%20limitation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1594437%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1594437%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3B-%20Thanks%20for%20the%20update%20and%20clarification%20Greg.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20give%20us%20any%20insight%20into%20the%20development%20of%20the%20final%20%22solution%22%3F%3C%2FP%3E%3CP%3EHow%20it's%20tracking%2C%20potential%20timeline%2C%20photo's%20of%20some%20poor%20geezer%20rocking%20back%20and%20forth%20under%20his%20desk%20in%20anguish%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20not%20seen%20any%20mention%20of%20it%20in%20over%20a%20year%2C%20if%20you%20can%20link%20to%20a%20roadmap%20that%20would%20be%20fantastic.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELast%20mentioned%20here%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Ffaqs-from-exchange-and-outlook-booths-at-2019-microsoft-ignite%2Fba-p%2F1053448%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Ffaqs-from-exchange-and-outlook-booths-at-2019-microsoft-ignite%2Fba-p%2F1053448%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1595295%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1595295%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20blog.%20Is%20there%20somewhere%20I%20can%20monitor%20for%20updates%20on%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20number%20of%20sites%20with%20active%20directory%20and%20Azure%20AD%20Connect%20to%20sync%20user%20passwords%20with%20their%20MS365%20business%20apps%20identity.%20A%20lot%20of%20these%20sites%20never%20had%20Exchange%2C%20they%20used%20a%203rd%20party%20email%20provider.%20We%20now%20want%20to%20add%20a%20mailbox%20to%20their%20MS365%20account%2C%20but%20as%20soon%20as%20we%20tell%20the%20customer%20that%20in%20order%20to%20do%20so%20Microsoft%20expect%20them%20to%20provision%20a%20full%20blown%20Exchange%202016%20server%20on-premise%2C%20with%20the%20hardware%2C%20installation%20and%20ongoing%20maintenance%20cost%20that%20brings%20just%20to%20manage%20a%20few%20AD%20user%20attributes%2C%20it%20becomes%20a%20deal%20breaker.%20None%20of%20them%20can%20remove%20on-premise%20active%20directory%20due%20to%20application%20software%20requirements%2C%20but%20one%20or%20two%20have%20reluctantly%20opted%20to%20remove%20Azure%20AD%20Connect%20-%20not%20an%20ideal%20'solution'.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20sites%20that%20did%20have%20a%20few%20Exchange%20servers%20in%20their%20estate%20are%20quite%20happy%20to%20reduce%20that%20to%20just%20one%20for%20management%20purposes%20-%20but%20they%20are%20coming%20from%20a%20completely%20different%20start%20point%20than%20those%20sites%20who%20never%20had%20Exchange.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%2C%3C%2FP%3E%3CP%3EKevin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1597662%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1597662%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F761689%22%20target%3D%22_blank%22%3E%40Kevin_Davis%3C%2FA%3E%26nbsp%3BHi%20Kevin%2C%20this%20blog%20is%20the%20place%20to%20watch%20for%20news.%20And%20if%20you%20follow%20me%20on%20Twitter%20(%40gregtaylor_msft)%20I'll%20usually%20tweet%20when%20we%20post%20new%20articles.%20RSS%20is%20so%201990's.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1614491%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1614491%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3Bis%20there%20some%20particular%20reason%20that%20Exchange%202019%20doesn't%20get%20free%20hybrid%20keys%3F%26nbsp%3B%20It's%20a%20harsh%20180%20turn%20to%20suddenly%20take%20that%20away%20after%20having%20the%20option%203%20Exchange%20versions%20in%20a%20row%20previously.%26nbsp%3B%20The%20only%20thing%20I've%20seen%20said%20about%20this%20in%20this%20blog%20and%20the%20comments%20is%20that%20the%20answer%20is%20%22No%22%20and%20that%20won't%20change.%26nbsp%3B%20Have%20not%20yet%20seen%20the%20reason%20for%20the%20decision.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1614674%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1614674%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64125%22%20target%3D%22_blank%22%3E%40Jeremy%20Bradshaw%3C%2FA%3E%26nbsp%3BI%20agree%2C%20we%20don't%20even%20know%20what%20the%20'final'%20solution%20looks%20like%2C%20and%20it%20is%20likely%20that%20many%20organisations%20will%20need%20to%20keep%20using%20Exchange%20hybrid%20for%20quite%20some%20time%20anyway%20due%20to%20other%20reasons%20e.g.%20support%20processes%2C%20powershell%20scripts%2C%20mail%20relay%20etc.%20So%20why%20not%20let%20them%20keep%20using%20it%2C%20given%20that%20we've%20been%20forced%20to%20use%20it%20all%20these%20we%20may%20as%20well%20be%20allowed%20to%20use%20the%20current%20version%20in%20mainstream%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1614847%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1614847%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64125%22%20target%3D%22_blank%22%3E%40Jeremy%20Bradshaw%3C%2FA%3E%26nbsp%3B%20and%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F464343%22%20target%3D%22_blank%22%3E%40halbp%3C%2FA%3E%26nbsp%3B%20-%20let%20me%20try%20and%20add%20some%20context.%20I%20don't%20expect%20everyone%20will%20agree%2C%20but%20you%20wanted%20to%20understand%20the%20reason%20so%20I'll%20try%20and%20explain.%20The%20reason%20simply%20is%20that%20we%20chose%20to%20only%20distribute%202019%20via%20VLSC%20and%20not%20via%20broad%20public%20download.%20Which%20means%20not%20everyone%20has%20access%20to%20the%20bits%2C%20which%20makes%20handing%20out%20a%20free%20key%20tricky.%20So%20that%20is%20the%20main%20reason%20for%20it%2C%20to%20support%20our%20change%20to%20distribution%20for%202019.%20Why%20did%20we%20choose%20to%20switch%20to%20distributing%20only%20via%20VLSC%3F%20We%20released%202019%20and%20were%20very%20clear%20(I%20know%2C%20as%20I%20did%20the%20announcement)%20that%20we%20believe%20all%20our%20customers%20should%20be%20moving%20to%20the%20cloud%2C%20particularly%20the%20smaller%20companies%20who%20don't%20buy%20via%20a%20VL%20program%2C%20and%20this%20is%20one%20way%20to%20make%20that%20happen.%20We%20receive%20little%20to%20no%20feedback%20on%20ability%20to%20access%20the%20bits%20from%20customers.%20Meaning%2C%20those%20customers%20that%20are%20licensed%20and%20want%20to%20install%20it%2C%20can%20get%20it.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20is%20also%20true%20is%20that%20if%20you%20are%20using%202016%20or%202019%20just%20for%20recipient%20management%20-%20there's%20no%20functional%20advantage%20to%202019.%20So%20there's%20no%20reason%20to%20deploy%202019%2C%20with%20its%20increased%20hardware%20requirements%20just%20for%20hybrid%20recipient%20management.%20Use%202016%2C%20it's%20free%20and%202019%20only%20complicates%20things%20in%20that%20scenario.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F464343%22%20target%3D%22_blank%22%3E%40halbp%3C%2FA%3E%26nbsp%3Bif%20you%20are%20using%20Exchange%20on-prem%20in%20the%20long%20term%20for%20much%20more%20than%20just%20recipient%20management%2C%20for%20those%20things%20you%20listed%2C%20then%20expecting%20us%20to%20give%20you%20that%20server%20for%20free%20is%20where%20we%20will%20probably%20have%20to%20disagree%20-%20I%20think%20you%20should%20pay%20for%20that%20type%20of%20usage.%20If%20you%20just%20want%20a%20free%20mail%20relay%2C%20you%20don't%20need%20Exchange.%20If%20you%20want%20to%20use%20Exchange%20for%20features%20only%20Exchange%20can%20provide%20-%20and%20for%20more%20than%20just%20recipient%20management%20(for%20which%20we%20will%20ship%20code%20to%20negate%20the%20need%20for%20it)%20-%20you%20should%20buy%20a%20license%20for%20it.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1615434%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1615434%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3Bthanks%20for%20the%20clarification%2C%20I%20assumed%20it%20was%20something%20to%20do%20with%20the%20long-term%20roadmap%20of%20moving%20to%20the%20cloud.%3C%2FP%3E%3CP%3ETo%20give%20a%20little%20more%20context%20to%20the%20SME%20environment%2C%20we%20are%20looking%20at%20moving%20our%20own%20server%20infrastructure%20to%20be%20cloud%20based%20(lead%20by%20example)%20and%20have%20done%20most%20of%20it%20such%20as%20placing%20all%20our%20shared%20files%20on%20OneDrive%20or%20Sharepoint%2C%20and%20have%20MS365%20for%20Office%20Apps%20and%20email.%20The%20next%20step%20in%20our%20plan%20is%20to%20remove%20on-prem%20Exchange%2C%20but%20for%20that%20we%20need%20to%20make%20our%20user%20accounts%20cloud%20based%2C%20and%20not%20synced%20via%20Azure%20AD%20Connect.%20Simple%20enough%20in%20itself%20to%20break%20the%20sync%20and%20recover%20the%20user%20from%20Deleted%20Users%2C%20but%20our%20on-prem%20ADDS%20is%20used%20to%20sync%20all%20sorts%20of%20other%20SSO%20integrations%2C%20such%20as%20LDAP%20to%20our%20MFA%20solution%20(WatchGuard%20AuthPoint)%20our%20RMM%20platform%2C%20client%20documentation%20platform%2C%20etc.%20It%20very%20quickly%20opens%20a%20can%20of%20worms%20to%20say%20%22make%20the%20users%20cloud%20based%22%2C%20as%20I%20expect%20is%20the%20case%20with%20most%20SME's%20-%20certainly%20is%20with%20most%20of%20our%20clients%20with%20ADDS.%20Having%20in-cloud%20user%20accounts%20will%20also%20allow%20us%20to%20use%20that%20account%20to%20register%20new%20devices%20such%20as%20laptops%20during%20initial%20setup%20and%20login%20as%20the%20MS365%2FAzure%20account%2C%20instead%20of%20having%20to%20join%20the%20laptop%20to%20on-prem%20active%20directory%2C%20with%20all%20the%20associated%20remote%20working%2FVPN%20complications%20that%20brings.%3C%2FP%3E%3CP%3EWe%20are%20now%20turning%20our%20attention%20to%20Azure%20ADDS%20(which%20it%20seems%20is%20different%20to%20the%20rather%20badly%20named%20%22Azure%20AD%22)%2C%20so%20will%20see%20how%20that%20goes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20of%20that%20means%2C%20for%20now%2C%20that%20we%20still%20have%20to%20rely%20on%20Exchange%20for%20MS365%20tenants%20with%20Azure%20AD%20Connect%2C%20and%20are%20very%20keen%20to%20get%20to%20a%20point%20where%20on-prem%20Exchange%20with%20all%20the%20additional%20hardware%20and%20support%20costs%2C%20is%20no%20longer%20a%20requirement.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%2C%3C%2FP%3E%3CP%3EKevin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1615561%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1615561%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20response%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20I%20understand%20Exchange%202016%20is%20fine%20for%20current%20hybrid%2C%20but%20my%20point%20was%20that%20companies%20have%20complex%20JML%20processes%20built%20around%20using%20Exchange%20on-prem%20to%20manage%20mailboxes%2C%20and%20whilst%20we%20have%20a%20few%20more%20years%20in%20support%20obviously%20the%20clock%20is%20ticking.%20We%20don't%20know%20what%20the%20new%20solution%20looks%20like%2C%20but%20hopefully%20it%20will%20offer%20a%20similar%20level%20of%20automation.%3C%2FP%3E%3CP%3EAlso%2C%20I%20did%20not%20think%20that%20using%20Exchange%20hybrid%20for%20mail%20relay%20goes%20against%20the%20license%20terms%2C%20assuming%20there%20are%20no%20mailboxes%3F%20Yes%20we%20normally%20use%20another%20SMTP%20server%2C%20but%20for%20smaller%20environments%20if%20there%20is%20already%20an%20Exchange%20server%20it%20makes%20sense%20to%20use%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1615781%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1615781%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3Byes%2C%20thanks%20for%20the%20response.%3C%2FP%3E%3CP%3EI%20do%20disagree%20with%20most%20of%20it%20but%20will%20save%20us%20all%20the%20bother%20and%20just%20forget%20about%20it.%26nbsp%3B%20I%20miss%20the%20good%20old%20days%20of%20Exchange%20already%20%3Acrying_face%3A.%26nbsp%3B%20It%20was%20a%20good%20run.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1619060%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1619060%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat's%20about%20a%20Hybrid%20Configuration%20with%20Exchange%202016%20when%20you%20are%20using%20Exchange%20Online%20Archiving%3F%3C%2FP%3E%3CP%3EAt%20the%20moment%20it's%20required%20that%20you%20are%20on%20the%20current%20or%20current-1%20CU%20versions%20to%20be%20supported%20with%20Exchange%20Online%20Archiving.%3C%2FP%3E%3CP%3EWhen%20no%20new%20CU%20will%20be%20deployed%2C%20does%20that%20mean%20we'll%20be%20in%20an%20unsupported%20scenario%20for%20Hybrid%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%3C%2FP%3E%3CP%3EMichael%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1619224%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1619224%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F761689%22%20target%3D%22_blank%22%3E%40Kevin_Davis%3C%2FA%3E%26nbsp%3B-%20we%20want%20that%20last%20statement%20you%20made%20too.%20We're%20still%20working%20on%20making%20it%20a%20reality.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F464343%22%20target%3D%22_blank%22%3E%40halbp%3C%2FA%3E%26nbsp%3B-%20If%20you%20are%20using%20that%20last%20server%20for%20Hybrid%20recipient%20management%20it's%20ok%20to%20use%20it.%20But%20once%20you%20are%20not%2C%20you%20need%20to%20license%20the%20box.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64125%22%20target%3D%22_blank%22%3E%40Jeremy%20Bradshaw%3C%2FA%3E%26nbsp%3B-%20we%20all%20do%20sometimes%2C%20it's%20ok.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F774739%22%20target%3D%22_blank%22%3E%40MichaelHess%3C%2FA%3E%26nbsp%3B-%20Not%20sure%20I%20understand.%20The%20primary%20mailbox%20is%20where%3F%20On-Prem%3F%20on%202016%3F%20Stay%20on%20the%20latest%20CU%20we%20issue%2C%20you'll%20be%20in%20Extended%20Support%2C%20but%20it's%20supported.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1619235%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1619235%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3Bthanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1622424%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1622424%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3B%2C%20thanks%20for%20the%20response.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20primary%20mailboxes%20are%20still%20OnPrem%20on%20Exchange%202016%20but%20Hybrid%20setup%20is%20done%20and%20the%20migration%20to%20Exchange%20Online%20will%20be%20done%20in%20the%20future%20(during%202021).%20For%20the%20OnPrem%20mailboxes%20we%20have%20already%20started%20to%20deploy%20Exchange%20Online%20Archives%20in%20advance%20of%20the%20primary%20mailbox%20migration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1750180%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1750180%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20I%20wasn't%20sure%20exactly%20where%20to%20pose%20this%20question%3A%20We%20are%20currently%20running%20Exchange%202016%20on%20prem%20in%20a%20hybrid%20environment%20with%20O365.%20Most%20of%20our%20mailboxes%20are%20in%20the%20cloud%20but%20we%20do%20have%20an%20on-prem%20database%20with%20some%20on-prem%20mailboxes.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20planning%20on%20upgrading%20to%20Exchange%202019%20very%20soon.%20I%20was%20reading%20a%20detailed%20series%20of%20blog%20posts%20that%20talk%20about%20installing%20Exchange%20Server%202019%2C%20and%20they%20mention%20having%20to%20prepare%20Active%20Directory%20and%20extending%20the%20AD%20schema%20for%20Exchange%202019.%20Is%20this%20true%20even%20if%20we%20are%20running%20Exchange%202016%3F%20Do%20we%20still%20have%20to%20prepare%20AD%20and%20extend%20the%20schema%2C%20or%20does%20that%20only%20apply%20if%20you're%20installing%20Exchange%20for%20the%20very%20first%20time%20in%20your%20organization%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1752172%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1752172%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F464343%22%20target%3D%22_blank%22%3E%40halbp%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20believe%20the%20statement%20made%20earlier%20is%20incorrect%20regarding%20the%20use%20rights%20of%20Hybrid%20licence%20key%20for%20mail%20relay%20and%20user%20management%20automation%20scripts.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThe%20guidance%20has%20always%20been%20that%20the%20Hybrid%20licence%20key%20rights%20are%20fine%20so%20long%20as%20there%20are%20no%20Mailbox%20workloads%20hosted%20on%20the%20server.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20statement%20is%20made%20in%20the%20licensing%20FAQ%20and%20the%26nbsp%3Bguidance%20has%20also%20been%20updated%20to%20reflect%20the%20fact%20that%202019%20servers%20are%20not%20eligible%2C%20so%20it%20appears%20to%20be%20an%20active%20guidance.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERefer%20here%3A%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fexchange%2Fmicrosoft-exchange-licensing-faq-email-for-business%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fexchange%2Fmicrosoft-exchange-licensing-faq-email-for-business%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%22If%20you%20do%20not%20host%20any%20mailboxes%20on%20the%20servers%20used%20to%20connect%20to%20Microsoft%20365%20you%20can%20license%20them%20using%20the%20Microsoft%20365%20Hybrid%20Configuration%20Wizard%20(HCW)%20which%20you%20can%20find%26nbsp%3Bhere.%20The%20HCW%20validates%20your%20Microsoft%20365%20subscription%20and%20installs%20the%20appropriate%20licenses%20on%20your%20servers.%20Note%20that%20the%20free%20Exchange%20Server%20license%20is%20not%20available%20for%20Exchange%202019%20hybrid%20servers.%22%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20also%20worthwhile%20checking%20with%20your%20licence%20agreement%20provider%2C%20as%20you%20may%20already%20be%20entitled%20to%20run%20Exchange%20Server%20on-premises%20under%20some%20M365%20licensing%20agreements.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlthough%20I%20know%20this%20will%20not%20be%20of%20comfort%20to%20many%20smaller%20seat%20customers%2C%20if%20eligible%20it%20will%20provide%20a%20mail%20relaying%20solution%20in%20the%20future%2C%20if%20the%20Hybrid%20use%20licence%20becomes%20deprecated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1954735%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1954735%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F143175%22%20target%3D%22_blank%22%3E%40Rakesh%20Chauhan%3C%2FA%3E%26nbsp%3B-%20I%20didn't%20go%20yet.%20What%20potential%20solution%20are%20you%20referring%20to%3F%20Sorry%2C%20not%20clear%20to%20me.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1954607%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1954607%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%3CSPAN%3E%26nbsp%3B-%20don't%20worry%2C%20you%20can%20ignore%20my%20question%20%3A%20)%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115162%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115162%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20Current%20Exchange%20Version%20%3A%20EXCHANGE%202016%20(CU17)%3C%2FP%3E%3CP%3ESingle%20Server%20with%20Two%20DBs%3C%2FP%3E%3CP%3EI%20don%3Bt%20have%20any%20test%20environment.%3C%2FP%3E%3CP%3EI%20am%20planning%20to%20upgrade%20directly%20to%20CU19.But%20i%20got%20reviews%20from%20customers%20there%20are%20the%20problems%20in%20CU18%20and%20CU19%2C%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20customers%20are%20reported%20to%20MS.%3C%2FP%3E%3CP%3ENow%20MS%20is%20going%20to%20release%20CU20%20next%20month%20(March%2016)%20with%20all%20fix%20including%26nbsp%3Bvulnerability.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20do%20you%20suggest%20to%20should%20i%20go%20for%20CU19%20directly%20or%20await%20for%20CU20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20advise%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2129133%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2129133%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20we%20have%20an%20update%20on%20the%20new%20solution%20for%20Hybrid%20please%2C%20or%20at%20least%20let%20us%20use%202019%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2131413%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2131413%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F956385%22%20target%3D%22_blank%22%3E%40TLS%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EExchange%202016%20CU17%20is%20not%20a%20supported%20cumulative%20update.%20If%20you%20want%20to%20operate%20your%20Exchange%20Org%20in%20a%20supported%20setup%2C%20I'd%20recommend%20updating%20to%20the%20most%20recent%20CU%2C%20and%20update%20to%20a%20future%20CU%20as%20soon%20as%20it's%20released.%3CBR%20%2F%3E-Thomas%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2135065%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2135065%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20Thomas%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20Exchange2016%20CU19%20is%20the%20latest%20patch%20can%20i%20proceed%20with%20CU19%3F%3C%2FP%3E%3CP%3EAny%20known%20issue%20in%20this%20latest%20CU19%3F%20after%20upgrading%20CU17%20to%20CU19%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20advise-%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1574110%22%20slang%3D%22en-US%22%3EExchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1574110%22%20slang%3D%22en-US%22%3EUPDATE%202%2F12%2F21%3CP%3EThe%20Exchange%20Sustained%20Engineering%20Team%20continued%20servicing%20all%20customer%20issues%20for%20Exchange%202016%20that%20were%20opened%20with%20Microsoft%20by%20the%20end%20of%20Mainstream%20Support%2C%20which%20was%20Oct%2013%2C%202020.%20Some%20of%20these%20cases%20were%20being%20worked%20on%20by%20customers%20and%20Microsoft%20into%20the%20new%20year%2C%20with%20fixes%20being%20approved%20though%20the%20end%20of%20January.%20As%20such%2C%20not%20all%20fixes%20will%20be%20in%20the%20soon-to-be-shipped%20March%20update%20(CU20)%2C%20as%20code%20stabilization%20and%20quality%20targets%20do%20not%20allow%20us%20to%20take%20changes%20that%20late%20in%20the%20shipping%20cycle.%20Therefore%2C%20we%20have%20decided%20to%20extend%20out%20one%20more%20CU%20and%20we%20will%20be%20shipping%20CU21%20in%20June%202021.%20New%20cases%20are%20not%20being%20considered%20for%20CU21%3B%20this%20is%20only%20to%20complete%20our%20commitment%20to%20fix%20what%20was%20approved%20from%20the%20cases%20that%20were%20logged%20prior%20to%20the%20end%20of%20Mainstream%20Support.%26nbsp%3BMicrosoft%20encourages%20Exchange%20Server%202016%20customers%20to%20adopt%20CU21%20as%20soon%20as%20possible%20after%20it%E2%80%99s%20released%20in%20June%2C%202021%20to%20ensure%20uninterrupted%20delivery%20of%20any%20future%20security%20related%20fixes.%20After%20June%2015%2C%202021%2C%20only%20CU21%20or%20its%20successors%20will%20receive%20updates.%20During%20the%20Extended%20Support%20phase%2C%20only%20the%20latest%20CU%20is%20eligible%20to%20receive%20updates%20once%20the%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fservicing-exchange-2013-and-later%2Fba-p%2F596398%22%20target%3D%22_blank%22%3Estandard%203%20month%20transition%3C%2FA%3E%20period%20of%20the%20prior%20CU%20has%20lapsed.%3C%2FP%3E%3CP%3E----------------------------------------------------------------------------------------------%3C%2FP%3E%3CP%3EAs%20hopefully%20many%20of%20you%20already%20know%20Exchange%20Server%202016%20enters%20the%20Extended%20Support%20phase%20of%20its%20product%20lifecycle%20on%20October%2014th%202020.%20That%E2%80%99s%20just%20a%20few%20short%20months%20away.%3C%2FP%3E%3CP%3EDuring%20Extended%20Support%2C%20products%20receive%20only%20updates%20defined%20as%20by%20the%20Fixed%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Flifecycle%2Fpolicies%2Ffixed%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3ELife%20Cycle%3C%2FA%3E.%20For%20Exchange%20Server%202016%2C%20Fixed%20Life%20Cycle%20will%20include%20any%20required%20product%20updates%20due%20to%20security%20and%20time%20zone%20definition%20changes.%20With%20the%20transition%20of%20Exchange%20Server%202016%20to%20Extended%20Support%2C%20the%20quarterly%20release%20schedule%20of%20cumulative%20updates%20(CU)%20will%20end.%20The%20last%20planned%20CU%20for%20Exchange%20Server%202016%2C%20CU20%2C%20will%20be%20released%20in%20March%202021.%20This%20is%20a%20change%20from%20earlier%20blog%20notes%20because%20it%20became%20clear%20that%20CU19%20in%20December%202020%2C%20was%20too%20close%20the%20end%20of%20Mainstream%20Support%20to%20process%20all%20of%20the%20cases%20that%20came%20in%20by%20Oct%2013th.%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20one%20more%20consideration%20for%20this%20change%20that%20we%20want%20to%20address%20here%20today%2C%20and%20that%20is%20the%20ongoing%20use%20of%20Exchange%20Server%202016%20for%20recipient%20management%20for%20hybrid%20organizations%20that%20have%20moved%20all%20their%20mailboxes%20to%20the%20cloud.%3C%2FP%3E%3CP%3EAs%20you%20probably%20also%20know%20we%20have%20historically%20provided%20a%20free%20license%20for%20these%20%E2%80%98management%E2%80%99%20servers%20if%20their%20only%20use%20is%20to%20properly%20manage%20Exchange%20attributes%20when%20recipient%20objects%20are%20mastered%20on-premises.%20You%20also%20know%20that%20we%20never%20provided%20this%20free%20license%20type%20for%20Exchange%20Server%202019.%3C%2FP%3E%3CP%3EWe%20want%20to%20assure%20you%20that%20we%20are%20still%20committed%20to%20delivering%20a%20solution%20that%20will%20allow%20these%20lingering%20servers%20to%20be%20removed%2C%20but%20it%20will%20not%20arrive%20before%20Exchange%20Server%202016%20enters%20Extended%20Support.%3C%2FP%3E%3CP%3EFor%20this%20reason%2C%20we%20want%20to%20make%20our%20recommendation%20for%20this%20scenario%20clear.%20Our%20broad%20recommendation%20is%20to%20keep%20Exchange%20Server%202016%20in%20production%20use%20until%20such%20point%20as%20we%20release%20a%20solution%20that%20allows%20those%20servers%20to%20be%20removed.%20As%20explained%20earlier%2C%20Extended%20Support%20still%20provides%20security%20and%20time%20zone%20updates%20and%20so%20keeping%20them%20in%20production%20and%20ensuring%20they%20are%20properly%20patched%20does%20not%20increase%20your%20risk%20profile%20in%20any%20way.%3C%2FP%3E%3CP%3EIf%20you%20can%E2%80%99t%20move%20your%20mailboxes%20to%20the%20cloud%20and%20you%20plan%20on%20keeping%20mailboxes%20on-premises%2C%20then%20you%20really%20should%20be%20moving%20to%20Exchange%20Server%202019%2C%20and%20using%20that%20for%20both%20mailboxes%20and%20hybrid%20connectivity.%20That%20way%20you%20get%20full%20support%20including%20non-critical%20bug%20fixes%20and%20get%20ongoing%20product%20improvements.%3C%2FP%3E%3CP%3EWhen%20we%20have%20a%20solution%20available%20to%20allow%20any%20management-only%20servers%20to%20be%20removed%2C%20it%20may%20require%20an%20update%20to%20Exchange%20Server%202016%2C%20and%20in%20that%20case%20we%20may%20release%20a%20future%20CU%20or%20patch.%20Currently%20there%20is%20no%20plan%20to%20release%20future%20updates%20for%20Exchange%202016%2C%20but%20we%20want%20to%20assure%20our%20customers%20that%20if%20we%20need%20to%20do%20this%20to%20support%20the%20removal%20of%20these%20%E2%80%98management%20only%E2%80%99%20servers%2C%20we%20will.%20%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20encourages%20Exchange%20Server%202016%20customers%20to%20adopt%20CU20%20as%20soon%20as%20possible%20to%20ensure%20uninterrupted%20delivery%20of%20any%20future%20security%20related%20fixes.%20After%20March%2016%2C%202021%2C%20only%20CU20%20or%20its%20successors%20will%20receive%20updates.%20During%20the%20Extended%20Support%20phase%2C%20only%20the%20latest%20CU%20is%20eligible%20to%20receive%20updates%20once%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fservicing-exchange-2013%2Fba-p%2F596398%22%20target%3D%22_blank%22%3Estandard%203%20month%20transition%3C%2FA%3E%26nbsp%3Bperiod%20of%20the%20prior%20CU%20has%20lapsed.%20%26nbsp%3B%3C%2FP%3E%3CP%3EUpdates%20will%20continue%20to%20be%20made%20available%20via%20Windows%20Update%20and%20the%20Microsoft%20Download%20Center.%20Additional%20lifecycle%20information%20for%20all%20Microsoft%20products%20is%20available%20on%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Flifecycle%2F%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3Edocs.microsoft.com%3C%2FA%3E.%3C%2FP%3E%3CP%3EWe%20hope%20this%20update%20was%20informative%20and%20we%20look%20forward%20to%20hearing%20your%20feedback%20and%20answering%20any%20questions%20you%20may%20still%20have.%3C%2FP%3E%3CP%3EThe%20Exchange%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1574110%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20hopefully%20many%20of%20you%20already%20know%20Exchange%20Server%202016%20enters%20the%20Extended%20Support%20phase%20of%20its%20product%20lifecycle%20on%20October%2014th%202020.%20That%E2%80%99s%20just%20a%20few%20short%20months%20away.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1574110%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAll%20Posts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeployment%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2242480%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2242480%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324116%22%20target%3D%22_blank%22%3E%40The_Exchange_Team%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EI%20recently%20stumbled%20onto%20this%20via%20multiple%20other%20links.%26nbsp%3B%20I%20would%20caution%20MS%20on%20it's%20aggressive%20approach%20to%20forcing%20everyone%20to%20the%20cloud%20and%20forgetting%20that%20there%20are%20MANY%20disconnected%2Fair-gapped%20networks%20where%20MS%20products%20are%20the%20only%20approved%20tool.%26nbsp%3B%20I%20support%203%20of%20those%20types%20of%20environments%20in%20my%20current%20role.%20I%20use%202%20more%20for%20a%20total%20of%205.%20I%20just%20submitted%20design%20plans%20for%20a%206th%20totally%20disconnected%20network.%3CBR%20%2F%3E%3CBR%20%2F%3ECloud%20is%20NOT%20the%20end%20all%20be%20all.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2590306%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202016%20and%20the%20End%20of%20Mainstream%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2590306%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F164282%22%20target%3D%22_blank%22%3E%40Lukas%20Sassl%3C%2FA%3E%26nbsp%3B%2C%20kindly%20guide%20plesae%3C%2FP%3E%3CP%3EThis%20article%20states%3C%2FP%3E%3CP%3E%3CSPAN%3E%22After%20June%2015%2C%202021%2C%20only%20CU21%20or%20its%20successors%20will%20receive%20updates%22%20but%20we%20have%20received%20SU%20July%20for%20CU%2020%20as%20well.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20are%20at%20CU%2019%20and%20looking%20to%20apply%20July%20SU's%20which%20we%20know%20are%20only%20applicable%20to%20CU20%20and%20CU%2021.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20currently%20do%20have%20third%20party%20applications%20which%20have%20not%20yet%20announced%20support%20for%20CU%2021%20and%20we%20have%20registered%20support%20cases%20with%20them%20for%20a%20time%20line.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMy%20point%20is%20if%20we%20go%20for%20CU%2020%20and%20apply%20July%20SU's%20then%20according%20t%20this%20article%20only%20CU%2021%20will%20get%20any%20future%20security%20updates%2C%20so%20should%20we%20target%2021%20or%20go%20with%20CU%2020%2C%20because%20not%20looking%20to%20perform%20another%20CU%20update%20repeat%20in%20few%20days%2C%20hence%20looking%20for%20advise.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ECan%20we%20have%20at%20least%20support%20End%20date%20for%20CU20%20anywhere%3F%20As%20per%20documentation%20(n-1)%20rule%2C%20CU20%20was%20released%20on%20March%2016th%20and%20CU%2021%20released%20on%20June%2029th%20%2C%20so%20CU%2020%20will%20be%20supported%20till%2029th%20September%202021%2C%20please%20assist%20if%20this%20is%20correct%20prediction%20for%20support%20end%20date%20for%20CU%2020.%20This%20will%20help%20us%20to%20make%20a%20decision%20for%20CU%2020%20because%20for%2021%20need%20to%20wait%20for%20support%20announcements%20from%20vendors%20e.g.%20backup%20sofware%20vendor%20etc.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Feb 12 2021 07:22 AM
Updated by: