%3CLINGO-SUB%20id%3D%22lingo-sub-858555%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Extending%20End%20of%20Support%20for%20Exchange%20Server%202010%20to%20October%2013th%2C%202020%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-858555%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20should%20probably%20mention%20Exchange%202010%20can%20also%20run%20on%20Windows%202012%20(non%20R2%20version)%20-%20just%20as%20on%20option%20to%20avoid%20lack%20of%20support%20for%20Windows%20Server%202008%20or%202008%20R2.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20this%20support%20extension%20of%20Exchange%202010%20also%20includes%20scenarios%20with%20Exchange%20Online%20like%3A%3C%2FP%3E%3CP%3E-%20legacy%20public%20folder%20migrations%20to%20Exchange%20Online%3C%2FP%3E%3CP%3E-%20pure%20Exchange%202010%20hybrid%20installations%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-858591%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Extending%20End%20of%20Support%20for%20Exchange%20Server%202010%20to%20October%2013th%2C%202020%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-858591%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEDITED%3E%3C%2FEDITED%3E%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%2F32461%22%20target%3D%22_blank%22%3E%40Sascha%20Schmatz%3C%2FA%3E%26nbsp%3B%20-%20Correct.%20Exchange%20Server%202010%20is%20also%20supported%20on%20Windows%20Server%202012%20and%202012%20R2%20(with%20Update%20Rollup%2026%20for%20SP3%20as%20we%20stated%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FThe-Microsoft-Hybrid-Agent-Public-Preview%2Fba-p%2F608939%22%20target%3D%22_self%22%3Ehere%3C%2FA%3E%26nbsp%3B%22%3CSPAN%3Ewe%E2%80%99re%20announcing%20here%20that%20we%26nbsp%3B%3C%2FSPAN%3E%3CI%3Ewill%3C%2FI%3E%3CSPAN%3E%26nbsp%3Bsupport%20Exchange%20Server%202010%20installed%20on%20Windows%20Server%202012%20R2%20with%20the%20upcoming%20release%20of%20Update%20Rollup%2026%20for%20Exchange%20Server%202010%20SP3.%20We%E2%80%99re%20doing%20that%20so%20if%20you%20really%20want%20to%20add%20another%20Exchange%202010%20server%20to%20your%20org%2C%20on%20Windows%20Server%202012%20R2%2C%20you%20can.%3C%2FSPAN%3E%22)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20really%20don't%20think%20customers%20should%20start%20re-deploying%202010%20on%20top%20of%202012%20or%202012%20R2%20just%20to%20avoid%20the%20ESU%20though%20-%20that's%20an%20awful%20lot%20of%20work.%20But%20if%20a%20new%202010%20server%20for%20some%20reason%20has%20to%20be%20added%20to%20the%20org%2C%20then%20doing%20it%20on%202012%20R2%20makes%20sense.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYes%20to%20the%20other%20scenarios.%20Exchange%202010%20remains%20supported%20until%20Oct%2013%2C%202020.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-753591%22%20slang%3D%22en-US%22%3EMicrosoft%20Extending%20End%20of%20Support%20for%20Exchange%20Server%202010%20to%20October%2013th%2C%202020%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-753591%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20investigating%20and%20analyzing%20the%20deployment%20state%20of%20an%20extensive%20number%20of%20Exchange%20customers%20we%20have%20decided%20to%20move%20the%20end%20of%20Extended%20Support%20for%20Exchange%20Server%202010%20from%20January%2014%3CSUP%3Eth%3C%2FSUP%3E%202020%20to%20October%2013%3CSUP%3Eth%3C%2FSUP%3E%202020.%3C%2FP%3E%0A%3CP%3EOur%20commitment%20to%20meeting%20the%20evolving%20needs%20of%20our%20customers%20is%20as%20strong%20as%20ever%2C%20and%20we%20recognize%20discontinuing%20support%20for%20a%20product%20that%20has%20been%20as%20popular%20and%20reliable%20as%20Exchange%20Server%202010%20can%20be%20an%20adjustment.%20We%20also%20know%20that%20some%20of%20you%20are%20in%20the%20midst%20of%20upgrades%20to%20a%20newer%20version%20of%20Exchange%20Server%20on-premises%2C%20or%20more%20transformative%20migrations%20to%20the%20cloud%20with%20Office%20365%20and%20Exchange%20Online.%20With%20this%20in%20mind%2C%20we%20are%20extending%20end%20of%20support%20to%20October%2013%3CSUP%3Eth%3C%2FSUP%3E2020%20to%20give%20Exchange%20Server%202010%20customers%20more%20time%20to%20complete%20their%20migrations.%20This%20extension%20also%20aligns%20with%20the%20end%20of%20support%20for%20Office%202010%20and%20SharePoint%20Server%202010.%3C%2FP%3E%0A%3CP%3EAfter%20October%2013%3CSUP%3Eth%3C%2FSUP%3E2020%2C%20Microsoft%20will%20no%20longer%20provide%20technical%20support%20for%20problems%20that%20may%20occur%20including%3A%20bug%20fixes%20for%20issues%20that%20are%20discovered%20and%20that%20may%20impact%20the%20stability%20and%20usability%20of%20the%20server%2C%20security%20fixes%20for%20vulnerabilities%20that%20are%20discovered%20and%20that%20may%20make%20the%20server%20vulnerable%20to%20security%20breaches%2C%20and%20time%20zone%20updates.%20Your%20installation%20of%20Exchange%202010%20will%2C%20of%20course%2C%20continue%20to%20run%20after%20this%20date%3B%20however%2C%20due%20to%20the%20changes%20and%20potential%20%26nbsp%3Bend%20of%20support%20risks%2C%20we%20strongly%20recommend%20you%20migrate%20from%20Exchange%202010%20as%20soon%20as%20possible.%3C%2FP%3E%0A%3CP%3EAs%20a%20reminder%2C%20if%20Exchange%20Server%202010%20is%20running%20on%20Windows%20Server%202008%20or%20Windows%20Server%202008%20R2%2C%20it's%20important%20to%20consider%20how%20you%20will%20obtain%20security%20updates%20for%20the%20underlying%20operating%20system%20too.%20Please%20read%20more%20about%20your%20options%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fcloud-platform%2Fwindows-server-2008%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3EPlease%20know%20that%20we%20can%20help.%20If%20you%20have%20a%20complex%20deployment%2C%20or%20if%20you%20simply%20don%E2%80%99t%20have%20the%20time%20or%20resources%20to%20dedicate%20to%20a%20project%20like%20this%2C%20there%20are%20plenty%20of%20ways%20to%20get%20help.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EFirstly%2C%20if%20you%20are%20migrating%20to%20Office%20365%20and%20Exchange%20Online%2C%20you%20may%20be%20eligible%20to%20use%20the%20free%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Ffasttrack%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20FastTrack%20service%3C%2FA%3E.%20FastTrack%20provides%20best%20practices%2C%20tools%2C%20and%20resources%20to%20make%20migration%20to%20Office%20365%20and%20Exchange%20Online%20as%20seamless%20as%20possible.%20Best%20of%20all%2C%20you%20have%20access%20to%20a%20support%20engineer%20that%20will%20walk%20you%20through%20your%20migration%2C%20from%20planning%20and%20design%20all%20the%20way%20to%20migrating%20the%20last%20mailbox.%3C%2FLI%3E%0A%3CLI%3ESecondly%2C%20if%20you%20run%20into%20any%20problems%20during%20your%20migration%20to%20Office%20365%20and%20you%20are%20not%20eligible%20for%20FastTrack%2C%20or%20if%20you%20are%20migrating%20to%20a%20newer%20version%20of%20Exchange%20Server%2C%20Microsoft%20can%20still%20help.%20Try%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20support%3C%2FA%3Eor%20the%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange%2Fct-p%2FExchange%22%20target%3D%22_self%22%3EExchange%20Technical%20Community%3C%2FA%3E.%3C%2FLI%3E%0A%3CLI%3EThirdly%2C%20you%20also%20might%20choose%20to%20engage%20a%20partner%20to%20help%20you.%20We%20have%20a%20great%20number%20of%20partners%20with%20deep%20skills%20in%20Exchange%2C%20and%20we%E2%80%99re%20sure%20one%20of%20them%20will%20be%20able%20to%20help%20you.%20You%20can%20browse%20a%20list%20of%20Exchange%20partners%20at%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsolution-providers%2Fhome%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsolution-providers%2Fhome%3C%2FA%3Eto%20find%20one%20in%20your%20location%20or%20that%20has%20skills%20in%20your%20industry.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EClearly%2C%20we%20think%20moving%20to%20Exchange%20Online%20and%20Office%20365%20is%20a%20good%20idea.%20We%20really%20do%20believe%20that%E2%80%99s%20where%20you%E2%80%99ll%20get%20access%20to%20the%20most%20secure%20and%20productive%20software%20with%20the%20lowest%20TCO.%20But%20over%20and%20above%20all%20of%20that%2C%20it%20gets%20you%20out%20of%20the%20upgrade%20business.%20If%20you%20migrate%20fully%20to%20Office%20365%20you%20really%20don%E2%80%99t%20need%20to%20worry%20about%20%E2%80%98big%20bang%E2%80%99%20version%20upgrades%20any%20more.%20You%20just%20have%20to%20keep%20a%20much%20smaller%20number%20of%20on-premises%20servers%20up%20to%20date%2C%20and%20you%E2%80%99re%20good.%3C%2FP%3E%0A%3CP%3EIf%20you%20do%20want%20to%20stay%20on-premises%20don%E2%80%99t%20forget%20that%20you%20cannot%20upgrade%20directly%20from%20Exchange%202010%20on-premises%20to%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FExchange-Server-2019-Now-Available%2Fba-p%2F608610%22%20target%3D%22_self%22%3EExchange%20Server%202019%3C%2FA%3E.%20You%20can%20upgrade%20to%20Exchange%202013%20or%202016%20directly%20from%20Exchange%202010%20and%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FExchange-On-Premises-Best-Practices-for-Migrations-from-2010-to%2Fba-p%2F845660%22%20target%3D%22_self%22%3Ewe%20recommend%20you%20upgrade%20to%20Exchange%202016%3C%2FA%3E%20if%20you%20have%20the%20choice.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3EGreg%20Taylor%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EDirector%20of%20Product%20Marketing%20-%20Exchange%20Server%2FOnline%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-753591%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20extending%20the%20end%20of%20support%20for%20Exchange%20Server%202010%20from%20January%2014%3CSUP%3Eth%3C%2FSUP%3E2020%20to%20October%2013%3CSUP%3Eth%3C%2FSUP%3E2020.%20Read%20more%20here.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-753591%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECommunity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeployment%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eexchange%202010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-876474%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Extending%20End%20of%20Support%20for%20Exchange%20Server%202010%20to%20October%2013th%2C%202020%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-876474%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20great%20news%20!%20But%20correct%20me%20if%20I%20am%20wrong%2C%20most%20people%20who%20have%202010%20exchange%2C%20it%20is%20installed%20on%20windows%20server%202008%20R2%20which%20has%20no%20more%20support%2C%20so%20the%20extension%20isn't%20of%20any%20use.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-877047%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Extending%20End%20of%20Support%20for%20Exchange%20Server%202010%20to%20October%2013th%2C%202020%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-877047%22%20slang%3D%22en-US%22%3E%3CP%3EWindows%20Server%202008%20R2%20is%20in%20broad%20extended%20supported%20until%20Jan%2014%202020%2C%20but%20customers%20can%20buy%20an%20Extended%20Security%20Update%20agreement%20for%20it.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4497181%2Flifecycle-faq-extended-security-updates%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4497181%2Flifecycle-faq-extended-security-updates%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1006238%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Extending%20End%20of%20Support%20for%20Exchange%20Server%202010%20to%20October%2013th%2C%202020%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1006238%22%20slang%3D%22en-US%22%3E%3CP%3Ewill%20sbs%202011%20support%20be%20extended%20as%20well%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1120803%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Extending%20End%20of%20Support%20for%20Exchange%20Server%202010%20to%20October%2013th%2C%202020%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1120803%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20in%20the%20camp%20that%20migrated%20from%20Exchange%202010%20to%20Office%20365.%3C%2FP%3E%3CP%3EWe%20have%20now%20completed%20the%20migration%20of%20all%20mailboxes%20and%20now%20wish%20to%20Decommission%20the%20Hybrid%20setup%20and%20also%20need%20to%20keep%20the%20AD%20Sync.%3C%2FP%3E%3CP%3EMicrosoft%20states%20that%20we%20need%20to%20keep%20one%20exchange%20server%20to%20be%20supported%20but%20our%20one%20and%20only%20server%20is%20Exchange%202010%20running%20on%202008%20R2%20so%20we%20need%20to%20decommission%20them.%20Updating%20the%20server%20and%2For%20upgrading%20the%20on%20prem%20exchange%20server%20is%20out%20of%20the%20question.%3C%2FP%3E%3CP%3EThere%20was%20some%20talk%20at%20Ignite%202017%20about%20creating%20a%20Hybrid%20Connector%20that%20would%20allow%20the%20removal%20of%20the%20last%20onprem%20exchange%20server.%26nbsp%3B%20Is%20Microsoft%20going%20to%20move%20forward%20on%20this%20idea%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1664011%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Extending%20End%20of%20Support%20for%20Exchange%20Server%202010%20to%20October%2013th%2C%202020%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1664011%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20here%20we%20are%20with%20Exchange%202010%20end%20of%20support%20coming%20soon%20on%20October%2013%2C%202020%20and%20no%20supported%20way%20to%20decommision%20last%20exchange%20server.%3CBR%20%2F%3Eso%20now%20we%20are%20attempting%20to%20install%20an%20Exchange%202016%20server%20on%20Server%202016%20to%20replace%20the%202010%20server.%3CBR%20%2F%3ESince%20the%20Exchange%202016%20server%20ISO%20now%20insists%20on%20detecting%20for%20Hybrid%20environments%2C%20complexity%20has%20been%20introduced%20to%20the%20Schema%20update%20phase%20causing%20setup.exe%20to%20fail.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThere%20does%20not%20seem%20to%20be%20a%20clear%20path%20to%20get%202016%20successfully%20installed.%3C%2FP%3E%3CP%3EExchange%20Online%20support%20refuses%20to%20help%20us%20as%20they%20state%20that%20this%20is%20an%20issue%20for%20the%20Exchange%20Onprem%20team.%3CBR%20%2F%3EWe%20are%20not%20an%20enterprise%20customer%20and%20thus%20do%20not%20have%20support%20fo%20onprem%20exchange%2C%20however%20we%20have%20support%20for%20Exchange%20Online.%3CBR%20%2F%3Esetup.exe%20is%20failing%20within%20communications%20to%20exchange%20online%20so%20they%20should%20support%20us.%3CBR%20%2F%3EWe%20don't%20even%20want%20to%20have%20an%20onprem%20Exchange%20server%20but%20Microsoft%20has%20made%20this%20a%20requirement%20for%20the%20admin%20tools.%3C%2FP%3E%3CP%3ECurrently%20have%20Full%20Hydrid%20Exchange%202010%20-%20Office%20365%20environment.%20Working%20great.%3CBR%20%2F%3ENeed%20to%20decommision%20exchange%202010%20server%20and%20replace%20with%20exchange%202016%20hybrid%20only.%3CBR%20%2F%3Etrying%20to%20install%20exchange%202016%20CU17%20ISO%20on%20a%20fresh%20Windows%20Server%202016%20install%3CBR%20%2F%3Eall%20prerequisites%20done%20according%20to%20%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fdeploy-new-installations%2Finstall-mailbox-role%3Fview%3Dexchserver-2016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fdeploy-new-installations%2Finstall-mailbox-role%3Fview%3Dexchserver-2016%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInstall%20account%20is%20a%20member%20of%20domain%20admins%2C%20enterprise%20admins%20and%20schema%20admins.%3CBR%20%2F%3Esetup.exe%20fails%20in%20Hybrid%20Deployment%20Check%3A%20Deserialization%20fails%3C%2FP%3E%3CP%3EFound%20documents%20stating%20that%20setup.exe%20wizard%20cannot%20be%20used%20in%20hybrid%20environment.%20The%20PrepareAD%20command%20must%20be%20run%20manually%20with%20the%20%2FTenantOrganizationConfig%20switch%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fprepare-ad-and-domains%3Fview%3Dexchserver-2016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fprepare-ad-and-domains%3Fview%3Dexchserver-2016%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2FTenantOrganizationConfig%20switch%20requires%20the%20Org%20Tenant%20XML%20file%3C%2FP%3E%3CP%3EFound%20document%20explaining%20the%20use%20of%20following%20command%20to%20get%20Org%20Tenant%20XML%20file%3A%3CBR%20%2F%3EGet-OrganizationConfig%20%7C%20Export-clixml%20-Path%20C%3A%5Ctemp%5CTenant.xml%3C%2FP%3E%3CP%3EFound%20various%20documents%20stating%20that%20PrepareAD%20still%20fails%20with%20%2FTenantOrganizationConfig%20switch.%3C%2FP%3E%3CP%3EFollowing%20document%20talks%20about%20registry%20key%20to%20bypass%20Hydrid%20detection%20during%20install%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F05c1e110-67a7-4941-8995-4899dc27543f%2Fexchange-2016-prepare-ad-fails-with-systemaccessviolationexception%3Fforum%3DExch2016SD%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F05c1e110-67a7-4941-8995-4899dc27543f%2Fexchange-2016-prepare-ad-fails-with-systemaccessviolationexception%3Fforum%3DExch2016SD%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20correct%20method%20to%20proceed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20is%20Microsoft%20going%20to%20develop%20a%20tool%20for%20recipient%20management%20that%20does%20not%20require%20on%20Onprem%20exchange%20server%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1691082%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Extending%20End%20of%20Support%20for%20Exchange%20Server%202010%20to%20October%2013th%2C%202020%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1691082%22%20slang%3D%22en-US%22%3E%3CP%3EA%20member%20of%20the%20Exchange%20and%20Outlook%20Beta%20team%20reached%20out%20to%20me%20help%20out.%26nbsp%3B%20Thank%20you.%3C%2FP%3E%3CP%3EFinally%20got%20exchange%202016%20installed%20in%20our%20Hybrid%20environment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20prepare%20Active%20Directory%20document%20(Step%202)%20has%20a%20small%20statement%20at%20the%20end%20%22%3CEM%3EImportant.%20If%20you%20have%20a%20hybrid%20deployment%20configured%20between%20your%20on-premises%20organization%20and%20Exchange%20Online%2C%20add%20the%26nbsp%3B%2FTenantOrganizationConfig%26nbsp%3Bswitch%20to%20the%20command%3C%2FEM%3E.%22%20This%20comment%20is%20really%20important%20but%20also%20needs%20some%20further%20instruction.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20are%20the%20important%20beginning%20steps%20if%20you%20already%20have%20a%20Hybrid%20onprem-online%20environment%3A%3C%2FP%3E%3CP%3E1)%20Export%20your%20Tenant%20Organization%20config%20xml%20file%20with%20the%20following%20powershell%20command%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CEM%3EGet-OrganizationConfig%20%7C%20Export-clixml%20-Path%20C%3A%5Ctemp%5CTenant.xml%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E2)%20Prepare%20AD%20with%20this%20command%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CEM%3ESetup%20%2FPrepareAD%20%2FTenantOrganizationconfig%3AC%3A%5Ctemp%5CTenant.xml%20%2FIAcceptExchangeServerLicenseTerms%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CEM%3E3)%20Reboot%3C%2FEM%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CEM%3E4)%20Prepare%20AD%20again%20with%20this%20command%3A%3C%2FEM%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CEM%3Esetup.exe%20%2FPrepareAD%20%2FIAcceptExchangeServerLicenseTerms%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CEM%3E5)%20Reboot%3C%2FEM%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CEM%3E6)%20run%20setup.exe%20to%20complete%20UI%20install%3C%2FEM%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E

After investigating and analyzing the deployment state of an extensive number of Exchange customers we have decided to move the end of Extended Support for Exchange Server 2010 from January 14th 2020 to October 13th 2020.

Our commitment to meeting the evolving needs of our customers is as strong as ever, and we recognize discontinuing support for a product that has been as popular and reliable as Exchange Server 2010 can be an adjustment. We also know that some of you are in the midst of upgrades to a newer version of Exchange Server on-premises, or more transformative migrations to the cloud with Office 365 and Exchange Online. With this in mind, we are extending end of support to October 13th 2020 to give Exchange Server 2010 customers more time to complete their migrations. This extension also aligns with the end of support for Office 2010 and SharePoint Server 2010.

After October 13th 2020, Microsoft will no longer provide technical support for problems that may occur including: bug fixes for issues that are discovered and that may impact the stability and usability of the server, security fixes for vulnerabilities that are discovered and that may make the server vulnerable to security breaches, and time zone updates. Your installation of Exchange 2010 will, of course, continue to run after this date; however, due to the changes and potential  end of support risks, we strongly recommend you migrate from Exchange 2010 as soon as possible.

As a reminder, if Exchange Server 2010 is running on Windows Server 2008 or Windows Server 2008 R2, it's important to consider how you will obtain security updates for the underlying operating system too. Please read more about your options here.

Please know that we can help. If you have a complex deployment, or if you simply don’t have the time or resources to dedicate to a project like this, there are plenty of ways to get help.

  • Firstly, if you are migrating to Office 365 and Exchange Online, you may be eligible to use the free Microsoft FastTrack service. FastTrack provides best practices, tools, and resources to make migration to Office 365 and Exchange Online as seamless as possible. Best of all, you have access to a support engineer that will walk you through your migration, from planning and design all the way to migrating the last mailbox.
  • Secondly, if you run into any problems during your migration to Office 365 and you are not eligible for FastTrack, or if you are migrating to a newer version of Exchange Server, Microsoft can still help. Try Microsoft support or the Exchange Technical Community.
  • Thirdly, you also might choose to engage a partner to help you. We have a great number of partners with deep skills in Exchange, and we’re sure one of them will be able to help you. You can browse a list of Exchange partners at https://www.microsoft.com/en-us/solution-providers/home to find one in your location or that has skills in your industry.

Clearly, we think moving to Exchange Online and Office 365 is a good idea. We really do believe that’s where you’ll get access to the most secure and productive software with the lowest TCO. But over and above all of that, it gets you out of the upgrade business. If you migrate fully to Office 365 you really don’t need to worry about ‘big bang’ version upgrades any more. You just have to keep a much smaller number of on-premises servers up to date, and you’re good.

If you do want to stay on-premises don’t forget that you cannot upgrade directly from Exchange 2010 on-premises to Exchange Server 2019. You can upgrade to Exchange 2013 or 2016 directly from Exchange 2010 and we recommend you upgrade to Exchange 2016 if you have the choice.

Greg Taylor

Director of Product Marketing - Exchange Server/Online

8 Comments
Contributor

You should probably mention Exchange 2010 can also run on Windows 2012 (non R2 version) - just as on option to avoid lack of support for Windows Server 2008 or 2008 R2.

 

So this support extension of Exchange 2010 also includes scenarios with Exchange Online like:

- legacy public folder migrations to Exchange Online

- pure Exchange 2010 hybrid installations

<edited, and apologies for any confusion>

 

@Sascha Schmatz  - Correct. Exchange Server 2010 is also supported on Windows Server 2012 and 2012 R2 (with Update Rollup 26 for SP3 as we stated here "we’re announcing here that we will support Exchange Server 2010 installed on Windows Server 2012 R2 with the upcoming release of Update Rollup 26 for Exchange Server 2010 SP3. We’re doing that so if you really want to add another Exchange 2010 server to your org, on Windows Server 2012 R2, you can.")

 

We really don't think customers should start re-deploying 2010 on top of 2012 or 2012 R2 just to avoid the ESU though - that's an awful lot of work. But if a new 2010 server for some reason has to be added to the org, then doing it on 2012 R2 makes sense. 

 

Yes to the other scenarios. Exchange 2010 remains supported until Oct 13, 2020. 

Occasional Visitor

This is great news ! But correct me if I am wrong, most people who have 2010 exchange, it is installed on windows server 2008 R2 which has no more support, so the extension isn't of any use. 

Windows Server 2008 R2 is in broad extended supported until Jan 14 2020, but customers can buy an Extended Security Update agreement for it. https://support.microsoft.com/en-us/help/4497181/lifecycle-faq-extended-security-updates

Occasional Visitor

will sbs 2011 support be extended as well?

 

New Contributor

We are in the camp that migrated from Exchange 2010 to Office 365.

We have now completed the migration of all mailboxes and now wish to Decommission the Hybrid setup and also need to keep the AD Sync.

Microsoft states that we need to keep one exchange server to be supported but our one and only server is Exchange 2010 running on 2008 R2 so we need to decommission them. Updating the server and/or upgrading the on prem exchange server is out of the question.

There was some talk at Ignite 2017 about creating a Hybrid Connector that would allow the removal of the last onprem exchange server.  Is Microsoft going to move forward on this idea?

New Contributor

So here we are with Exchange 2010 end of support coming soon on October 13, 2020 and no supported way to decommision last exchange server.
so now we are attempting to install an Exchange 2016 server on Server 2016 to replace the 2010 server.
Since the Exchange 2016 server ISO now insists on detecting for Hybrid environments, complexity has been introduced to the Schema update phase causing setup.exe to fail.


There does not seem to be a clear path to get 2016 successfully installed.

Exchange Online support refuses to help us as they state that this is an issue for the Exchange Onprem team.
We are not an enterprise customer and thus do not have support fo onprem exchange, however we have support for Exchange Online.
setup.exe is failing within communications to exchange online so they should support us.
We don't even want to have an onprem Exchange server but Microsoft has made this a requirement for the admin tools.

Currently have Full Hydrid Exchange 2010 - Office 365 environment. Working great.
Need to decommision exchange 2010 server and replace with exchange 2016 hybrid only.
trying to install exchange 2016 CU17 ISO on a fresh Windows Server 2016 install
all prerequisites done according to :
https://docs.microsoft.com/en-us/exchange/plan-and-deploy/deploy-new-installations/install-mailbox-r...

 

Install account is a member of domain admins, enterprise admins and schema admins.
setup.exe fails in Hybrid Deployment Check: Deserialization fails

Found documents stating that setup.exe wizard cannot be used in hybrid environment. The PrepareAD command must be run manually with the /TenantOrganizationConfig switch


https://docs.microsoft.com/en-us/exchange/plan-and-deploy/prepare-ad-and-domains?view=exchserver-201...

 

/TenantOrganizationConfig switch requires the Org Tenant XML file

Found document explaining the use of following command to get Org Tenant XML file:
Get-OrganizationConfig | Export-clixml -Path C:\temp\Tenant.xml

Found various documents stating that PrepareAD still fails with /TenantOrganizationConfig switch.

Following document talks about registry key to bypass Hydrid detection during install:
https://social.technet.microsoft.com/Forums/en-US/05c1e110-67a7-4941-8995-4899dc27543f/exchange-2016...

 

What is the correct method to proceed?

 

When is Microsoft going to develop a tool for recipient management that does not require on Onprem exchange server?

New Contributor

A member of the Exchange and Outlook Beta team reached out to me help out.  Thank you.

Finally got exchange 2016 installed in our Hybrid environment.

 

The prepare Active Directory document (Step 2) has a small statement at the end "Important. If you have a hybrid deployment configured between your on-premises organization and Exchange Online, add the /TenantOrganizationConfig switch to the command." This comment is really important but also needs some further instruction.

 

Here are the important beginning steps if you already have a Hybrid onprem-online environment:

1) Export your Tenant Organization config xml file with the following powershell command: 

Get-OrganizationConfig | Export-clixml -Path C:\temp\Tenant.xml

2) Prepare AD with this command:

Setup /PrepareAD /TenantOrganizationconfig:C:\temp\Tenant.xml /IAcceptExchangeServerLicenseTerms

3) Reboot

4) Prepare AD again with this command:

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

5) Reboot

6) run setup.exe to complete UI install