Home
%3CLINGO-SUB%20id%3D%22lingo-sub-400398%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-400398%22%20slang%3D%22en-US%22%3E%3CP%3EOk%2C%20I%20guess%20I%20want%20to%20throw%20my%202%20cents%20into%20LTSC%20piggy%20bank%20%3A-).%26nbsp%3BSo%2C%20we%20have%20big%20Enterprise%20organization.%20Yep%2C%20one%20of%20those%20big%20ones%20that%20everyone%20knows.%20EVERYONE!%20And%20of%20course%20just%20like%20everyone%20else%20on%20this%20planet%20scared%20of%20staying%20on%20W7%20because%20soon%20will%20be%20not%20supported%2C%20and%20as%20result%20non-compliance%2C%20audit%2C%20regulators%20and%20big%2C%20big%20fines!%20Does%20not%20sound%20good!%26nbsp%3BSo%20started%20moving%20with%20SAC.%201709.%20Well%2C%20because%20it%20was%201%20year%20ago.%201803%20was%20skipped%20-%20thanks%20to%20MS%20for%20announcing%20new%20strategy%20of%20supporting%20fall%20releases%20for%2030%20months%20instead%20of%20originally%20planned%2018%20months!%20Now%20got%201809.%20Yes%2C%20it%20was%20mess!%20In%20fact%20it%20was%20disaster.%20You%20were%20saying%2009%20means%20September%3F%20Yeah%20right!%20How%20about%20November%3F%20October%20was%20bug-fixes%20time%20ha-ha-ha!%20Halloween%20of%20bugs.%20But%20as%20you%20know%2C%20November%20is%20the%20time%20when%20things%20slow%20down.%20Why%3F%20Well%2C%20many%20reasons.%20First%20it%20is%20new%20fiscal%20year.%20First%20month%20is%20always%20slow.%20Besides%20everybody%20is%20in%20the%20Christmas%20mood.%20Santa%20coming%20to%20town%20in%20case%20you%20did%20not%20know.%20Then%20it%20is%20January%2C%20best%20time%20to%20go%20Dominican%2C%20Mexico%20or%20Cuba%20-%20prices%20doing%20down!%20Who%20does%20not%20like%20cheap%20vacation%20all-inclusive%3F%20Then%20February%20things%20start%20picking-up%20slowly.%20But%20hey%2C%20now%20business%20got%20scary%2C%20they%20want%20to%20test%20their%20Applications%2C%20but%20they%20don't%20have%20time.%20And%20you%20know%2C%20all%20those%203rd%20party%20agents%3F%20Security%20agents%3F%20Have%20you%20heard%20about%20them%3F%20They%20also%20may%20not%20work%20in%201809.%20So%20if%20we%20push%201809%20we%20may%20break%20all%20machines.%20Risk%20is%20real%2C%20and%20everybody%20scary.%20But%20things%20not%20getting%20any%20better.%20Soon%20it%20will%20be%201909%20and%20it%20only%20will%20be%20worse.%20So%20this%20is%20a%20road%20to%20perdition.%20What%20you%20suggest%3F%20Stay%20on%201709%20or%20jump%20to%201809%3F%20What%20if%20something%20happens%3F%20It%20will%20be%20the%20END.%20And%20nobody%20want%20the%20END.%20Everybody%20want%20to%20live.%20Everyone%20want%20to%20retire%20happy%20ha-ha-ha!%20Now%20let's%20see%20why%20SAC%20is%20better%20(as%20per%20you%20list)%3A%201.%20Edge%20is%20missing.%20Sure.%20But%20Edge%20is%20disaster.%20There%20are%20problems%20with%20SSO%20via%20ADFS%20because%20MS%20did%20not%20allow%20any%20browser%20to%20access%20ADFS%2C%20each%20Agent%20string%20must%20be%20explicitly%20written%20into%20ADFS%20configuration.%20You%20saying%20add%20this%20to%20ADFS%3F%20Sure.%20But%20do%20you%20remember%20we%20were%20talking%20about%20large%20enterprise%3F%205-second%20command%20to%20execute%20in%20PROD%20environment%20takes%20easily%206%20months.%20Why%3F%20Don't%20ask.%20Just%20believe!%20So%20for%20any%20changes%20we%20are%20looking%20months%20and%20months%20to%20implement.%202.%20Cortana.%20We%20disabled%20it%20in%20SAC%20anyway%2C%20so%20why%20bother%3F%20Nobody%20use%20Cortana%2C%20except%20MS%20people%20who%20present%20something%20on%20Ignite!%203.%20App%20Store.%20Most%20enterprise%20block%20it%20-%20otherwise%20this%20is%20a%20Pandora%20box!%20If%20users%20start%20installing%20what%20they%20want%20this%20will%20be%20the%20end!%204.%20Same%20thing%20for%20many%20other%20things.%20So%20what%20really%20business%20need%3F%20They%20need%20their%20Applications.%20And%20they%20want%20them%20to%20work%20stable%20today%2C%20tomorrow%20and%20in%205%20years%2C%20day%20after%20day.%20And%20if%20changes%20occurs%20so%20often%20and%20could%20break%20things%2C%20this%20is%20not%20good.%20Did%20I%20almost%20convinced%20you%20why%20large%20enterprises%20should%20go%20with%20LTSC%3F%20Ha-ha-ha!%20Your%20turn!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-370204%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-370204%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F301148%22%20target%3D%22_blank%22%3E%40WindowsChamp%3C%2FA%3E%26nbsp%3Bbeat%20me%20to%20it.%20Again!%26nbsp%3B%3CIMG%20id%3D%22smileyhappy%22%20class%3D%22emoticon%20emoticon-smileyhappy%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fi%2Fsmilies%2F16x16_smiley-happy.png%22%20alt%3D%22Smiley%20Happy%22%20title%3D%22Smiley%20Happy%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369671%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369671%22%20slang%3D%22en-US%22%3E%3CP%3EJohn%2C%20very%20nice%20overview.%20I%20work%20with%20OEM's%20that%20build%20appliances%20and%20I%20provide%20guidance%20primarily%20for%20OEM's%20rather%20than%20corporate%20america.%26nbsp%3B%20For%20those%20that%20are%20interested%20in%20more%20details%20around%20how%20to%20license%20via%20the%20OEM%20channel%20please%20have%20a%20look%20at%20my%20blog%20on%20Windows%20LTSB%2FLTSC%20here%3A%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Focs.arrow.com%2Fmsembedded%2Fblog%2Fto-update-that-is-the-question%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Focs.arrow.com%2Fmsembedded%2Fblog%2Fto-update-that-is-the-question%2F%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20would%20also%20mention%20that%20you%20did%20state%20it%20is%20a%20free%20upgrade%20between%20LTSC%20editions%20and%20that%20is%20not%20the%20case%20in%20the%20OEM%20channel.%20In%20fact%20in-place%20upgrades%20are%20prevented%20with%20the%20LTSC%20edition%20and%20it%20does%20require%20the%20purchase%20of%20a%20full%20new%20upgrade%20license.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-358082%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-358082%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20is%20even%20included%20in%20the%20Server%20SKU%20%3AD%3C%2Fimg%3E%20I%20have%20asked%20about%20Xbox%20app%20on%20another%20thread%20about%20Server%20security%20hardening%20and%20only%20got%20an%20answer%20that%20some%20role%2Ffeature%20might%20need%20Xbox%20to%20do%20something%2C%20like%20VDI%20or%20RDS%20(remote%20workers%20wanting%20to%20play%20some%20games%3F%3A)).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-357930%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357930%22%20slang%3D%22en-US%22%3EMaybe%20there%20wouldn't%20be%20so%20much%20interest%20in%20LTSC%20if%20your%20core%20offerings%20weren't%20so%20full%20of%20bloat.%20No%20IT%20professional%20asked%20for%20your%20data%20spigot%20aka%20telemetry.%20You%20can%20try%20and%20cram%20Edge%20down%20our%20throats%20all%20you%20want%20but%20we%20don't%20want%20it.%20We%20didn't%20ask%20for%20nor%20do%20we%20want%20all%20the%20consumer%20apps%20suggestions%2C%20chibi%20graphics%20and%20gamification.%20The%20problem%20is%20that%20you%20(Microsoft)%20have%20an%20agenda%20that%20does%20not%20align%20with%20the%20stated%20needs%20of%20IT%20professionals%20and%20advanced%20users.%20Rather%20than%20deliver%20the%20products%20that%20we%20want%2C%20you'd%20rather%20try%20to%20gaslight%20us%20into%20thinking%20that%20we're%20crazy%20for%20wanting%20an%20unbloated%20OS.%20An%20Xbox%20app%20in%20Windows%2010%20Enterprise%3F%20Really%20dude%3F%20Really%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-341124%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-341124%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-note-content%22%3E%3CDIV%20class%3D%22lia-note-body%20lia-component-body%22%3E%3CP%3EDear%20John%2C%3C%2FP%3E%3CP%3E%3CBR%20%2F%3Ei've%20recently%20read%20your%20interesting%20post%20about%20WIN%2010%20LTSC.%3C%2FP%3E%3CP%3EAt%20the%20moment%20i%20am%20working%20on%20a%20project%20for%20a%20company%20to%20roll%20out%20WIN%2010%20and%20planning%20to%20use%20LTSC.%3C%2FP%3E%3CP%3EI%20have%20one%20question%20about%20the%20following%20sentences%20in%20your%20text%3A%3C%2FP%3E%3CP%3E%22Each%20LTSC%20release%20receives%2010%20years%20of%20servicing%20and%20support%5Bi%5D.%20During%20the%20life%20of%20a%20LTSC%20release%2C%20you%20can%20upgrade%20your%20devices%20to%20the%20next%20or%20latest%20LTSC%20release%20free%20of%20charge%20using%20an%20in-place%20upgrade%2C%20or%20to%20any%20currently%20supported%20release%20of%20Windows%2010.%20Because%20the%20LTSC%20is%20technically%20its%20own%20SKU%2C%20an%20upgrade%20is%20required%20from%20Windows%2010%20Enterprise%20LTSC%20to%20Windows%2010%20Enterprise%2C%20which%20supports%20the%20Semi-Annual%20Channel.%22%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIs%20the%20meaning%20right%2C%20that%20i%20will%20get%20each%20LTSC%20upgrade%20within%20ten%20years%20for%20free%3F%3F%3F%20That%20will%20be%20a%20great%20feature.%3C%2FP%3E%3CP%3ELike%20in%205%20years%20when%20there%20is%20for%20example%20version%202105%2C%20I%20will%20get%20that%20for%20free%3F%3C%2FP%3E%3CP%3ECan%20I%20ask%20you%20where%20you've%20got%20that%20information%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThanks%20in%20advance%20and%20kind%20regards%2C%3C%2FP%3E%3CP%3EMarco%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22lia-note-actions%20clearfix%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22lia-quilt-column%20lia-quilt-column-24%20lia-quilt-column-single%20lia-quilt-column-main-content%22%3E%3CDIV%20class%3D%22lia-quilt-column-alley%20lia-quilt-column-alley-single%22%3E%3CDIV%20class%3D%22lia-note-actions%20clearfix%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-335129%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-335129%22%20slang%3D%22en-US%22%3E%3CP%3EMS%20is%20touting%20Autopilot%20(and%20Intune)%20to%20be%20that%20next%20%22image%22%20deployment%20tool%20(not%20really%20an%20image%20in%20the%20regular%20sense%2C%20just%20a%20set%20of%20settings%20that%20will%20prepare%20Windows%20for%20work).%20But%20i%20can't%20see%20this%20being%20used%20in%20public%20sector%20where%20you%20don't%20know%20who%20will%20win%20new%20PC%20shipment%20tender.%20Could%20be%20some%20smallish%20local%20retailer%20who%20never%20heard%20about%20Autopilot.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-335127%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-335127%22%20slang%3D%22en-US%22%3E%3CP%3EActually%2C%20that's%20exactly%20what%20i%20meant%20in%20my%20comment%2C%20that%20users%20don't%20care%20for%20user%20features%2C%20so%20the%20only%20incentive%20for%20IT%20admins%20to%20install%20updates%20every%206%20months%20is%20to%20stay%20secure%20and%20to%20get%20those%20hidden%20to%20the%20eye%20improvements%20(DO%2C%20Autopilot%2C%20etc.).%20The%20problem%20is%20that%20you%20can't%20%22sell%22%20these%20updates%20to%20users%2Fexecs.%20They%20need%20something%20useful%20they%20can%20get%20their%20hands%20on.%20As%20they%20don't%20get%20it%2C%20they%20are%20just%20annoyed%20with%20often%20updates%20that%20take%20long%20to%20install%20and%20don't%20see%20point%20in%20that.%20You%20want%20me%20to%20explain%20spreadsheet%20users%20how%20great%20recent%20DO%20improvements%20were%3F%20Of%20course%2C%20you%20can%20have%20an%20argument%20that%20it%20can%20save%20internet%20traffic%20cost%20and%20make%20less%20impact%20on%20network%20(in%20DO%20case).%20But%20on%20my%20previous%20job%20updates%20were%20handled%20via%20WSUS%20and%20we%20had%20unlimited%20broadband%20internet%2C%20so%20DO%20wouldn't%20do%20much%20for%20us.%20Anyway%2C%20IT%20admins%20are%20now%20tasked%20to%20do%20big%20updates%20twice%20a%20year%2C%20users%20don't%20see%20value%20in%20this.%20Background%20improvements%20are%20neat%2C%20if%20you%20have%20real%20use%20for%20them%2C%20but%20in%20the%20end%2C%20companies%20need%20a%20stable%20and%20secure%20OS%20to%20do%20work%20(by%20secure%20i%20mean%20just%20monthly%20security%20updates).%20This%20can%20be%20reduced%20to%201%20update%20per%20year.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-335116%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-335116%22%20slang%3D%22en-US%22%3E%3CP%3EA%20whole%20lot%20of%20the%20problem%20with%20people%20deploying%20LTSB%2FLTSC%20to%20do%20the%20desktop%20(us%20included%20BTWbtwould%20be%20solved%20if%20the%20Enterprise%20and%20Education%20versions%20of%20Windows%20were%20exactly%20that%20%26amp%3B%20not%20just%20re-badged%20versions%20of%20Home%20with%20a%20few%20enterprise%20features%20turned%20on.%20Lose%20Cortana%2C%20Windows%20Store%2C%20Candy%20Crush%2C%20Xbox%2C%20Music%2C%20etc.%20and%20you'd%20be%20half-way%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAdd%20in%20some%20decent%20modern%20tools%20to%20customise%20and%20control%20the%20deployment%20of%20images%20(SCCM%20is%20way%20overkill%20for%20anyone%20with%20less%20than%20thousands%20of%20seats%20(we%20tried%20-%20we%20needed%20more%20resources%20to%20run%20SC%20than%20the%20rest%20of%20the%20organisation)%2C%20WDS%20seems%20stuck%20in%20the%20Windows%207%20era)%20and%20the%20whole%20LTSB%2FLTSC%20on%20the%20Desktop%20issue%20would%20go%20away.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-335088%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-335088%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20key%20element%20that%20haven't%20been%20touched%20in%20this%20article%20is%20the%20capability%20of%20the%20features%20in%20Windows%2010%20from%201511%20to%201809%2C%20John%20posted%20a%20nice%20Picture%20of%20all%20the%20new%20features%20that%20has%20been%20added%20to%20Windows%2010%2C%20and%20some%20ppl%20mock%20those%20and%20say%20that%20their%20users%20does'nt%20need%20to%20connect%20their%20phone%20or%20whatever.%20But%20they%20miss%20a%20vital%20Point%20and%20that's%20the%20capability%20of%20the%20said%20feature%2C%20for%20example%20Delivery%20Optimization%20%22DO%22%20the%20functionality%20of%20that%20so%20important%20feature%20has%20vastly%20imoproved%20since%20launch%2C%20and%20that's%20not%20the%20only%20feature%20that%20has%20been%20improved.%20If%20your%20on%20LTSC%20for%20the%2010%20year%20support%2C%20god%20knows%20what%20all%20background%20functionality%20you%20will%20miss%20out%20on.%20Being%20on%20LTSC%20for%20a%20longer%20time%20will%20also%20get%20you%20further%20behind%20the%20real%20World%20so%20when%20the%20day%20comes%20to%20upgrade%20to%20say%20LTSC%202025%20you%20might%20find%20yourself%20in%20a%20situation%20where%20your%20dev%20team%20has%20been%20quietly%20developing%20with%20VS%202008%20and%20all%20of%20a%20sudden%20you%20have%20a%20migration%20Project%20on%20the%20scale%20of%20Windows%20XP%20to%20Windows%207.%20Ofcource%20there%20are%20systems%20that%20are%20best%20being%20left%20alone%20from%20the%20fast%20paced%20outside%20World%2C%20but%20they%20are%20few%20and%20far%20apart.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESure%20the%20quality%20in%20Microsoft%20releases%20have%20gone%20down%20since%20they%20fired%20thier%20whole%20QA%20team%2C%20so%20please%20MS%20rethink!%20but%20using%20that%20as%20an%20excuse%20to%20go%20for%20LTSC%2C%20nah.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-307136%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-307136%22%20slang%3D%22en-US%22%3E%3CP%3EThese%20types%20of%20posts%20really%20upset%20me.%20You%20want%20consumers%20and%20IT%20Admins%20to%20stop%20resorting%20to%20an%20OS%20you%20say%20is%20intended%20for%20medical%20devices%20and%20kiosks%3F%20Then%20stop%20consistently%20putting%20out%20versions%20of%20Windows%2010%20that%20break%20NICs%2C%20lose%20data%2C%20reboot%20sans%20warning%2C%20and%20come%20pre-loaded%20with%20adware%20like%20candy%20Crush%2C%20xbox%20apps%2C%20start%20menu%20ads%2C%20lock%20screen%20ads%2C%20and%202%20browsers.%20Can%20I%20ask%20why%20even%20Microsoft%20hasn't%20been%20able%20to%20untangle%20IE%20from%20their%20own%20%22latest%20and%20greatest%22%20rendition%20of%20Windows%2010%3F%20%22WaaS%22%20is%20very%20new%20terminology%20and%20has%20yet%20to%20prove%20sustainable%20as%20a%20model.%20Lest%20we%20forget%20that%20a%20large%20portion%20of%20the%20Win10%20market%20share%20came%20from%20Microsoft%20imaging%20entire%20organizations%20overnight%20with%20clandestine%20Windows%207%20updates%20sometime%20around%20early%202017.%20People%20need%20usable%20images%20for%20VDI%20environments%20with%20video%2Fnetwork%20throughput%20limitations.%20People%20have%20older%20hardware%20that%20needs%20to%20be%20able%20to%20run%20mission%20critical%2C%20legacy%20software.%20Cortana%20and%20the%20App%20Store%20have%20no%20place%20on%20the%20majority%20of%20many%20workshop%20machines.%20Stop%20blaming%20your%20users%20for%20adopting%20something%20that%20actually%20works%20as%20a%20viable%20solution%20with%20STABLE%20updates.%20Stop%20using%20paying%20customers%20as%20beta%20testers.%20Can%20I%20ask%20what%20exactly%20happened%20to%20Patch%20Tuesday%3F%20Because%20for%20the%20last%20year%2C%20at%20least%2C%20updates%20have%20gone%20through%20no%20QA%20team%20and%20come%20down%20the%20channel%20seemingly%20at%20random.%20Occasional%20out%20of%20band%20patches%20are%20fine.%20Building%20the%20plane%20as%20it's%20taking%20off%20and%20then%20yelling%20at%20your%20passengers%20for%20deploying%20their%20parachutes%20when%20you%20hit%20turbulence%20is%20a%20good%20way%20to%20have%20an%20entire%20organization%20shift%20away%20from%20your%20airline.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20will%20point%20other%20readers%20to%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.howtogeek.com%2F395121%2Fwindows-isnt-a-service-its-an-operating-system%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%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.howtogeek.com%2F395121%2Fwindows-isnt-a-service-its-an-operating-system%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-304343%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-304343%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3BThe%20statistics%20provided%20in%20your%20earlier%20comment%20are%20extremely%20misleading%20in%20that%20they%20are%20based%20on%20Windows%20Store%20ads%20which%20would%20not%20include%20LTSB%2FLTSC%20releases%20at%20all.%20They%20would%20also%20not%20include%20organizations%20where%20the%20Windows%20Store%20is%20disabled%20via%20GPO.%20This%20is%20specifically%20mentioned%20in%20the%20article.%20All%20that%20is%20proved%20here%20is%20that%20Microsoft%20Update%20is%20extremely%20aggressive%20in%20Windows%2010.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20for%20LTSC%20vs%20SAC%3A%20I%20would%20much%20rather%20spend%20the%20time%20to%20build%20a%20new%20image%20every%20year%20(or%20so)%20as%20new%20LTSC%20versions%20are%20released%20when%20the%20alternative%20is%20to%20have%20the%20user%20experience%20across%20the%20organization%20be%20turned%20upside%20down%20every%20six%20months%20as%20workflows%20change%20in%20Windows.%20That's%20before%20considering%20the%20major%20stability%20issues%20that%20seem%20to%20be%20plaguing%20the%20SAC%26nbsp%3Bbranch%20on%20a%20regular%26nbsp%3Bbasis.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20our%20organization%2C%20the%20most%20unstable%20machines%20by%20far%20are%20among%20the%20three%20that%20run%20SAC%20vs%20the%20many%20hundreds%20running%20LTSB%20at%20the%20time%20of%20writing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298079%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298079%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20-%20Does%20the%20LTSC%202019%20support%20multi%20app%20kiosk%3F%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fconfiguration%2Flock-down-windows-10-to-specific-apps%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fconfiguration%2Flock-down-windows-10-to-specific-apps%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-294003%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-294003%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20most%20changes%20on%20paper%20sound%20cool%20for%20IT%20enthusiasts%2C%20but%20not%20so%20interesting%20for%20end%20users%2C%20who%20maybe%20just%20work%20with%20a%20few%20spreadsheets%20and%20docs%20and%20not%20so%20into%20technology.%20They%20don't%20care%20about%20timeline%2C%20or%20doing%20screenshots%20with%20new%20app%20or%20connecting%20their%20phones%20to%20PC%2C%20etc.%20Main%20reason%20for%20IT%20to%20install%20it%20is%20to%20keep%20up%20to%20date%2C%20to%20have%20monthly%20cumulative%20updates%20weight%20less%20and%20to%20get%20IT%20updates%20like%20better%20Autopilot%20support%20and%20new%20policies%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293984%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293984%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20John.%3C%2FP%3E%3CP%3EI%20give%20You%20another%20example.%3C%2FP%3E%3CP%3EIn%20our%20industry%20(%20kind%20of%20Software%20development)%20we%20are%20using%20hundreds%20of%20different%20%22bot%22%20machines.%20Automated%20testing%2C%20compiling%2C%20building%2C%20etc%20systems.%20Most%20of%20those%20are%20still%20running%20older%20versions%20of%20Windows.%20Because%20people%20responsible%20for%20those%20processes%20doesnt%20have%26nbsp%3B%20absolute%20certainity%2C%20that%20those%20routines%26nbsp%3B%20work%20fine%20after%20every%20SAC%20upgrade.%20For%20those%20systems%20most%20of%20end-user%20features%20and%20functionalities%20introduced%20with%20new%20W10%20release%20are%20pointless.%20So%2C%20for%20IT%20is%20very%20hard%20to%20sell%20them%20idea-%26nbsp%3B%20to%20screw%20twice%20per%20year%20all%20their%20systems.%20They%20have%20much%20important%20jobs%20to%20perform%20than%20test%20compatibility%20with%20next%20W10%20release.%26nbsp%3B%20We%20are%20trying%20to%20keep%20our%20user%20stations%20on%20more%20recent%20versions%20-%20it%20cost%20us%20lot%20(time%20resources)%20and%26nbsp%3Bend-users%20dont%20understand%20why%20it%20is%20needed.%20they%20dont%20see%20benefit%2C%20or%20it%20is%20tiny%20compared%20to%20introduced%20problems.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293594%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293594%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Oleg%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20discussion%20kickoff.%26nbsp%3B%20First%20to%20your%20question.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20over%20estimated%20LTSC%20usage.%26nbsp%3B%20Let%20me%20use%20a%203rd%20party%20source%2C%20so%20we%20remove%20any%20concern%20I'm%20trying%20to%20cook%20the%20books%20%3A)%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Fmeterpreter.org%2Fdata-shows-that-windows-10-april-update-market-share-soared-to-90%2F%3Fcn-reloaded%3D1%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%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%2Fmeterpreter.org%2Fdata-shows-that-windows-10-april-update-market-share-soared-to-90%2F%3Fcn-reloaded%3D1%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%3EAccording%20to%20InfoTech's%20reporting%2C%20LTSC%20is%20at%20MOST%202%25%20of%20all%20devices.%26nbsp%3B%20Other%20then%20servers%20and%20special%20purpose%20devices%2C%20it%20really%20is%20the%20exception%20today%2C%20and%20for%20desktop%20productivity%20usage%2C%26nbsp%3B%20movement%20is%20from%20it%2C%20to%20SAC.%20%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%3EWhat%20is%20the%20LTSC%20end%20user%20missing%3F%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%3EHe%20is%20a%20small%20subset%2C%20organized%20by%20release%2C%20of%20the%20featurs%20and%20functionality%20added%20in%20subsequent%20SAC%20releases.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F61113i08B965A65AAB5BC2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22SAC.JPG%22%20title%3D%22SAC.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EI'm%20glad%20you%20are%20finding%26nbsp%3B%20LTSC%20great%20and%20stable%20for%20you%2C%26nbsp%3B%20I%20agree%20it%20is.%20I%20would%20submit%20for%20your%20consideration%20(%20based%20on%20real%20data%20telemetry%2C%20and%20actual%20innovation%20we%20have%20added%20)%20that%20I%20know%20the%20subsequent%20SAC%20builds%20are%20even%20more%20stable%2C%20better%20performant%2C%20and%20more%20secure.%20We%20will%20continue%20to%20work%20to%20address%20your%20servicing%20concerns%20and%20challenges%2C%20and%20hope%20that%20in%20the%20near%20future%2C%20we%20can%20make%20it%20work%20for%20you.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJohn%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293232%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293232%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20tell%20that%20preferred%20choice%20is%20changing%20in%20the%20industry%3F%20Any%20approximate%20numbers%3F%20Say%20a%20year%20ago%2030%25%20of%20enterprises%20preferred%20LTSC%20and%20today%2025%25%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20love%20to%20stay%20on%20SAC%2C%20but%20with%20limited%20IT%20human%20resources%2C%20budget%20and%20time%20(like%20in%20most%20SMBs)%20it%20is%20too%20burdening%20to%20keep%20up.%20And%20what%20about%20%22stability%22%20flop%20of%201809%3F%20I%20doubt%20any%20serious%20org%20has%20started%20even%20testing%20and%20i%20feel%201903%20will%20be%20released%20just%20after%20most%20update%20to%20the%20latest%20version.%202%20updates%20per%20year%20is%20too%20often%20(i%20know%20i%20can%20skip%2C%20but%20what%20is%20the%20point%20then%20to%20use%20SAC%20anyway).%20We%20don't%20have%20money%20for%20Intune%2C%20SCCM%2C%20Enterprise%20versions.%20Dealing%20with%20feature%20updates%20via%20WSUS%20is%20PITA.%20Btw%2C%20is%20there%20x64%20only%20feature%20update%20for%201809%20in%20WSUS%20finally%3F%20A%20few%20weeks%20ago%20there%20was%20none.%20Why%20advertise%20new%20cool%20feature%20like%202%20times%20smaller%20update%20size%20by%20splitting%20update%20into%20x86%20and%20x64%20and%20only%20providing%20packages%20for%20older%20versions%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20LTSC%20believers%20won't%20disappear%20soon%2C%20as%20many%20may%20prefer%20stability%20(real%20stability)%20over%20theoretical%20improvements%20and%20possible%20problems.%20If%20anything%2C%20they%20numbers%20may%20grow%20after%20the%201809%20blunder.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-677652%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-677652%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20adding%20my%20two%20cents%20here.%20Most%20users%20keep%20their%20devices%20for%20an%20average%20of%205%20years.%20If%20MS%20supported%20each%20Windows%20SAC%20release%20for%20up%20to%205%20years%2C%20it%20would%20be%20so%20much%20easier%20for%20enterprises%20to%20embrace%20SAC%20over%20LTSC.%20That%20would%20mean%20users%20get%20a%20new%20Windows%20version%20every%20time%20they%20change%20their%20PC%20as%20opposed%20to%20disrupting%20them%20every%20year%20or%20so%20at%20the%20risk%20of%20breaking%20their%20applications.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20all%20those%20LTSC%20issues%20raised%20in%20the%20article%2C%20they%20all%20have%20a%20workaround%20or%20alternative%20so%20they%20are%20of%20no%20concern%20and%20I%20can%20safely%20dismiss%20them%20as%20fear-mongering%20designed%20to%20fit%20Microsoft's%20agenda.%20After%20all%2C%20let's%20look%20at%20who%20wrote%20the%20article.%20The%20author%20conveniently%20failed%20to%20even%20take%20a%20peek%20at%20the%20recent%20series%20of%20upgrade%20disasters%20and%20delays%20Microsoft%20is%20facing.%20I%20think%20it%20is%20evident%20Microsoft%20can't%20keep%20up%20with%20their%20own%20agenda%2C%20which%20has%20hurt%20their%20credibility.%20If%20they%20are%20to%20be%20successful%20at%20repairing%20the%20damage%2C%20first%20they%20have%20to%20earn%20our%20trust%20before%20we%20can%20take%20their%20agenda%20seriously%20by%20releasing%20stable%20and%20trustworthy%20upgrades%20that%20are%20consistently%20on%20time.%20Constant%20delays%20is%20a%20clear%20sign%20of%20trouble.%20If%20MS%20can't%20keep%20up%20with%20their%20own%20pace%2C%20what%20makes%20anyone%20think%20that%20the%20average%20enterprise%20will%20be%20able%20to%20do%20the%20same%3F%20We%20just%20don't%20have%20the%20resources%20to%20go%20around%20every%206%20months%20upgrading%20machines.%20If%20they%20slowed%20down%20the%20release%20pace%20to%20maybe%20once%20a%20year%2C%20and%20support%20those%20releases%20for%20up%20to%205%20years%2C%20I%20believe%20Microsoft%20might%20be%20able%20to%20keep%20up%20with%20the%20pace%2C%20they%20won't%20stumble%20as%20much%2C%20make%20it%20much%20easier%20for%20enterprises%2C%20significantly%20reduce%20the%20push%20back%2C%20and%20have%20a%20much%20more%20successful%20Win%2010%20upgrade%20path.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-678486%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-678486%22%20slang%3D%22en-US%22%3E%3CP%3EMS%20is%20surprisingly%20quiet%20about%20the%2019H2%20update%20and%20there%20are%20rumors%20it%20might%20be%20very%20minor%20stability%20update%20instead%20of%20a%20regular%20feature%20update.%20Although%20i%20would%20just%20scrap%20it%20and%20go%20the%201%20update%20per%20year%20route.%205%20years%20though%3F%20Nah%2C%20that's%20too%20long.%20Especially%20with%20laptops.%20They%20get%20beaten%20up%20badly%20(if%20used%20as%20laptops%20and%20carried%20around%20a%20lot).%20And%20they%20get%20morally%20old.%203%20years%20seems%20like%20a%20more%20reasonable%20age%20to%20change.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293181%22%20slang%3D%22en-US%22%3ELTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293181%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EUpdate%207%2F15%2F2019%3C%2FSTRONG%3E%3A%26nbsp%3B%20The%20content%20in%20this%20post%20applies%20to%20PC%20and%20laptop%20type%20devices%20converted%20to%20Windows%2010%20Enterprise%20LTSC%2C%20and%20not%20devices%20purchased%20with%20Windows%2010%20IoT%20Enterprise%20pre-installed.%20Examples%20of%20the%20latter%20include%20kiosks%2C%20medical%20equipment%2C%20and%20digital%20signs%2C%20i.e.%20use%20cases%20where%20devices%20are%20commonly%20treated%20as%20a%20whole%20system%20and%20are%2C%20therefore%2C%20%E2%80%9Cupgraded%E2%80%9D%20by%20building%20and%20validating%20a%20new%20system%2C%20turning%20off%20the%20old%20device%2C%20and%20replacing%20it%20with%20a%20new%2C%20certified%20device.%20Organizations%20that%20leverage%20this%20approach%20are%20seeking%20the%20manageability%20and%20security%20of%20Windows%2010%20while%20staying%20on%20the%20same%20operating%20system%20version%20for%20the%20life%20of%20the%20device.%3C%2FP%3E%0A%3CHR%20%2F%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EIf%20you%20ask%20someone%20from%20Microsoft%2C%20or%20read%20industry%20guidance%2C%20about%20the%20best%20strategy%20for%20managing%20Windows%2010%20updates%2C%20the%20overarching%20recommendation%20is%20to%20use%20the%20Semi-Annual%20Channel%20(SAC)%20as%20the%20default%20servicing%20channel%20for%20Windows%2010%20devices.%20With%20the%20Semi-Annual%20Channel%2C%20devices%20receive%20two%20feature%20updates%20per%20year%2C%20and%20benefit%20from%20the%20best%20performance%2C%20user%20experience%2C%20security%2C%20and%20stability.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EThe%20Long-Term%20Servicing%20Channel%20(LTSC)%20is%20designed%20for%20Windows%2010%20devices%20and%20use%20cases%20where%20the%20key%20requirement%20is%20that%20functionality%20and%20features%20don%E2%80%99t%20change%20over%20time.%20Examples%20include%20medical%20systems%20(such%20as%20those%20used%20for%20MRI%20and%20CAT%20scans)%2C%20industrial%20process%20controllers%2C%20and%20air%20traffic%20control%20devices.%20These%20devices%20share%20characteristics%20of%20embedded%20systems%3A%20they%20are%20typically%20designed%20for%20a%20specific%20purpose%20and%20are%20developed%2C%20tested%2C%20and%20certified%20before%20use.%20They%20are%20treated%20as%20a%20whole%20system%20and%20are%2C%20therefore%2C%20commonly%20%E2%80%9Cupgraded%E2%80%9D%20by%20building%20and%20validating%20a%20new%20system%2C%20turning%20off%20the%20old%20device%2C%20and%20replacing%20it%20with%20the%20new%2C%20certified%20device.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWe%20designed%20the%20LTSC%20with%20these%20types%20of%20use%20cases%20in%20mind%2C%20offering%20the%20promise%20that%20we%20will%20support%20each%20LTSC%20release%20for%2010%20years--and%20that%20features%2C%20and%20functionality%20will%20not%20change%20over%20the%20course%20of%20that%2010-year%20lifecycle.%3C%2FP%3E%0A%3CH2%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2018px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%20id%3D%22toc-hId-1701929792%22%3EDifferences%20between%20the%20Semi-Annual%20Channel%20and%20LTSC%3C%2FH2%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EAs%20I%20noted%20above%2C%20Windows%2010%20devices%20in%20the%20Semi-Annual%20Channel%20receive%20twice-yearly%20feature%20updates%2C%20once%20in%20the%20spring%20and%20once%20in%20the%20fall.%20These%20updates%20contain%20new%20features%2C%20services%2C%20and%20other%20major%20changes.%20Security%20updates%2C%20optimizations%2C%20and%20other%20minor%20updates%20or%20patches%20are%20released%20every%20month%20thereafter.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3ETo%20deliver%20on%20the%20commitment%20of%20no%20changes%20to%20features%20or%20functionality%2C%20a%20Windows%2010%20LTSC%20release%20does%20not%20contain%20any%20of%20the%20components%20of%20Windows%2010%20that%20may%20change%20over%20the%20life%20of%20the%20release.%20These%20components%20include%20Microsoft%20Edge%20(as%20a%20modern%20browser%2C%20it%20is%20constantly%20evolving%20to%20support%20the%20current%20modern%20browser%20web%20standards)%20as%20well%20as%20components%2Fapplications%20regularly%20updated%20via%20the%20Microsoft%20Store%2C%20such%20as%20Camera%2C%20Cortana%2C%20OneNote%2C%20and%20other%20modern%20apps%20that%20continue%20to%20advance%20with%20innovative%20improvements.%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EInternet%20Explorer%20is%20included%20in%20Windows%2010%20LTSC%20releases%20as%20its%20feature%20set%20is%20not%20changing%2C%20even%20though%20it%20will%20continue%20to%20get%20security%20fixes%20for%20the%20life%20of%20a%20Windows%2010%20LTSC%20release.%3C%2FP%3E%0A%3CH2%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2018px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%20id%3D%22toc-hId--850227169%22%3EThe%20LTSC%20cadence%3C%2FH2%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWe%20create%20a%20new%20LTSC%20release%20approximately%20every%20three%20years%2C%20and%20each%20release%20contains%20all%20the%20new%20capabilities%20and%20support%20included%20in%20the%20Windows%2010%20features%20updates%20that%20have%20been%20released%20since%20the%20previous%20LTSC%20release.%20Unlike%20the%20year-and-month%20terminology%20employed%20to%20describe%20Windows%2010%20features%20updates%20(e.g.%201703%20or%201809)%2C%20LTSC%20releases%20are%20named%20with%20a%20specific%20year%2C%20such%20as%20Windows%2010%20Enterprise%20LTSC%202016%20or%20Windows%2010%20Enterprise%20LTSC%202019%2C%20and%20they%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-IT-Pro-Blog%2FChanges-to-Office-and-Windows-servicing-and-support%2Fba-p%2F151509%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ealign%20to%20perpetual%20Office%20releases%3C%2FA%3E%20such%20as%20Office%202019.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EEach%20LTSC%20release%20receives%2010%20years%20of%20servicing%20and%20support%3CA%20href%3D%22%23_edn1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20name%3D%22_ednref1%22%3E%3CSPAN%3E%5Bi%5D%3C%2FSPAN%3E%3C%2FA%3E.%20During%20the%20life%20of%20a%20LTSC%20release%2C%20you%20can%20upgrade%20your%20devices%20to%20the%20next%20or%20latest%20LTSC%20release%20free%20of%20charge%20using%20an%20in-place%20upgrade%2C%20or%20to%20any%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fitpro%2Fwindows-10%2Frelease-information%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ecurrently%20supported%20release%20of%20Windows%2010%3C%2FA%3E.%20Because%20the%20LTSC%20is%20technically%20its%20own%20SKU%2C%20an%20upgrade%20is%20required%20from%20Windows%2010%20Enterprise%20LTSC%20to%20Windows%2010%20Enterprise%2C%20which%20supports%20the%20Semi-Annual%20Channel.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EAs%20with%20the%20Semi-Annual%20Channel%2C%20LTSC%20devices%20receive%20regular%20quality%20and%20security%20updates%20to%20ensure%20that%20device%20security%20stays%20up%20to%20date.%20While%20quality%20updates%20are%20available%20for%20Windows%2010%20Enterprise%20LTSC%2C%20you%20can%20choose%20to%20defer%20them%20using%20tools%20such%20as%20Windows%20Update%20for%20Business%20or%20System%20Center%20Configuration%20Manager.%3C%2FP%3E%0A%3CH2%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2018px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%20id%3D%22toc-hId-892583166%22%3EMaking%20a%20fully%20informed%20choice%20about%20the%20LTSC%3C%2FH2%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EBefore%20its%20release%20and%20throughout%20the%20first%20year%20of%20Windows%2010%2C%20many%20predicted%20that%20LTSC%20would%20be%20the%20preferred%20servicing%20channel%20for%20enterprise%20customers.%20This%20has%20turned%20out%20not%20to%20be%20the%20case%2C%20and%20the%20SAC%20is%20the%20predominant%20choice%20for%20enterprises%20today.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EI%E2%80%99m%20currently%20working%20with%20a%20few%20early%20LTSC%20adopters%20who%20are%20now%20looking%20to%20unwind%20their%20LTSC%20deployments%20and%20shift%20to%20SAC.%20There%20are%20several%20reasons%20why%20using%20the%20LTSC%20can%20turn%20out%20to%20be%20the%20wrong%20fit%20for%20the%20Windows%2010%20devices%20in%20an%20organization.%20For%20example%2C%20one%20organization%20deployed%20LTSC%20to%20bring%20forward%20the%20same%20IT%20rules%20and%20image%20creation%20and%20management%20processes%20they%20had%20used%20since%20Windows%20XP%2C%20in%20this%20case%20to%20new%20Surface%20devices.%20You%20can%20imagine%20the%20reaction%20of%20their%20end%20users%20when%20they%20excitedly%20opened%20their%20new%20Surface%20devices%2C%20only%20to%20find%20that%20features%20such%20as%20Camera%2C%20Ink%2C%20and%20Pen%20did%20not%20work%E2%80%94and%20that%20they%20were%20missing%20many%20of%20the%20modern%2C%20touch%20friendly%20version%20of%20apps%E2%80%94because%20the%20devices%20had%20been%20%E2%80%9Crepaved%E2%80%9D%20with%20a%20Windows%2010%20Enterprise%20LTSC%20release.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EAnother%20reason%20some%20organizations%20chose%20to%20adopt%20the%20LTSC%20centered%20around%20application%20compatibility.%20In%20talking%20with%20some%20of%20these%20organizations%3B%20however%2C%20initial%20concerns%20about%20application%20compatibility%20from%20release%20to%20release%20in%20their%20environment%20have%20proved%20to%20be%20a%20non-issue.%3C%2FP%3E%0A%3CH3%20style%3D%22margin-top%3A%2024px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2017px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%20id%3D%22toc-hId--1856087300%22%3EConsiderations%3C%2FH3%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EAll%20too%20often%2C%20I%20have%20seen%20strategic%20decisions%20about%20Windows%2010%20servicing%20options%20and%20the%20use%20of%20the%20Long-Term%20Servicing%20Channel%20driven%20by%20the%20wrong%20criteria%3B%20for%20example%2C%20IT%20professional%20familiarity%20prevailing%20over%20end%20user%20value%20and%20impact.%20The%20LTSC%20is%20designed%20for%20devices%20and%20use%20cases%20where%20features%20and%20functionality%20will%20not%20change.%20It%20provides%2010%20years%20of%20security%20servicing%20to%20a%20static%20Windows%2010%20feature%20set.%20If%20you%20are%20considering%20the%20LTSC%20for%20devices%20in%20your%20organization%2C%20please%20consider%20the%20following%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%20margin-top%3A%2020px%3B%22%3E%3CU%3ESilicon%20support%3C%2FU%3E%3A%20Windows%2010%20Enterprise%20LTSC%20will%20support%20the%20currently%20released%20processors%20and%20chipsets%20at%20the%20time%20of%20release%20of%20the%20LTSC.%20When%20choosing%20to%20utilize%20the%20LTSC%2C%20you%20must%20factor%20hardware%20into%20your%20decision%2C%20making%20sure%20you%20have%20a%20long-term%20supply%20of%20devices%20and%20service%20components%20for%20the%20life%20of%20your%20expected%20usage%20of%20the%20device.%20If%20the%20hardware%20your%20device%20is%20using%20needs%20to%20be%20replaced%20in%20five%20years%2C%20do%20you%20have%20a%20replacement%20supply%20to%20support%20the%20version%20you%20are%20running%3F%20You%20also%20want%20to%20be%20sure%20you%20have%20a%20hardware%20solution%20that%20will%20provide%20you%20with%20extended%20driver%2Ffirmware%20support%20to%20match%20your%20expected%20lifecycle%20use%20of%20the%20LTSC%20for%20that%20device.%20(See%20the%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F18581%2Flifecycle-faq-windows-products%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ELifecycle%20FAQ%3C%2FA%3E%20to%20learn%20more%20about%20the%20Windows%20Silicon%20Support%20Policy.)%3C%2FLI%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%22%3E%3CU%3ENew%20peripheral%20support%3C%2FU%3E%3A%20Because%20the%20API%20and%20driver%20support%20models%20are%20not%20changing%2C%20the%20LTSC%20release%20you%20deploy%20may%20not%20support%20new%20hardware%20or%20peripherals%20that%20you%20need%20to%20use%20in%20your%20organization.%3C%2FLI%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%22%3E%3CU%3EApplication%20support%3C%2FU%3E%3A%20With%20each%20Semi-Annual%20Channel%20release%20following%20an%20LTSC%20release%2C%20there%20is%20a%20growing%20gap%20in%20APIs%20and%20functionality%20between%20the%20current%20Windows%20API%20in%20use%20by%20most%20all%20devices%2C%20and%20previous%20LTSC%20releases.%20Many%20ISVs%20do%20not%20support%20LTSC%20editions%20for%20their%20applications%2C%20as%20they%20want%20their%20applications%20to%20use%20the%20latest%20innovation%20and%20capabilities%20to%20give%20users%20the%20best%20experience.%20This%20is%20the%20case%20with%20Office%20ProPlus%2C%20which%20does%20not%20support%20Windows%2010%20Enterprise%20LTSC%20releases%20as%20it%20relies%20on%20Windows%2010%20feature%20updates%20and%20the%20Semi-Annual%20Channel%20to%20deliver%20the%20best%20user%20experience%20with%20the%20latest%20capabilities.%20(If%20you%20were%20using%20Windows%2010%20Enterprise%20LTSC%202019%2C%20you%20would%2C%20therefore%2C%20need%20to%20use%20Office%202019.)%3C%2FLI%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%22%3E%3CU%3EBest%20security%3C%2FU%3E%3A%20Windows%2010%2C%20with%20the%20latest%20feature%20update%20installed%2C%20is%20always%20the%20most%20secure%20release%20of%20Windows%2010%2C%20offering%20the%20latest%20security%20capabilities%20and%20functionality.%3C%2FLI%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%22%3E%3CU%3EBest%20stability%3C%2FU%3E%3A%20Windows%2010%2C%20with%20the%20latest%20feature%20update%20installed%2C%20has%20the%20latest%20performance%20and%20stability%20improvements.%3C%2FLI%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%22%3E%3CU%3EGreatest%20hardware%20choice%3C%2FU%3E%3A%20New%20devices%20target%20and%20ship%20with%20the%20latest%20Windows%2010%20release%20to%20light%20up%20new%20hardware%20capabilities%20and%20improvements.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH2%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2018px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%20id%3D%22toc-hId-83236540%22%3ESummary%3C%2FH2%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EThe%20Long-Term%20Servicing%20Channel%20a%20tool%20designed%20for%20a%20specific%20job.%20When%20used%20for%20the%20right%20job%2C%20it%E2%80%99s%20a%20great%20solution%2C%20but%20when%20misaligned%2C%20it%20can%20be%20like%20trying%20to%20drive%20a%20screw%20with%20a%20hammer.%20It%E2%80%99s%2C%20at%20best%2C%20unsatisfying%2C%20and%20likely%20problematic%20at%20some%20point.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EIf%20you%20understand%20the%20considerations%20listed%20above%2C%20have%20secured%20hardware%20and%20support%20to%20align%20with%20the%20intended%20duration%20of%20usage%2C%20and%20have%20secured%20support%20for%20your%20applications%2C%20the%20LTSC%20can%20provide%20your%20organization%20with%20years%20of%20secure%2C%20static%20operation%2C%20with%20full%20servicing%20and%20support%20for%20its%2010-year%20lifespan.%20For%20most%20use%20cases%3B%20however%2C%20I%20recommend%20the%20Semi-Annual%20Channel%20as%20the%20better%20option%20for%20security%2C%20stability%2C%20and%20hardware%2Fapplication%20capabilities%2C%20and%20the%20overall%20experience%20of%20your%20end%20users.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3ETo%20learn%20more%2C%20check%20out%20our%20on%20demand%20session%20from%20Microsoft%20Ignite%20on%20%3CA%20href%3D%22https%3A%2F%2Fmyignite.techcommunity.microsoft.com%2Fsessions%2F64512%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EThe%20pros%20and%20cons%20of%20LTSC%20in%20the%20enterprise%3C%2FA%3E.%3C%2FP%3E%0A%3CHR%20%2F%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-size%3A%2014px%3B%20font-weight%3A%20400%3B%20color%3A%20%23333333%3B%22%3E%3CA%20href%3D%22%23_ednref1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20name%3D%22_edn1%22%3E%3CSPAN%3E%5Bi%5D%3C%2FSPAN%3E%3C%2FA%3E%20%3CEM%3ETen%20years%20of%20support%20includes%20a%20minimum%20of%20five%20years%20Mainstream%20Support%20(during%20which%20both%20security%20and%20non-security%20updates%20are%20provided)%20and%20a%20minimum%20of%20five%20years%20Extended%20Support%20(during%20which%20only%20security%20updates%20are%20provided).%20Please%20see%20the%20%3C%2FEM%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F14085%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CEM%3EFixed%20Lifecycle%20Policy%20for%20Microsoft%20Business%2C%20Developer%20and%20Desktop%20Operating%20Systems%3C%2FEM%3E%3C%2FA%3E%3CEM%3E%20for%20more%20detail.%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-293181%22%20slang%3D%22en-US%22%3E%3CP%3EExplore%20use%20cases%20for%20the%20Long-Term%20Servicing%20Channel%20(LTSC)%20and%20how%20it%20compares%20to%20other%20servicing%20options.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F61051i15715EB1A6ACDC28%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22medical.png%22%20title%3D%22medical.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-293181%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EServicing%20and%20updates%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-790765%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-790765%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20use%20the%20LTSC%20version.%20I%20originally%20went%20the%20route%20of%201803%20Enterprise%20and%20had%20so%20many%20problems%3A%3C%2FP%3E%3CP%3E-%20Removal%20of%20the%20bloatware%20is%20not%20clean%2C%20on%20new%20sysprep'd%20computers%20there%20are%20always%20errors%20regarding%20apps%20that%20have%20been%20removed%20in%20the%20Application%20log.%3C%2FP%3E%3CP%3E-%20Inconsistent%20application%20performance%3C%2FP%3E%3CP%3E-%20Using%20GPO's%20to%20disable%20the%20Store%2C%20Hello%2C%20Cortana%20doesn't%20do%20this%20cleanly%2C%20Application%20errors%20are%20consistently%20reported.%20Why%2C%20if%20they%20are%20turned%20OFF.%3C%2FP%3E%3CP%3E-%20With%20patching%20and%20updates%2C%20some%20of%20the%20apps%20%22return%22%20which%20is%20unacceptable.%20(ie%20OneDrive)%3C%2FP%3E%3CP%3E-%20Our%20computers%20are%20for%20%22work%22%20not%20home%2C%20shopping%20apps%20are%20inappropriate.%3C%2FP%3E%3CP%3E-%20We%20don't%20want%20%22Advertisements%22%20on%20work%20computers%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20want%20stability%2C%20clean%20and%20lean%20OS%20that%20is%20quick%20and%20for%20work.%20The%20adoption%20of%20new%20%22Features%22%20should%20always%20be%20an%20individual%20companies%20decision%2C%20not%20Microsofts.%20All%20non-required%20features%20are%20just%20applications%20that%20bloat%20the%20OS%20and%20increase%20management.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20don't%20have%20the%20staff%20to%20deal%20with%2C%206monthly%20Feature%20updates%2C%20which%20technically%20are%20%22inplace-upgrades%22%20and%20all%20their%20consistencies.%3C%2FP%3E%3CP%3EI%20think%20the%203yr%20rotation%20was%20good%2C%202yrs%20of%20stability.%20Then%20the%203rd%20year%20was%20dev%2Ftest%2Fimplementation%2Ftidy%20up%20for%20the%20next%20version%2C%20if%20it%20was%20stable.%20We%20skipped%20all%20of%20Windows%208.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-862384%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-862384%22%20slang%3D%22en-US%22%3E%3CP%3EI%E2%80%99d%20like%20to%20know%20how%20are%20we%20to%20keep%20up%20with%20these%20updates.%20By%20the%20time%20I%E2%80%99m%20done%20getting%201903%20out%2C%201903%20will%20be%20end%20of%20support%20and%20I%E2%80%99ll%20have%20to%20start%20rolling%20out%20whatever%20new%20build%20is%20current%20then.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20happened%20to%2010%20year%20long%20OS%E2%80%99s%20like%20XP%20and%207%3F%20%26nbsp%3BNow%20I%20have%20to%20upgrade%20the%20OS%20every%202%20years%20just%20to%20keep%20security%20updates%20coming%20down%20the%20pipe%3F%20%26nbsp%3BWe%20just%20did%20an%20internal%20NESSUS%20vulnerability%20scan%20and%2018%20machines%20on%201703%20and%20earlier%20came%20up%20on%20the%20report%20for%20being%20end%20of%20life.%20%26nbsp%3BI%E2%80%99m%20almost%20done%20getting%20all%20the%20Windows%207%20machines%20up%20to%20Windows%2010%2C%20but%20even%20if%20these%20machines%20have%20a%205%20year%20lifespan%2C%20the%20hardware%20will%20outlive%20the%20OS!%20%26nbsp%3BIt%20used%20to%20be%20we%20bought%20a%20generation%20of%20computer%20preloaded%20with%20an%20OS%20(like%20Win%207)%20then%205%20or%206%20years%20later%20those%20computers%20would%20be%20refreshed%20with%20a%20newer%20model%20and%20a%20newer%20OS%20(like%20Win%2010).%20%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EIf%20you%20want%20to%20do%20feature%20updates%20fine%2C%20but%20keep%20those%20security%20updates%20coming%20down%20the%20wire.%20%26nbsp%3BI%20can%E2%80%99t%20tell%20you%20how%20many%201607%20builds%20we%20have%20that%20just%20will%20NOT%20update%20at%20all%20to%201803%2C1809%20or%201903.%20%26nbsp%3B%E2%80%9CSomething%20went%20wrong%E2%80%9D%20is%20not%20helpful.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-862443%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-862443%22%20slang%3D%22en-US%22%3E%3CP%3EKeith%2C%20it%20might%20help%20first%20updating%20to%20older%20build.%20Some%20PCs%20here%20were%20failing%20to%20upgrade%20from%201709%20to%201809.%20Yeah%2C%20it%20was%20giving%20a%20confusing%20error%20that%20%22some%20driver%20is%20incompatible%22.%20No%20exact%20name%2C%20error%2C%20nothing.%20Just%20a%20button%20to%20proceed%20anyway.%20If%20i%20proceed%2C%20it%20works%20ok%20after%20the%20update.%20But%20this%20requires%20manual%20intervention.%20Surprisingly%20this%20works%2C%20if%20you%20first%20update%20to%201803%20and%20then%20to%201809.%20So%20for%20failing%20machines%20i'm%20using%20this%20approach.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBtw%2C%20we%20also%20have%2015-20%201703%20machines%20and%20it%20seems%20they%20are%20not%20going%20to%20be%20updated%20soon%20as%20application%20is%20not%20compatible%20with%20newer%20versions%20of%20Windows%20and%20there%20are%20also%20some%20political%20decisions%20to%20be%20made%20to%20move%20on.%201703%20was%20released%20in%202017%20and%20is%20expiring%20sooner%20than%20Windows%207.%201709%20released%20in%20the%20same%20year%20had%20some%20drastic%20change%20breaking%20the%20application.%20I%20know%20that%20MS%20now%20has%20so%20many%20versions%20on%20their%20hands%20to%20support%20all%20of%20them%20for%20at%20least%205%20years.%20But%20hey%2C%20there%20is%20the%20LTSC%20version%20to%20avoid%20this%20problems%2C%20no%3F%20%2Fs%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-864027%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-864027%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F107589%22%20target%3D%22_blank%22%3E%40Keith%20Sauer%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EHi%20Keith.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EHappy%20to%20help%2C%20I%20hear%20frustration%20in%20your%20feedback%2C%20but%20missing%20a%20lot%20of%20details%20that%20I%20might%20help%20with.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ESome%20initial%26nbsp%3Bthoughts%2C%20feel%20free%20to%20engage%20with%20specifics%26nbsp%3Bif%20you%20would%26nbsp%3Blike%20help.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E1)%20Once%20we%20work%20through%20your%20issues%2C%20I'm%20confident%20we%20will%20get%20you%20to%20were%20the%20vast%20majority%20of%20devices%20are%20today%2C%20installing%20updates%20and%20getting%20the%20security%2C%20end%20user%20functionality%2C%20and%20quality%20improvements%20that%20come%20with%20them.%26nbsp%3B%20There%20are%20literally%20millions%20of%20devices%20that%20do%20this%20every%20day%2C%20consumer%2C%20slam%20business%20and%20large%20enterprise.%26nbsp%3B%20%26nbsp%3BYou%20did%20not%20indicate%20with%20SKU%20you%20are%20using%2C%20but%20I'll%20assume%20pro%20is%20you%20are%20focused%20on%20the%2018%20month%20security%20servicing%20for%20each%20release.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E2)%20You%20forecast%20that%20it%20will%20take%20you%20more%20than%2018%20months%20to%20roll%20out%201903%20to%20your%20organization%2C%20but%20no%20details%20on%20what%20is%20limiting%20that%20velocity.%26nbsp%3B%20I%20work%20with%20many%20enterprise%20customers%20(%20other%20than%20Microsoft%20)%20who%26nbsp%3B%20update%201000s%26nbsp%3B%20of%20devices%20weekly%2C%20some%20even%20more.%20What%20are%20the%20limits%20that%20you%20running%20into%20and%20effecting%20that%20velocity%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E3)%20Just%20to%20make%20sure%20%2C%20though%20I%20think%20you%20know%20this%2C%26nbsp%3B%20for%20Pro%20SKU%2C%20we%20provide%26nbsp%3Bsecurity%26nbsp%3Bupdates%20for%2018%20months.%20So%20if%20you%20choose%20%2C%20you%20can%20update%20devices%20as%20slowly%20as%20%26lt%3B1%20%2F%20year%2C%20and%20still%20stay%20security%20patch%20current%2C%20you%20do%20not%20have%20to%20update%202%2Fyear.%26nbsp%3B%20The%20customer%20trend%20I%20do%20see%20is%20that%20once%20you%20get%20process%20in%20place%20to%20update%20once%20every%2012%20months%2C%20then%20updating%20more%20frequently%2C%20if%20you%20choose%20is%20incremental.%20Most%20of%20the%20change%20management%20is%20completed%20in%20getting%20to%20update%20more%20frequent%20than%20every%203-4%20years%2C%20ie%20once%20per%20year.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E4)%20Do%20you%20have%20specific%20issues%20that%20have%20prevented%20you%20from%20updating%26nbsp%3Bthose%20devices%26nbsp%3Bon%201703%3F%20How%20do%20you%20manage%20updates%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E5)%20We%20have%20updated%20millions%20of%20older%20machines%26nbsp%3Bthat%20started%20life%20on%20Windows%207%20%2C%20and%20now%20are%20now%20extending%26nbsp%3Btheir%26nbsp%3Buseful%26nbsp%3Blife%20with%20improved%20security%20and%20new%20functionality%20with%20Windows%2010%2C%20and%20the%20Windows%2010%20feature%20updates.%26nbsp%3B%20Windows%2010%20will%20certainly%20outlive%20the%20HW%2C%20but%20while%20it%20does%20so%2C%20it%20is%20extending%20the%20life%20of%20that%20HW.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E6)%201607%20devices%20that%20wont%20update.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ETell%20me%20more%3F%26nbsp%3B%20Have%20you%20check%20free%20diskspace%3F%26nbsp%3B%20This%20is%20one%20of%20the%20most%20common%20sources%20of%20update%20failures%2C%20lacking%20free%20space%20to%20download%20and%20install%20the%20updates.%26nbsp%3B%20%26nbsp%3BDo%20you%20have%203rd%20party%20encryption%20and%20security%20products%20that%20might%20be%20conflicting%3F%20Many%20then%2C%20fewer%20today%20still%2C%20required%20you%20to%20first%20uninstall%2C%20update%20the%203rd%20party%20tools%20before%20the%20update%2C%20though%20I%20would%20expect%20you%20would%20have%20worked%20through%20this%20with%20other%20devices%20that%20did%20update%2C%20so%20check%20disk%20space.%20Have%20you%20used%20the%20Setup%20Diag%20tool%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJohn%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%3CLINGO-SUB%20id%3D%22lingo-sub-864033%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-864033%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%20my%20old%20friend.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETell%20me%20more%20about%20the%20%22drastic%20change%22%20breaking%20your%20application.%20If%20this%20is%20the%20case%2C%20by%20all%20means%2C%20take%20advantage%20of%20our%20App%20Assure%20program%2C%20no%20cost%20to%20you%2C%20and%20we%20will%20correct%20or%20help%20re-mediate%20the%20issue%20for%20you.%20App%20compat%20%2C%20now%20with%20enterprise%2C%20LOB%20data%20included%20has%20been%20greater%20than%2099%25%2C%20we%20have%20had%20to%20make%20very%20few%20code%20changes%2Ffixes%2C%26nbsp%3B%20but%20if%20we%20break%20something%2C%20we%20want%20to%20correct%20it.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJOhn%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%3CLINGO-SUB%20id%3D%22lingo-sub-864069%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-864069%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20not%20sure%20if%20i%20can%20disclose%20such%20information%20(even%20the%20name%20in-house%20app).%20What%20i%20meant%2C%20that%20one%20might%20assume%20that%20going%20from%20March%20version%20to%20September%20one%20can%20expect%20it%20to%20be%20mostly%20compatible.%20This%20seems%20like%201909%20might%20be%20such%20example.%20Although%20looking%20at%20Insider%20builds%20there%20are%20still%20a%20bunch%20of%20changes%2C%20not%20just%20small%20fixes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-864089%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-864089%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20be%20very%20clear.%20you%20should%20expect%20it%20to%20be%20COMPLETELY%20compatible%20release%20to%20release%2C%20not%20just%20mostly%2C%20for%20those%20apps%20that%20are%20using%20public%20APIs.%26nbsp%3B%20If%20you%20have%20an%20app%20that%20is%20using%20undocumented%20calls%2C%20or%20other%20non-supported%20approaches%2C%26nbsp%3B%20no-promises.%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20its%20not%2C%20use%20App%20assure%20program%20so%20we%20can%20fix%20it%20for%20you%20and%20others.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-864097%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-864097%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20often%20the%20little%20things%20that%20are%20annoying.%26nbsp%3B%20I%20don't%20have%20a%20large%20deployment%20but%20every%20release%20there%20is%20something%20that%20takes%20time%20to%20fix%20and%20track%20down.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1903%20was%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faccountants-community.intuit.com%2Farticles%2F1860059-pdf-and-component-repair-tools-for-lacerte-and-proseries%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faccountants-community.intuit.com%2Farticles%2F1860059-pdf-and-component-repair-tools-for-lacerte-and-proseries%3C%2FA%3E%26nbsp%3BI%20had%20to%20repair%20the%20pdf%20printer%20for%20a%20LOB%20app.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt's%20typically%20something%20relating%20to%20printing%2C%20one%20time%20it%20was%20an%20Outlook%20app%20that%20stopped%20working%20and%20I%20had%20to%20repair%20it.%26nbsp%3B%20At%20home%20I've%20lost%20my%20hdmi%20display%20to%20my%20Lenovo%20docking%20station%20(and%20this%20isn't%20a%20cheap%20laptop%20either).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20I%20had%20thousands%20of%20desktops%20this%20wouldn't%20scale.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20personally%20only%20do%20a%20feature%20release%20a%20year%20for%20this%20reason.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-918750%22%20slang%3D%22en-US%22%3ERe%3A%20LTSC%3A%20What%20is%20it%2C%20and%20when%20should%20it%20be%20used%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-918750%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20be%20honest%2C%20I%20really%20do%20not%20see%20how%20you%20have%20such%20a%20big%20issue%20keeping%20up%20to%20date%20on%20Windows%2010.%20First%20off%2C%20LTSC%20is%20a%20bad%20choice%20for%20close%20to%20every%20user%20in%20any%20case%2C%20to%20many%20potential%20pitfalls%20and%20limitations.%20It's%20an%20embedded%2FIoT%20solution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EManaging%20computers%20without%20management%20tools%20is%20not%20easy%2C%20but%20if%20your%20are%20serious%20you%20should%20also%20be%20serious%20managing%20your%20computers%2C%20making%20sure%20they%20are%20up%20to%20date%20and%20compliant.%20With%20an%20increasing%20degree%20of%20travel%20and%20out%20of%20office%20usage%2C%20as%20well%20as%20interaction%20with%20external%20systems%20and%20users%2C%20firewalls%20are%20not%20the%20most%20important%20point%20of%20security%20any%20more%2C%20the%20endpoint%20is.%20Not%20having%20absolute%20control%20of%20the%20endpoint%20can%20turn%20out%20more%20expensive%20than%20you%20might%20think.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20using%20a%20combination%20of%20SCCM%20and%20Intune%20managing%20endpoints%2C%20and%20as%20a%20single%20admin%20I%20manage%20thousands%20of%20devices%2C%20Windows%2C%20iOS%20and%20Android%2C%20in%20a%20more%20diverse%2C%20both%20geographically%20and%20methodically%2C%20environment%20than%20most%20other%20businesses.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20for%20the%201806%20issues%2C%20well%2C%20I%20did%20not%20experience%20any.%20Nor%20did%20I%20have%20any%20issues%20with%20any%20other%20release%20either.%20My%20impression%20is%2C%20most%20people%20did%20not%20have%20any%20issues%2C%20but%20a%20small%20percentage%20of%20close%20to%20a%20billion%20devices%20is%20still%20many%20systems%20and%20users.%20When%20the%20new%20release%20is%20out%2C%20I%20wait%20a%20few%20weeks%20before%20I%20update%20a%20small%20set%20of%20test%20computers%20in%20my%20office.%20I%20do%20some%20testing%20trying%20to%20provoke%20some%20errors%2C%20while%20also%20looking%20for%20people%20having%20issues%20online%2C%20trying%20to%20identify%20HW%20and%20SW%20setups%20common%20for%20our%20environment.%20I%20then%20deploy%20the%20update%20to%20a%20set%20of%20chosen%20early%20adopters%2Fpower%20users%2C%20yeah%2C%20they%20know%20they%20are%20guinea%20pigs%2C%20and%20let%20them%20run%20the%20new%20the%20update%20for%20a%20while.%20I%20then%20deploy%20for%20the%20entire%20organisation.%20All%20data%20is%20stored%20off%20device%2C%20and%20a%20full%20device%20rollback%20takes%20about%20one%20hour%2C%20should%20something%20go%20bad.%20So%20far%20I've%20had%20issues%20with%20one%20upgrade%20on%20one%20computer%2C%20out%20of%20several%20thousands.%20And%2C%20after%20redeploying%20the%20OS%2C%20every%20update%20since%20were%20ok.%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20a%20perfect%20world%20we%20would%20have%20more%20people%20testing%20every%20computer%20type%20with%20every%20software%20before%20deploying%20the%20upgrades%2C%20but%20needless%20to%20say%2C%20this%20is%20not%20possible%20with%20just%20one%20person%20managing%20clients.%20At%20some%20point%2C%20something%20might%20go%20wrong%2C%20we%20all%20know%20this.%20But%20we%20have%20disaster%20recovery%20plans%2C%20and%20most%20users%20can%20do%20a%20OSD%20from%20their%20own%20desk%20getting%20the%20system%20operational%20within%20the%20hour.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20find%20that%20keeping%20the%20endpoints%20secure%20and%20compliant%20is%20more%20important%20in%20the%20long%20run.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32395%22%20target%3D%22_blank%22%3E%40Andres%20Pae%3C%2FA%3E%26nbsp%3BNobody%20said%20do%20not%20use%20LTSC%2C%20and%20your%20example%20of%20static%2C%20automated%20systems%2C%20conducting%20the%20same%20tasks%20over%20and%20over%2C%20with%20little%20use%20of%20new%20features%2C%20doing%20nothing%20but%20these%20specific%20tasks%2C%20well%20this%20could%20be%20one%20of%20the%20use%20cases%20where%20LTSC%20is%20the%20best%20choice.%20Just%20think%20it%20through%20first.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Update 7/15/2019:  The content in this post applies to PC and laptop type devices converted to Windows 10 Enterprise LTSC, and not devices purchased with Windows 10 IoT Enterprise pre-installed. Examples of the latter include kiosks, medical equipment, and digital signs, i.e. use cases where devices are commonly treated as a whole system and are, therefore, “upgraded” by building and validating a new system, turning off the old device, and replacing it with a new, certified device. Organizations that leverage this approach are seeking the manageability and security of Windows 10 while staying on the same operating system version for the life of the device.


If you ask someone from Microsoft, or read industry guidance, about the best strategy for managing Windows 10 updates, the overarching recommendation is to use the Semi-Annual Channel (SAC) as the default servicing channel for Windows 10 devices. With the Semi-Annual Channel, devices receive two feature updates per year, and benefit from the best performance, user experience, security, and stability.

The Long-Term Servicing Channel (LTSC) is designed for Windows 10 devices and use cases where the key requirement is that functionality and features don’t change over time. Examples include medical systems (such as those used for MRI and CAT scans), industrial process controllers, and air traffic control devices. These devices share characteristics of embedded systems: they are typically designed for a specific purpose and are developed, tested, and certified before use. They are treated as a whole system and are, therefore, commonly “upgraded” by building and validating a new system, turning off the old device, and replacing it with the new, certified device.

We designed the LTSC with these types of use cases in mind, offering the promise that we will support each LTSC release for 10 years--and that features, and functionality will not change over the course of that 10-year lifecycle.

Differences between the Semi-Annual Channel and LTSC

As I noted above, Windows 10 devices in the Semi-Annual Channel receive twice-yearly feature updates, once in the spring and once in the fall. These updates contain new features, services, and other major changes. Security updates, optimizations, and other minor updates or patches are released every month thereafter.

To deliver on the commitment of no changes to features or functionality, a Windows 10 LTSC release does not contain any of the components of Windows 10 that may change over the life of the release. These components include Microsoft Edge (as a modern browser, it is constantly evolving to support the current modern browser web standards) as well as components/applications regularly updated via the Microsoft Store, such as Camera, Cortana, OneNote, and other modern apps that continue to advance with innovative improvements. 

Internet Explorer is included in Windows 10 LTSC releases as its feature set is not changing, even though it will continue to get security fixes for the life of a Windows 10 LTSC release.

The LTSC cadence

We create a new LTSC release approximately every three years, and each release contains all the new capabilities and support included in the Windows 10 features updates that have been released since the previous LTSC release. Unlike the year-and-month terminology employed to describe Windows 10 features updates (e.g. 1703 or 1809), LTSC releases are named with a specific year, such as Windows 10 Enterprise LTSC 2016 or Windows 10 Enterprise LTSC 2019, and they align to perpetual Office releases such as Office 2019.

Each LTSC release receives 10 years of servicing and support[i]. During the life of a LTSC release, you can upgrade your devices to the next or latest LTSC release free of charge using an in-place upgrade, or to any currently supported release of Windows 10. Because the LTSC is technically its own SKU, an upgrade is required from Windows 10 Enterprise LTSC to Windows 10 Enterprise, which supports the Semi-Annual Channel.

As with the Semi-Annual Channel, LTSC devices receive regular quality and security updates to ensure that device security stays up to date. While quality updates are available for Windows 10 Enterprise LTSC, you can choose to defer them using tools such as Windows Update for Business or System Center Configuration Manager.

Making a fully informed choice about the LTSC

Before its release and throughout the first year of Windows 10, many predicted that LTSC would be the preferred servicing channel for enterprise customers. This has turned out not to be the case, and the SAC is the predominant choice for enterprises today.

I’m currently working with a few early LTSC adopters who are now looking to unwind their LTSC deployments and shift to SAC. There are several reasons why using the LTSC can turn out to be the wrong fit for the Windows 10 devices in an organization. For example, one organization deployed LTSC to bring forward the same IT rules and image creation and management processes they had used since Windows XP, in this case to new Surface devices. You can imagine the reaction of their end users when they excitedly opened their new Surface devices, only to find that features such as Camera, Ink, and Pen did not work—and that they were missing many of the modern, touch friendly version of apps—because the devices had been “repaved” with a Windows 10 Enterprise LTSC release.

Another reason some organizations chose to adopt the LTSC centered around application compatibility. In talking with some of these organizations; however, initial concerns about application compatibility from release to release in their environment have proved to be a non-issue.

Considerations

All too often, I have seen strategic decisions about Windows 10 servicing options and the use of the Long-Term Servicing Channel driven by the wrong criteria; for example, IT professional familiarity prevailing over end user value and impact. The LTSC is designed for devices and use cases where features and functionality will not change. It provides 10 years of security servicing to a static Windows 10 feature set. If you are considering the LTSC for devices in your organization, please consider the following:

  • Silicon support: Windows 10 Enterprise LTSC will support the currently released processors and chipsets at the time of release of the LTSC. When choosing to utilize the LTSC, you must factor hardware into your decision, making sure you have a long-term supply of devices and service components for the life of your expected usage of the device. If the hardware your device is using needs to be replaced in five years, do you have a replacement supply to support the version you are running? You also want to be sure you have a hardware solution that will provide you with extended driver/firmware support to match your expected lifecycle use of the LTSC for that device. (See the Lifecycle FAQ to learn more about the Windows Silicon Support Policy.)
  • New peripheral support: Because the API and driver support models are not changing, the LTSC release you deploy may not support new hardware or peripherals that you need to use in your organization.
  • Application support: With each Semi-Annual Channel release following an LTSC release, there is a growing gap in APIs and functionality between the current Windows API in use by most all devices, and previous LTSC releases. Many ISVs do not support LTSC editions for their applications, as they want their applications to use the latest innovation and capabilities to give users the best experience. This is the case with Office ProPlus, which does not support Windows 10 Enterprise LTSC releases as it relies on Windows 10 feature updates and the Semi-Annual Channel to deliver the best user experience with the latest capabilities. (If you were using Windows 10 Enterprise LTSC 2019, you would, therefore, need to use Office 2019.)
  • Best security: Windows 10, with the latest feature update installed, is always the most secure release of Windows 10, offering the latest security capabilities and functionality.
  • Best stability: Windows 10, with the latest feature update installed, has the latest performance and stability improvements.
  • Greatest hardware choice: New devices target and ship with the latest Windows 10 release to light up new hardware capabilities and improvements.

Summary

The Long-Term Servicing Channel a tool designed for a specific job. When used for the right job, it’s a great solution, but when misaligned, it can be like trying to drive a screw with a hammer. It’s, at best, unsatisfying, and likely problematic at some point.

If you understand the considerations listed above, have secured hardware and support to align with the intended duration of usage, and have secured support for your applications, the LTSC can provide your organization with years of secure, static operation, with full servicing and support for its 10-year lifespan. For most use cases; however, I recommend the Semi-Annual Channel as the better option for security, stability, and hardware/application capabilities, and the overall experience of your end users.

To learn more, check out our on demand session from Microsoft Ignite on The pros and cons of LTSC in the enterprise.


[i] Ten years of support includes a minimum of five years Mainstream Support (during which both security and non-security updates are provided) and a minimum of five years Extended Support (during which only security updates are provided). Please see the Fixed Lifecycle Policy for Microsoft Business, Developer and Desktop Operating Systems for more detail.

30 Comments
Super Contributor

You tell that preferred choice is changing in the industry? Any approximate numbers? Say a year ago 30% of enterprises preferred LTSC and today 25%?

 

I would love to stay on SAC, but with limited IT human resources, budget and time (like in most SMBs) it is too burdening to keep up. And what about "stability" flop of 1809? I doubt any serious org has started even testing and i feel 1903 will be released just after most update to the latest version. 2 updates per year is too often (i know i can skip, but what is the point then to use SAC anyway). We don't have money for Intune, SCCM, Enterprise versions. Dealing with feature updates via WSUS is PITA. Btw, is there x64 only feature update for 1809 in WSUS finally? A few weeks ago there was none. Why advertise new cool feature like 2 times smaller update size by splitting update into x86 and x64 and only providing packages for older versions?

 

I think LTSC believers won't disappear soon, as many may prefer stability (real stability) over theoretical improvements and possible problems. If anything, they numbers may grow after the 1809 blunder.

Microsoft

Hi Oleg,

 

Thanks for your discussion kickoff.  First to your question.

 

You over estimated LTSC usage.  Let me use a 3rd party source, so we remove any concern I'm trying to cook the books :)

 

https://meterpreter.org/data-shows-that-windows-10-april-update-market-share-soared-to-90/?cn-reload...

 

According to InfoTech's reporting, LTSC is at MOST 2% of all devices.  Other then servers and special purpose devices, it really is the exception today, and for desktop productivity usage,  movement is from it, to SAC.  

 

What is the LTSC end user missing?

He is a small subset, organized by release, of the featurs and functionality added in subsequent SAC releases.

SAC.JPG

I'm glad you are finding  LTSC great and stable for you,  I agree it is. I would submit for your consideration ( based on real data telemetry, and actual innovation we have added ) that I know the subsequent SAC builds are even more stable, better performant, and more secure. We will continue to work to address your servicing concerns and challenges, and hope that in the near future, we can make it work for you.

 

John 

New Contributor

Hi John.

I give You another example.

In our industry ( kind of Software development) we are using hundreds of different "bot" machines. Automated testing, compiling, building, etc systems. Most of those are still running older versions of Windows. Because people responsible for those processes doesnt have  absolute certainity, that those routines  work fine after every SAC upgrade. For those systems most of end-user features and functionalities introduced with new W10 release are pointless. So, for IT is very hard to sell them idea-  to screw twice per year all their systems. They have much important jobs to perform than test compatibility with next W10 release.  We are trying to keep our user stations on more recent versions - it cost us lot (time resources) and end-users dont understand why it is needed. they dont see benefit, or it is tiny compared to introduced problems.  

Super Contributor

Yes, most changes on paper sound cool for IT enthusiasts, but not so interesting for end users, who maybe just work with a few spreadsheets and docs and not so into technology. They don't care about timeline, or doing screenshots with new app or connecting their phones to PC, etc. Main reason for IT to install it is to keep up to date, to have monthly cumulative updates weight less and to get IT updates like better Autopilot support and new policies, etc.

Occasional Visitor
Visitor

@John Wilcox The statistics provided in your earlier comment are extremely misleading in that they are based on Windows Store ads which would not include LTSB/LTSC releases at all. They would also not include organizations where the Windows Store is disabled via GPO. This is specifically mentioned in the article. All that is proved here is that Microsoft Update is extremely aggressive in Windows 10.

 

As for LTSC vs SAC: I would much rather spend the time to build a new image every year (or so) as new LTSC versions are released when the alternative is to have the user experience across the organization be turned upside down every six months as workflows change in Windows. That's before considering the major stability issues that seem to be plaguing the SAC branch on a regular basis.

 

In our organization, the most unstable machines by far are among the three that run SAC vs the many hundreds running LTSB at the time of writing.

Occasional Visitor

These types of posts really upset me. You want consumers and IT Admins to stop resorting to an OS you say is intended for medical devices and kiosks? Then stop consistently putting out versions of Windows 10 that break NICs, lose data, reboot sans warning, and come pre-loaded with adware like candy Crush, xbox apps, start menu ads, lock screen ads, and 2 browsers. Can I ask why even Microsoft hasn't been able to untangle IE from their own "latest and greatest" rendition of Windows 10? "WaaS" is very new terminology and has yet to prove sustainable as a model. Lest we forget that a large portion of the Win10 market share came from Microsoft imaging entire organizations overnight with clandestine Windows 7 updates sometime around early 2017. People need usable images for VDI environments with video/network throughput limitations. People have older hardware that needs to be able to run mission critical, legacy software. Cortana and the App Store have no place on the majority of many workshop machines. Stop blaming your users for adopting something that actually works as a viable solution with STABLE updates. Stop using paying customers as beta testers. Can I ask what exactly happened to Patch Tuesday? Because for the last year, at least, updates have gone through no QA team and come down the channel seemingly at random. Occasional out of band patches are fine. Building the plane as it's taking off and then yelling at your passengers for deploying their parachutes when you hit turbulence is a good way to have an entire organization shift away from your airline.

 

I will point other readers to: https://www.howtogeek.com/395121/windows-isnt-a-service-its-an-operating-system/

Senior Member

One key element that haven't been touched in this article is the capability of the features in Windows 10 from 1511 to 1809, John posted a nice Picture of all the new features that has been added to Windows 10, and some ppl mock those and say that their users does'nt need to connect their phone or whatever. But they miss a vital Point and that's the capability of the said feature, for example Delivery Optimization "DO" the functionality of that so important feature has vastly imoproved since launch, and that's not the only feature that has been improved. If your on LTSC for the 10 year support, god knows what all background functionality you will miss out on. Being on LTSC for a longer time will also get you further behind the real World so when the day comes to upgrade to say LTSC 2025 you might find yourself in a situation where your dev team has been quietly developing with VS 2008 and all of a sudden you have a migration Project on the scale of Windows XP to Windows 7. Ofcource there are systems that are best being left alone from the fast paced outside World, but they are few and far apart.

 

Sure the quality in Microsoft releases have gone down since they fired thier whole QA team, so please MS rethink! but using that as an excuse to go for LTSC, nah.

Occasional Visitor

A whole lot of the problem with people deploying LTSB/LTSC to do the desktop (us included BTWbtwould be solved if the Enterprise and Education versions of Windows were exactly that & not just re-badged versions of Home with a few enterprise features turned on. Lose Cortana, Windows Store, Candy Crush, Xbox, Music, etc. and you'd be half-way there.

 

Add in some decent modern tools to customise and control the deployment of images (SCCM is way overkill for anyone with less than thousands of seats (we tried - we needed more resources to run SC than the rest of the organisation), WDS seems stuck in the Windows 7 era) and the whole LTSB/LTSC on the Desktop issue would go away.

Super Contributor

Actually, that's exactly what i meant in my comment, that users don't care for user features, so the only incentive for IT admins to install updates every 6 months is to stay secure and to get those hidden to the eye improvements (DO, Autopilot, etc.). The problem is that you can't "sell" these updates to users/execs. They need something useful they can get their hands on. As they don't get it, they are just annoyed with often updates that take long to install and don't see point in that. You want me to explain spreadsheet users how great recent DO improvements were? Of course, you can have an argument that it can save internet traffic cost and make less impact on network (in DO case). But on my previous job updates were handled via WSUS and we had unlimited broadband internet, so DO wouldn't do much for us. Anyway, IT admins are now tasked to do big updates twice a year, users don't see value in this. Background improvements are neat, if you have real use for them, but in the end, companies need a stable and secure OS to do work (by secure i mean just monthly security updates). This can be reduced to 1 update per year.

Super Contributor

MS is touting Autopilot (and Intune) to be that next "image" deployment tool (not really an image in the regular sense, just a set of settings that will prepare Windows for work). But i can't see this being used in public sector where you don't know who will win new PC shipment tender. Could be some smallish local retailer who never heard about Autopilot.

Visitor

Dear John,


i've recently read your interesting post about WIN 10 LTSC.

At the moment i am working on a project for a company to roll out WIN 10 and planning to use LTSC.

I have one question about the following sentences in your text:

"Each LTSC release receives 10 years of servicing and support[i]. During the life of a LTSC release, you can upgrade your devices to the next or latest LTSC release free of charge using an in-place upgrade, or to any currently supported release of Windows 10. Because the LTSC is technically its own SKU, an upgrade is required from Windows 10 Enterprise LTSC to Windows 10 Enterprise, which supports the Semi-Annual Channel."


Is the meaning right, that i will get each LTSC upgrade within ten years for free??? That will be a great feature.

Like in 5 years when there is for example version 2105, I will get that for free?

Can I ask you where you've got that information?


Thanks in advance and kind regards,

Marco

 
 
Occasional Visitor
Maybe there wouldn't be so much interest in LTSC if your core offerings weren't so full of bloat. No IT professional asked for your data spigot aka telemetry. You can try and cram Edge down our throats all you want but we don't want it. We didn't ask for nor do we want all the consumer apps suggestions, chibi graphics and gamification. The problem is that you (Microsoft) have an agenda that does not align with the stated needs of IT professionals and advanced users. Rather than deliver the products that we want, you'd rather try to gaslight us into thinking that we're crazy for wanting an unbloated OS. An Xbox app in Windows 10 Enterprise? Really dude? Really?
Super Contributor

It is even included in the Server SKU :D I have asked about Xbox app on another thread about Server security hardening and only got an answer that some role/feature might need Xbox to do something, like VDI or RDS (remote workers wanting to play some games?:)).

Occasional Visitor

John, very nice overview. I work with OEM's that build appliances and I provide guidance primarily for OEM's rather than corporate america.  For those that are interested in more details around how to license via the OEM channel please have a look at my blog on Windows LTSB/LTSC here: http://ocs.arrow.com/msembedded/blog/to-update-that-is-the-question/

I would also mention that you did state it is a free upgrade between LTSC editions and that is not the case in the OEM channel. In fact in-place upgrades are prevented with the LTSC edition and it does require the purchase of a full new upgrade license.  

Regular Visitor

@WindowsChamp beat me to it. Again! Smiley Happy

Frequent Visitor

Ok, I guess I want to throw my 2 cents into LTSC piggy bank :-). So, we have big Enterprise organization. Yep, one of those big ones that everyone knows. EVERYONE! And of course just like everyone else on this planet scared of staying on W7 because soon will be not supported, and as result non-compliance, audit, regulators and big, big fines! Does not sound good! So started moving with SAC. 1709. Well, because it was 1 year ago. 1803 was skipped - thanks to MS for announcing new strategy of supporting fall releases for 30 months instead of originally planned 18 months! Now got 1809. Yes, it was mess! In fact it was disaster. You were saying 09 means September? Yeah right! How about November? October was bug-fixes time ha-ha-ha! Halloween of bugs. But as you know, November is the time when things slow down. Why? Well, many reasons. First it is new fiscal year. First month is always slow. Besides everybody is in the Christmas mood. Santa coming to town in case you did not know. Then it is January, best time to go Dominican, Mexico or Cuba - prices doing down! Who does not like cheap vacation all-inclusive? Then February things start picking-up slowly. But hey, now business got scary, they want to test their Applications, but they don't have time. And you know, all those 3rd party agents? Security agents? Have you heard about them? They also may not work in 1809. So if we push 1809 we may break all machines. Risk is real, and everybody scary. But things not getting any better. Soon it will be 1909 and it only will be worse. So this is a road to perdition. What you suggest? Stay on 1709 or jump to 1809? What if something happens? It will be the END. And nobody want the END. Everybody want to live. Everyone want to retire happy ha-ha-ha! Now let's see why SAC is better (as per you list): 1. Edge is missing. Sure. But Edge is disaster. There are problems with SSO via ADFS because MS did not allow any browser to access ADFS, each Agent string must be explicitly written into ADFS configuration. You saying add this to ADFS? Sure. But do you remember we were talking about large enterprise? 5-second command to execute in PROD environment takes easily 6 months. Why? Don't ask. Just believe! So for any changes we are looking months and months to implement. 2. Cortana. We disabled it in SAC anyway, so why bother? Nobody use Cortana, except MS people who present something on Ignite! 3. App Store. Most enterprise block it - otherwise this is a Pandora box! If users start installing what they want this will be the end! 4. Same thing for many other things. So what really business need? They need their Applications. And they want them to work stable today, tomorrow and in 5 years, day after day. And if changes occurs so often and could break things, this is not good. Did I almost convinced you why large enterprises should go with LTSC? Ha-ha-ha! Your turn!

Frequent Visitor

Just adding my two cents here. Most users keep their devices for an average of 5 years. If MS supported each Windows SAC release for up to 5 years, it would be so much easier for enterprises to embrace SAC over LTSC. That would mean users get a new Windows version every time they change their PC as opposed to disrupting them every year or so at the risk of breaking their applications.

 

To all those LTSC issues raised in the article, they all have a workaround or alternative so they are of no concern and I can safely dismiss them as fear-mongering designed to fit Microsoft's agenda. After all, let's look at who wrote the article. The author conveniently failed to even take a peek at the recent series of upgrade disasters and delays Microsoft is facing. I think it is evident Microsoft can't keep up with their own agenda, which has hurt their credibility. If they are to be successful at repairing the damage, first they have to earn our trust before we can take their agenda seriously by releasing stable and trustworthy upgrades that are consistently on time. Constant delays is a clear sign of trouble. If MS can't keep up with their own pace, what makes anyone think that the average enterprise will be able to do the same? We just don't have the resources to go around every 6 months upgrading machines. If they slowed down the release pace to maybe once a year, and support those releases for up to 5 years, I believe Microsoft might be able to keep up with the pace, they won't stumble as much, make it much easier for enterprises, significantly reduce the push back, and have a much more successful Win 10 upgrade path.

Super Contributor

MS is surprisingly quiet about the 19H2 update and there are rumors it might be very minor stability update instead of a regular feature update. Although i would just scrap it and go the 1 update per year route. 5 years though? Nah, that's too long. Especially with laptops. They get beaten up badly (if used as laptops and carried around a lot). And they get morally old. 3 years seems like a more reasonable age to change.

Occasional Visitor

We use the LTSC version. I originally went the route of 1803 Enterprise and had so many problems:

- Removal of the bloatware is not clean, on new sysprep'd computers there are always errors regarding apps that have been removed in the Application log.

- Inconsistent application performance

- Using GPO's to disable the Store, Hello, Cortana doesn't do this cleanly, Application errors are consistently reported. Why, if they are turned OFF.

- With patching and updates, some of the apps "return" which is unacceptable. (ie OneDrive)

- Our computers are for "work" not home, shopping apps are inappropriate.

- We don't want "Advertisements" on work computers

 

We want stability, clean and lean OS that is quick and for work. The adoption of new "Features" should always be an individual companies decision, not Microsofts. All non-required features are just applications that bloat the OS and increase management.

 

We don't have the staff to deal with, 6monthly Feature updates, which technically are "inplace-upgrades" and all their consistencies.

I think the 3yr rotation was good, 2yrs of stability. Then the 3rd year was dev/test/implementation/tidy up for the next version, if it was stable. We skipped all of Windows 8.

 

Occasional Contributor

I’d like to know how are we to keep up with these updates. By the time I’m done getting 1903 out, 1903 will be end of support and I’ll have to start rolling out whatever new build is current then.

 

What happened to 10 year long OS’s like XP and 7?  Now I have to upgrade the OS every 2 years just to keep security updates coming down the pipe?  We just did an internal NESSUS vulnerability scan and 18 machines on 1703 and earlier came up on the report for being end of life.  I’m almost done getting all the Windows 7 machines up to Windows 10, but even if these machines have a 5 year lifespan, the hardware will outlive the OS!  It used to be we bought a generation of computer preloaded with an OS (like Win 7) then 5 or 6 years later those computers would be refreshed with a newer model and a newer OS (like Win 10).  

If you want to do feature updates fine, but keep those security updates coming down the wire.  I can’t tell you how many 1607 builds we have that just will NOT update at all to 1803,1809 or 1903.  “Something went wrong” is not helpful.

Super Contributor

Keith, it might help first updating to older build. Some PCs here were failing to upgrade from 1709 to 1809. Yeah, it was giving a confusing error that "some driver is incompatible". No exact name, error, nothing. Just a button to proceed anyway. If i proceed, it works ok after the update. But this requires manual intervention. Surprisingly this works, if you first update to 1803 and then to 1809. So for failing machines i'm using this approach.

 

Btw, we also have 15-20 1703 machines and it seems they are not going to be updated soon as application is not compatible with newer versions of Windows and there are also some political decisions to be made to move on. 1703 was released in 2017 and is expiring sooner than Windows 7. 1709 released in the same year had some drastic change breaking the application. I know that MS now has so many versions on their hands to support all of them for at least 5 years. But hey, there is the LTSC version to avoid this problems, no? /s

Regular Visitor

@Keith Sauer

  

Hi Keith.  

Happy to help, I hear frustration in your feedback, but missing a lot of details that I might help with.

Some initial thoughts, feel free to engage with specifics if you would like help.

 

1) Once we work through your issues, I'm confident we will get you to were the vast majority of devices are today, installing updates and getting the security, end user functionality, and quality improvements that come with them.  There are literally millions of devices that do this every day, consumer, slam business and large enterprise.   You did not indicate with SKU you are using, but I'll assume pro is you are focused on the 18 month security servicing for each release. 

 

2) You forecast that it will take you more than 18 months to roll out 1903 to your organization, but no details on what is limiting that velocity.  I work with many enterprise customers ( other than Microsoft ) who  update 1000s  of devices weekly, some even more. What are the limits that you running into and effecting that velocity?

 

3) Just to make sure , though I think you know this,  for Pro SKU, we provide security updates for 18 months. So if you choose , you can update devices as slowly as <1 / year, and still stay security patch current, you do not have to update 2/year.  The customer trend I do see is that once you get process in place to update once every 12 months, then updating more frequently, if you choose is incremental. Most of the change management is completed in getting to update more frequent than every 3-4 years, ie once per year. 

 

4) Do you have specific issues that have prevented you from updating those devices on 1703? How do you manage updates? 

 

5) We have updated millions of older machines that started life on Windows 7 , and now are now extending their useful life with improved security and new functionality with Windows 10, and the Windows 10 feature updates.  Windows 10 will certainly outlive the HW, but while it does so, it is extending the life of that HW. 

 

6) 1607 devices that wont update.  

Tell me more?  Have you check free diskspace?  This is one of the most common sources of update failures, lacking free space to download and install the updates.   Do you have 3rd party encryption and security products that might be conflicting? Many then, fewer today still, required you to first uninstall, update the 3rd party tools before the update, though I would expect you would have worked through this with other devices that did update, so check disk space. Have you used the Setup Diag tool?

 

John

 

 

 

Regular Visitor

@Oleg K 

 

Hello my old friend.

 

Tell me more about the "drastic change" breaking your application. If this is the case, by all means, take advantage of our App Assure program, no cost to you, and we will correct or help re-mediate the issue for you. App compat , now with enterprise, LOB data included has been greater than 99%, we have had to make very few code changes/fixes,  but if we break something, we want to correct it. 

 

JOhn

 

 

 

Super Contributor

I'm not sure if i can disclose such information (even the name in-house app). What i meant, that one might assume that going from March version to September one can expect it to be mostly compatible. This seems like 1909 might be such example. Although looking at Insider builds there are still a bunch of changes, not just small fixes.

Regular Visitor

 

I'll be very clear. you should expect it to be COMPLETELY compatible release to release, not just mostly, for those apps that are using public APIs.  If you have an app that is using undocumented calls, or other non-supported approaches,  no-promises. 

If its not, use App assure program so we can fix it for you and others.

 

It's often the little things that are annoying.  I don't have a large deployment but every release there is something that takes time to fix and track down.

 

1903 was https://accountants-community.intuit.com/articles/1860059-pdf-and-component-repair-tools-for-lacerte... I had to repair the pdf printer for a LOB app.

 

It's typically something relating to printing, one time it was an Outlook app that stopped working and I had to repair it.  At home I've lost my hdmi display to my Lenovo docking station (and this isn't a cheap laptop either).

  

If I had thousands of desktops this wouldn't scale.

 

I personally only do a feature release a year for this reason.

Occasional Visitor

To be honest, I really do not see how you have such a big issue keeping up to date on Windows 10. First off, LTSC is a bad choice for close to every user in any case, to many potential pitfalls and limitations. It's an embedded/IoT solution.

 

Managing computers without management tools is not easy, but if your are serious you should also be serious managing your computers, making sure they are up to date and compliant. With an increasing degree of travel and out of office usage, as well as interaction with external systems and users, firewalls are not the most important point of security any more, the endpoint is. Not having absolute control of the endpoint can turn out more expensive than you might think.

 

I'm using a combination of SCCM and Intune managing endpoints, and as a single admin I manage thousands of devices, Windows, iOS and Android, in a more diverse, both geographically and methodically, environment than most other businesses. 

 

As for the 1806 issues, well, I did not experience any. Nor did I have any issues with any other release either. My impression is, most people did not have any issues, but a small percentage of close to a billion devices is still many systems and users. When the new release is out, I wait a few weeks before I update a small set of test computers in my office. I do some testing trying to provoke some errors, while also looking for people having issues online, trying to identify HW and SW setups common for our environment. I then deploy the update to a set of chosen early adopters/power users, yeah, they know they are guinea pigs, and let them run the new the update for a while. I then deploy for the entire organisation. All data is stored off device, and a full device rollback takes about one hour, should something go bad. So far I've had issues with one upgrade on one computer, out of several thousands. And, after redeploying the OS, every update since were ok.

In a perfect world we would have more people testing every computer type with every software before deploying the upgrades, but needless to say, this is not possible with just one person managing clients. At some point, something might go wrong, we all know this. But we have disaster recovery plans, and most users can do a OSD from their own desk getting the system operational within the hour.

We find that keeping the endpoints secure and compliant is more important in the long run.

 

@Andres Pae Nobody said do not use LTSC, and your example of static, automated systems, conducting the same tasks over and over, with little use of new features, doing nothing but these specific tasks, well this could be one of the use cases where LTSC is the best choice. Just think it through first.

Occasional Visitor

Serpentbane, but that is the point. 

One of the main reasons why organizations chose LTSC in the first place is to NOT get the "new features" you were talking about. 
Microsoft made it very hard on Windows 10 to get rid of things the Organization does not want - things like setting file associations etc. needs a lot of workarounds to make it work because it is obvious Microsoft does not care about Admins anymore. 

This was much better on LTSB/C, as a lot of the stuff that people want gone (Store, UWP Apps, Edge, Cortana... and their file associations etc) were not there to begin with, so they didn't need to be disabled/hacked out/worked around, etc. 

Also, we deploy our devices for a four year cycle, and by using LTSC, we could just deploy these devices and keep them on one version for the entire Lifecycle - no changes, no stuff breaking. 

It is the little things that happen with the Windows 10 updates - defaults get changed, they add new icons to the task bar (I had a ton of support calls when the unwanted "Mail" App was auto-pinned to the taskbar with upgrades), the interface is changing constantly (looking at you, Windows Search) ... people do not want that. Neither do we want that as Admins. You might like the "new Features", I  just see "more crap I have to disable/remove". 

Also, people HATE when the upgrades arrive. They take a long time, happen when they want to shutdown/quickly reboot their machine and hinder then from going home (99% Laptops), and are a hassle. And I have trouble forcing my users to have a single reboot a month as it is (IT had to override Management on that one). 

Just remember that back on any other version of Windows, you only had to worry about deploying to a device once, have it auto-configured by whatever scripts you built, and only worry about the monthly updates.

 

Now, with every new Windows 10 version I have to verify that my scripts still work (PSA: often they get broken by changes from Microsoft), I have to verify my Drivers and Software all still work, figure out where Microsoft changed the presets set by users in the upgrade process, where they added unwanted "features" and GUI elements, update my GPOs ... Administering Windows 10 devices to a level that my Organization wants (not to a level that Microsoft deems "suitable") creates about five times as much work as Windows 7 or Windows XP did before. 

 

I know, a lot of people seem to like Edge, Cortana, etc.. but we don't. We don't want them, we don't need them. We do not need UWP, we do not need the Store, we do not need another Browser or Security Software. We just want Devices for our Lifecycle that behave consistently from one day to another, and GUI changes are not consistency. 

It was hard enough to figure out how to turn most of the annoyances on Windows 10 off, but to have to do it repeatedly every 6-12 months is just.. argh. 

 

Just as an anecdote, I had a script (why do I need a script for this) that unpinned Edge from the Task bar - as it was not a normal icon but some system functionality deeply hidden that put it there. In the end, it worked and the icon was gone - and it worked fine in 1809 or older. When we moved to 1903, it still worked that it unpinned the icon - but now users couldn't pin stuff to the taskbar anymore, as it was forgetting the pins after logout.  Why is simple stuff like that so hard... 

I am currently moving all our devices up to 1903, and when that is done, to 1909...and we expect to stay on that version as long as support runs out (30 Months)... and until then, hopefully Microsoft will have revised their update model, as they seem to begin to realize that 6 Months is way too often in corporate land. 

in an Ideal world, there would not be two, but three Tiers to Windows 10:

SAC, the same as before, 18-30 Months support.

LTSC: The same as before, 10 Years support.

LTS-Business: New Channel, no new feature updates, released every ~3-4 Years, with an equivalent support period of ~5 Years. Create one Year of overlap from one release to the next. 

 

Frequent Visitor

Whenever I hear someone telling me they "do not see how you have such a big issue" with anything, I totally get it. They don't see it because they don't have to work in the environment we work. So they don't understand it, and naturally they don't see what the issue is.