The next Windows 10 Long Term Servicing Channel (LTSC) release

Published Feb 18 2021 12:00 PM 176K Views
Microsoft

Windows 10 introduced Windows as a service, a method of continually providing new features and capabilities through regular feature updates. Semi-Annual Channel versions of Windows, such as version 1909, version 2004, and version 20H2, are released twice per year.

In addition to Semi-Annual Channel releases of Windows 10 Enterprise, we also developed a Long Term Servicing Channel for Windows, known as Windows 10 Enterprise LTSC, and an Internet of Things (IoT) version known as Windows 10 IoT Enterprise LTSC. Each of these products was designed to have a 10-year support lifecycle, as outlined in our lifecycle documentation.

What are we announcing today?

Today we are announcing that the next version of Windows 10 Enterprise LTSC and Windows 10 IoT Enterprise LTSC will be released in the second half (H2) of calendar year 2021. Windows 10 Client LTSC will change to a 5-year lifecycle, aligning with the changes to the next perpetual version of Office. This change addresses the needs of the same regulated and restricted scenarios and devices. Note that Windows 10 IoT Enterprise LTSC is maintaining the 10-year support lifecycle; this change is only being announced for Office LTSC and Windows 10 Enterprise LTSC. You can read more about the Windows 10 IoT Enterprise LTSC announcement on the Windows IoT blog.

Frequently asked questions (FAQ)

Why are you making this change to Windows 10 Enterprise LTSC?

Windows 10 Enterprise LTSC is meant for specialty devices and scenarios that simply cannot accept changes or connect to the cloud, but still require a desktop experience: regulated devices that cannot accept feature updates for years at a time, process control devices on the manufacturing floor that never touch the internet, and specialty systems that must stay locked in time and require a long-term support channel.

Through in-depth conversations with customers, we have found that many who previously installed an LTSC version for information worker desktops have found that they do not require the full 10-year lifecycle. With the fast and increasing pace of technological change, it is a challenge to get the up-to-date experience customers expect when using a decade-old product. Where scenarios do require 10 years of support, we have found in our conversations that these needs are often better solved with Windows 10 IoT Enterprise LTSC.

This change also aligns the Windows 10 Enterprise LTSC lifecycle with the recently announced Office LTSC lifecycle for a more consistent customer experience and better planning.

You state that you are making this change to Windows 10 Enterprise LTSC to align with the changes to Office LTSC. Has your guidance changed on installing Office on Windows 10 Enterprise LTSC?

Our guidance has not changed: Windows 10 Enterprise LTSC is designed for specialty devices, and not information workers. However, if you find that you have a need for Windows 10 Enterprise LTSC, and you also need Office on that device, the right solution is Windows 10 Enterprise LTSC + Office LTSC. For consistency for those customers, we are aligning the lifecycle of the two products.

What about the current versions of LTSC – Windows 10 Enterprise LTSC 2015/2016/2019?

We are not changing the lifecycle of the LTSC versions that have been previously released. This change only impacts the next version of Windows 10 Enterprise LTSC, scheduled to be released in the second half of the 2021 calendar year.

What should I do if I need to install or upgrade to the next version, but I need the 10-year lifecycle for my device?

We recommend that you reassess your decision to use Windows 10 Enterprise LTSC and change to Semi-Annual Channel releases of Windows where it is more appropriate. For your fixed function devices, such as kiosk and point-of-sale devices, that need to continue using LTSC and are planning to install or upgrade to the next version, consider moving to Windows 10 IoT Enterprise LTSC. Again, we understand the needs for IoT/fixed purpose scenarios are different and there is no change to the 10-year support lifecycle for Windows 10 IoT Enterprise LTSC. For information on how to obtain Windows 10 IoT Enterprise LTSC, please reach out to your local IoT distributor.

Is there a difference in the Windows 10 operating system between Windows 10 Enterprise LTSC and Windows 10 IoT Enterprise LTSC?

The two operating systems are binary equivalents but are licensed differently. For information on licensing Windows 10 IoT Enterprise LTSC, please reach out to your local IoT distributor.

Where can I find more information about Windows 10 IoT Enterprise LTSC?

You can learn about the different Windows for IoT editions, and for which scenarios each edition is optimized in the Windows for IoT documentation. You’ll also find tutorials, quick start guides, and other helpful information. Check it out today!

When will Windows 10 IoT Enterprise LTSC announce their release?

Windows 10 IoT Enterprise LTSC will be released in the second half of 2021. You can read more about the Windows 10 IoT Enterprise LTSC announcement on the Windows IoT blog.



Continue the conversation. Find best practices. Visit the Windows Tech Community.

Stay informed. For the latest updates on new releases, tools, and resources, stay tuned to this blog and follow us @MSWindowsITPro on Twitter.

78 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-2148335%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2148335%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20let%20me%20get%20this%20straight...%20LTSB%2FLTSC%20has%20been%20forever%20pushed%20by%20Microsoft%20as%20a%20solution%20for%20embedded%20systems%20like%20kiosks%2C%20signage%2C%20medical%2Findustrial%20equipment%2C%20etc.%20Microsoft%20has%20always%20quite%20explicitly%20discouraged%20the%20use%20of%20it%20as%20a%20daily%20driver%20for%20information%20workers%20specifically%20because%20of%20the%20lack%20of%20OS%20servicing%2C%20ongoing%20silicon%20support%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20now%20Microsoft's%20justification%20of%20cutting%20LTSC's%20lifecycle%20in%20half%20from%20now%20on%20is%20that%20customers%20using%20it%20for%20information%20workers'%20machines%20%3CU%3E%3CSTRONG%3Eagainst%3C%2FSTRONG%3E%20%3C%2FU%3EMicrosoft's%20guidance%20found%20it%20to%20be%20a%20hassle%20to%20upgrade%2Fmanage%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat's%20a%20major%20slap%20in%20the%20face%20to%20customers%20using%20LTSB%2FLTSC%20in%20correct%20deployment%20scenarios.%20In%20what%20world%20does%20this%20make%20sense%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBad%20move%20in%20my%20opinion%2C%20Microsoft.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2258453%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2258453%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20is%20a%20difference%20between%20an%20operating%20system%20like%20Windows%207%20and%20it's%2010-year-support%20and%20Windows%2010%20LTSC.%20Windows%207%20got%20updates%20to%20support%20new%20hardware%20over%20teh%20years.%20Windows%2010%20LTSC%201809%20f.%20e.%20will%20not%20get%20such%20updates%20(if%20I'm%20right).%20Sooner%20or%20later%20the%20available%20hardware%20on%20the%20market%20changes.%20So%20what%20shell%20I%20do%20with%20an%20operating%20system%20what%20have%20support%20for%2010%20years%20but%20after%20four%2C%20five%20or%20even%20seven%20years%20there%20is%20no%20hardware%20I%20can%20install%20it%20on%3F%20Maybe%20some%20people%20have%20special%20hardware%20what%20will%20be%20sold%20an%20supported%20over%20such%20a%20long%20time%20but%20I'm%20in%20doubt%20that%20this%20is%20the%20case%20for%20the%20most%20of%20us.%20For%20the%20moment%20we%20use%20Windows%2010%20LTSC%201809.%20But%20we%20believe%20that%20we%20must%20change%20to%20a%20newer%20version%20of%20Windows%2010%20LTSC%20before%20the%20support%20for%201809%20ends%20because%20of%20the%20hardware%20problem.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2258818%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2258818%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F171696%22%20target%3D%22_blank%22%3E%40Barbara%20Joost%3C%2FA%3E%26nbsp%3Bthe%20situation%20is%20even%20worse%20based%20on%20your%20scenario.%26nbsp%3B%3CBR%20%2F%3ELTSC%20does%20only%20support%20the%20hardware%20available%20at%20release.%20Means%20if%202022%20LTSC%20is%20released%20it%20should%20support%20Intel%2011%20Gen%20but%20not%20the%2012%20Gen%20(a%20new%20gen%20is%20released%20every%20year%20on%20the%20current%20schedule)%2C%20or%20to%20take%20it%20to%20AMD%20it%20should%20support%20Ryzen%205000%20CPUs%20but%20not%20the%20next%20gen.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2263092%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2263092%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20were%20using%20Win%20LTSC%20with%20Surface%20Pro%207%20with%20no%20issues.%20As%20we%20are%20moving%20to%20Surface%20Pro%207%2B%2C%20LTSC%20is%20no%20more%20compatible%20with%20respect%20to%20drivers.%20We%20have%20placed%20ordering%20500%20Surface%20Pro%207%2B%20on%20hold%20due%20to%20the%20driver%20compatibility%20issue.%20Please%20advise%20on%20fixing%20the%20driver%20issue%20with%20LTSC%20and%20Surface%20Pro%207%2B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2263230%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2263230%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F289393%22%20target%3D%22_blank%22%3E%40K_Wester-Ebbinghaus%3C%2FA%3E%26nbsp%3BThat's%20the%20point.%20We%20use%20a%20for%20our%20LTSC%20installations%20special%20device%20by%20Dell%20what%20is%20especially%20certified%20for%20Windows%2010%20LTSC%20by%20Dell.%20Using%20devices%20certified%20for%20Windows%2010%20LTSC%20was%20the%20hard%20condition%20under%20which%20we%20allowed%20LTSC%20in%20our%20environment.%20As%20long%20Dell%20sells%20this%20device%20in%20the%20given%20hardware%20configuration%20we%20can%20use%20Windows%2010%20LTSC%201809.%20But%20sooner%20or%20later%20Dell%20must%20follow%20the%20change%20in%20the%20CPU%20architecture%20in%20the%20technical%20world%20around.%20At%20this%20point%20we%20must%20change%20to%20a%20newer%20version%20of%20LTSC%20too%20in%20the%20case%20we%20buy%20new%20machines.%20I'm%20sure%20this%20will%20not%20take%2010%20years.%20This%20will%20happen%20earlier.%20So%20it%20makes%20not%20so%20much%20sens%20in%20my%20eyes%20to%20support%20an%20LTSC%20over%2010%20years.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%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-2272666%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272666%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20clarify%20what%20%22Windows%2010%20Client%20LTSC%22%20is%20in%20the%20third%20paragraph%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272683%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272683%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026155%22%20target%3D%22_blank%22%3E%40robinmholt%3C%2FA%3E%26nbsp%3BLTSC%20is%20Windows%2010%20Enterprise%20Long-term%20servicing%20channel.%20Here's%20a%20link%20on%20docs%20for%20information%20about%20what%20it%20is%2C%20and%20what's%20available%20in%20the%20different%20versions%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwhats-new%2Fltsc%2F%23%3A~%3Atext%3DThe%2520Long-Term%2520Servicing%2520Channel%2520%2528LTSC%2529%2520%2520%2520%2CWindows%252010%252C%2520Version%25201809%2520%2520%252011%252F13%252F2018%2520%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%2010%20Enterprise%20LTSC%20-%20What's%20new%20in%20Windows%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281579%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281579%22%20slang%3D%22en-US%22%3E%3CP%3EDo%20we%20have%20a%20better%20date%20on%20availability%20than%20just%20second%20half%20of%202021%3F%20I%20run%20a%20department%20at%20a%20college%20and%20we%20can't%20have%20a%20semi%20annual%20upgrades%20wreck%20software%2C%20so%20LTSC%20is%20what%20I've%20been%20using%20with%20our%20E5%20license.%20I'm%20at%20the%20point%20where%20the%20software%20wants%20the%20newer%20features%2C%20but%20postponing%20a%20Windows%20feature%20upgrade%20for%20X%20months%20is%20still%20not%20a%20workable%20solution.%20LTSC%20is%20the%20best%20way%20forward%20for%20me%20since%20my%20licensing%20allows%20me%20to%20use%20it.%20It%20is%20time%20that%20I%20start%20working%20on%20new%20images%20in%20preparation%20for%20the%20Summer%20work%20to%20get%20everything%20ready%20for%20the%20Fall%20semester.%20I'll%20go%20with%20regular%20Enterprise%20if%20I%20have%20no%20other%20choice%2C%20but%20the%20next%20version%20of%20LTSC%20would%20be%20best.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20it%20matters%2C%20I'm%20KMS%20activated%20so%20switching%20versions%20isn't%20really%20an%20issue%20as%20they%20are%20all%20available%20to%20our%20license%20(Pro%2C%20Enterprise%2C%20LTSC).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281728%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281728%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1033918%22%20target%3D%22_blank%22%3E%40Greg_E999%3C%2FA%3E%3C%2FP%3E%3CP%3EIts%20my%20understanding%20that%20we%20will%20no%20longer%20be%20able%20to%20obtain%20the%20media%20for%20the%20new%20LTSC%20through%20our%20E5%20%2F%20any%20enterprise%20agreements.%20We%20have%20to%20go%20through%20one%20of%20the%205%20Microsoft%20providers%20of%20the%26nbsp%3BWindows%2010%20IoT%20Enterprise%20LTSC%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281766%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281766%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1033918%22%20target%3D%22_blank%22%3E%40Greg_E999%3C%2FA%3E%3C%2FP%3E%3CP%3EHave%20you%20considered%20to%20use%20the%20benefit%20of%20never%20having%20to%20prepare%20any%20images%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20way%20it%20is%20a%20far%20lesser%20pain%20to%20have%20upgrades.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2004%2C20H2%20and%20even%20out%20of%20regular%2021H1%20can%20be%20upgraded%20by%20a%20500%20kb%20update%20to%20the%20lastet%20version.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20about%20an%20automated%20software%20deployment%20with%20MS%20tools%20included%20in%20your%20E5%20license%3F%3C%2FP%3E%3CP%3EThere's%20Intune%20%2B%20Autopilot%20%2C%20MEMCM%2C%20MDT%20etc%2C%20or%20community%20tools%20like%20OSDcloud%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20my%20experience%20most%20people%20I%20met%20are%20upset%20about%20the%20SAC%20because%20they%20still%20do%20manual%20images%2C%20sysprep%20and%20all%20the%20stuff%20as%20they%20did%20ever%20since.%3C%2FP%3E%3CP%3EAnd%20for%20SAC%20that's%20a%20lot%20of%20(uneccesary)%20work.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281792%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281792%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F972137%22%20target%3D%22_blank%22%3E%40Tammy104%3C%2FA%3E%26nbsp%3B%20Thanks%2C%20I%20guess%20that%20didn't%20click.%20Might%20be%20an%20issue%20and%20I%20guess%20I'll%20find%20out%20in%20the%20next%20few%20months%20when%20I%20log%20in%20and%20check%20for%20a%20download.%20It%20would%20be%20sad%20to%20see%20this%20option%20go%20because%20there%20are%20a%20lot%20of%20places%20that%20aren't%20connected%20to%20internet%2C%20etc.%2C%20which%20is%20exactly%20why%20they%20%22designed%22%20the%20LTSC%20releases.%20We%20work%20on%20a%20hardware%20cycle%20every%205-ish%20years%2C%20so%20the%20new%20term%20isn't%20a%20big%20deal%20to%20me.%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%2F289393%22%20target%3D%22_blank%22%3E%40K_Wester-Ebbinghaus%3C%2FA%3E%26nbsp%3B%20Thanks%2C%20I%20have%20thought%20about%20those%20things%2C%20but%20time%20is%20not%20on%20my%20side.%20And%20so%20much%20junk%20to%20unclutter%20with%20Pro%20or%20even%20Enterprise%20that%20LTSC%20doesn't%20include.%20But%20sometime%20I%20need%20to%20get%20with%20the%20current%20times%20and%20set%20up%20something%20like%20MDM.%20I%20would%20say%20SCCM%2C%20our%20college%20has%20this%20running%2C%20but%20the%20costs%20the%20last%20time%20I%20checked%20were%20far%20more%20than%20my%20little%20department%20can%20afford.%20I'm%20technically%20a%20separate%20everything%20from%20the%20college%2C%20the%20only%20thing%20I%20share%20is%20the%20internet%20connection%20(behind%20my%20own%20firewall).%20I'm%20running%20pretty%20vanilla%20Server%202019%20with%20the%20typical%20AD%20features%2C%20plus%20WDS%20for%20deployment.%20Also%20a%20few%20Freenas%2FTruenas%20servers%20for%20SMB%20shares%20for%20student%20work%20(video%20and%20audio%20projects)%2C%20plus%20a%20couple%20other%20Windows%20servers%20for%20a%20NEWS%20scripting%20application%20that%20may%20be%20going%20away.%20About%2060%20workstations%20at%20this%20time%2C%20so%20pretty%20small%20in%20the%20grand%20scheme%20of%20things.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20again%2C%20thanks%20to%20both%20of%20you%20for%20the%20info.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2286767%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2286767%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1033918%22%20target%3D%22_blank%22%3E%40Greg_E999%3C%2FA%3E%26nbsp%3BI%20agree%20SCCM%20more%20precisely%20Config%20Manager%20is%20a%20big%20solution%20for%20your%20scenario%2C%20if%20you%20have%20Microsoft%20E5%20licenses%20it%20is%20included%20though%20incl%20the%20needed%20SQL%20license.%20What%20you%20could%20do%20is%20to%20combine%20WDS%20to%20deploy%20vanilla%20images%20%2Cthen%20using%20AD%20Security%20groups%20and%20GPOs%20to%20assign%20who%20gets%20which%20stuff%3C%2FP%3E%3CP%3EThis%20could%20be%20tools%20like%20WinPKG%20or%20winget%2C%20even%20software%20distribution%20policies%20via%20GPOs%20are%20suitable%20and%20all%20of%20them%20are%20free%2C%20or%20things%20like%20PatchmyPC.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CBR%20%2F%3E%22time%20is%20not%20on%20my%20side%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3Ethere%20is%20some%20work%20needed%20but%20you%20do%20this%20one%20time%20and%20won't%20have%20to%20care%20much%20about%20new%20OS%20releases%20anymore%20it%20will%20save%20you%20a%20lot%20of%20time.%20reinstalling%20will%20be%20a%20breeze.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%22%3CSPAN%3EAnd%20so%20much%20junk%20to%20unclutter%20with%20Pro%20or%20even%20Enterprise%20that%20LTSC%20doesn't%20include%22%3C%2FSPAN%3E%3CBR%20%2F%3EAs%20for%20the%20junk%20it%20easy%20to%20get%20the%20best%20out%20of%20pro%20using%20WIMwitch%20to%20update%2C%20customize%20and%20cleanup%20your%20images.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298117%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298117%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20still%20confused.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%26nbsp%3BOS%20Name%20%3A%26nbsp%3B%20Microsoft%20Windows%2010%20Enterprise%20LTSC%2C%26nbsp%3BVersion%2010.0.17763%20Build%2017763%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EWhat%20is%20the%20EOL%26nbsp%3B%20for%20this%20version.%20is%20it%20may%2011%20%3F%26nbsp%3B%3C%2FP%3E%3CP%3Eif%20yes%20%2C%20which%20document%20should%20i%20refer%2C%20it%20is%20so%20messed%20up%20%2C%20MS%20not%20documenting%20things%20properly.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298120%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298120%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F955591%22%20target%3D%22_blank%22%3E%40ManjunBN%3C%2FA%3E%26nbsp%3BWindows%2010%20Enterprise%20LTSC%201809%20(2019)%20will%20be%20EOL%20on%20Jan.%209%2C%202029%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Flifecycle%2Fproducts%2Fwindows-10-2019-ltsc%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%2010%202019%20LTSC%20-%20Microsoft%20Lifecycle%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298204%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298204%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20Joe%2C%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2299704%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2299704%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F955591%22%20target%3D%22_blank%22%3E%40ManjunBN%3C%2FA%3E%26nbsp%3Byou%20can%20also%20refer%20to%20the%20Windows%20Update%20history%20pages%20and%20there%20choosing%20Windows%20Release%20information%3C%2FP%3E%3CP%3E(mind%20older%20OS%20pages%20in%20the%20update%20history%20contain%20broken%20links%20of%20Windows%2010%20release%20history)%26nbsp%3B%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%2F70570%22%20target%3D%22_blank%22%3E%40Joe%20Lurie%3C%2FA%3E%26nbsp%3Bdo%20you%20know%20anyone%20who's%20working%20on%20the%20update%20history%20pages%3F%20I%20have%20asked%20Aria%20Carley%20many%20weeks%20ago%20and%20she%20passed%20it%20on%2C%20but%20it%20wasn't%20fixed.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fwindows%2Frelease-health%2Frelease-information%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fwindows%2Frelease-health%2Frelease-information%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-2335763%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2335763%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20not%20seen%20any%20issues%20with%20doing%20in-place%20upgrades%20of%20LTSB%20to%20LTSC.%20In%20fact%20it's%20super%20easy%20to%20upgrade%20those%20versions%20since%20you%20do%20not%20have%20to%20worry%20about%20all%20the%20other%20superfluous%2C%20non-OS%20essential%20things%20that%20are%20in%20the%20normal%20Win10%20versions.%3C%2FP%3E%3CP%3EAlso%2C%20lol%20to%20anyone%20who%20has%20to%20support%20embedded%20machines%20and%20now%20have%20to%20deal%20with%20an%20out-of-support%20OS%20within%205%20years%2C%20hell%20there%20were%20still%20embedded%20things%20running%20WinXp%20not%20more%20than%20a%20few%20years%20ago.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2352540%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2352540%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20should%20stick%20to%20the%20model%20of%20LTSC%20being%2010%20years%2C%20it%20works%20well%20in%20edu%20where%20we%20don't%20want%20the%20store%20and%20to%20be%20honest%20we%20won't%20run%20them%20for%2010%20years%2C%20but%20it's%20reassuring%20to%20know%20that%20an%20old%20machine%20tucked%20away%20is%20still%20going%20to%20get%20security%20updates%20and%20when%20there%20are%20over%203000%20machines%20to%20update%2C%20that%20have%20to%20fit%20around%20a%20curriculum%20with%20a%20finite%20team%20of%20staff%20and%20about%20200%20million%20other%20objectives%20to%20sort%2C%20this%205%20year%20thing%20is%20just%20disappointing%2C%207%20perhaps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMight%20as%20well%20call%20it%20Medium%20Term%20Service%20Channel%20now...%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMakes%20me%20want%20to%20go%20MacOs%20ugh..%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2354714%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2354714%22%20slang%3D%22en-US%22%3E%3CP%3EZer0%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hear%20you%20on%20all%20points.%20But%20be%20careful%20wishing%20for%20Mac%20OS%2C%20they%20are%20now%20pushing%20updates%20without%20any%20input%20from%20the%20admins.%20Our%20Art%2FPhoto%20departments%20are%20Mac%20and%20it%20is%20a%20problem%20for%20the%20person%20who%20cares%20for%20those%20machines.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELTSC%20has%20been%20a%20huge%20labor%20saver%20for%20me%2C%20and%20I%20truly%20hope%20they%20will%20reconsider%20only%20distributing%20through%205%20vendors%20and%20let%20us%20go%20back%20to%20downloading%20it%20from%20our%20accounts%20like%20the%20other%20operating%20systems.%20Education%20is%20another%20perfect%20example%20of%20why%20this%20distribution%20should%20exist%2C%20we%20need%20stability%2C%20and%20releasing%20feature%20updates%20in%20the%20middle%20of%20the%20semesters%20is%20not%20very%20nice.%20And%20not%20all%20of%20us%20can%20afford%20(cost%20or%20time)%20to%20run%20SCCM%20(or%20whatever%20they%20are%20calling%20it%20now).%20I%20may%20need%20to%20go%20back%20and%20use%20a%20WSUS%20server%20so%20I%20might%20have%20a%20little%20control%2C%20but%20that%20means%20more%20time%20to%20go%20in%20and%20approve%20updates%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20said%2C%20I'm%20going%20to%20have%20to%20go%20through%20and%20build%20images%20of%20Enterprise%20for%20my%20computers%20and%20hope%20that%20a%20change%20happens%20and%20I%20can%20roll%20out%20the%20newer%20LTSC%20instead.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2366451%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2366451%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20see%20any%20problem%20with%20use%20of%20LTSC%20Windows%2010%20for%20home%20or%20office%20use.%20In%20fact%2C%20many%20people%20still%20use%20Windows%207%20with%20the%20only%20problem%20(besides%20of%20possible%20security%20issues)%20that%20web%20browsers%20won't%20update%20anymore%20over%20this%20platform.%3C%2FP%3E%3CP%3EBut%20I%20love%20the%20steadiness%20and%20quietness%20of%20windows%20LTSC%2C%20only%20security%20fixes%20but%20not%20huge%20updates%20that%20bothers%20people's%20life.%3C%2FP%3E%3CP%3EI%20personally%20don't%20like%20to%20have%20games%20like%20Candy%20crush%2C%20Xbox%20services!%2C%20Cortana%20and%20all%20these%20stuff%20that%20ruins%20desktop%20experience%2C%20so%20I'm%20very%20happy%20with%20LTSC%20windows.%3C%2FP%3E%3CP%3EPlease%20never%20abandon%20this!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2148535%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2148535%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20reason%20in%20my%20opinion%20is%20simple.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E10%20years%20are%20too%20long%20in%20terms%20of%20security%20changes.%20Li%3CSPAN%3Eke%20TLS%20support%20etc.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20I%20would%20encourage%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70570%22%20target%3D%22_blank%22%3E%40Joe%20Lurie%3C%2FA%3E%26nbsp%3Band%20the%20team%20to%20make%20it%20easier%20to%20get%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExtended%20support%20is%20very%20unattractive%20by%20design.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20LTSC%20gets%20now%205%20years%20is%20it%20split%20into%20half%20so%202.5%20y%20main%20support%20%2B%202.5%20y%20extended%20support%20or%20as%20a%20Novum%20only%205%20y%20Main%20support%20and%20no%20paid%20extended%20support%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20anyone%20needs%20Office%20on%20Windows%2010%202022%20LTSC%20I%20would%20plea%20to%20wait%20for%20Office%202022%20Release%20aswell.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2149018%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2149018%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20very%20disappointing.%20For%20those%20that%20deal%20with%20regulated%20and%20specialty%20equipment%20you%20understand%20that%20our%20vendors%20do%20not%20adapt%20that%20quickly%20and%20we%20the%20customers%20are%20left%20to%20deal%20with%20EOL%20OS'.%20If%20Microsoft%20is%20going%20down%20this%20road%20to%20shorten%20the%20life%20from%2010%20to%205%20years%20they%20really%20need%20to%20do%20a%20better%20job%20partnering%20with%20the%20suppliers%20that%20provide%20equipment%20controlled%20by%20Windows.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2149078%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2149078%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20the%20end%20it%20doesn't%20matter%20whether%20five%20years%20or%20ten%20years.%20We%20have%20a%20tape%20robot%20by%20Sun%20in%20our%20data%20center.%20(Anybody%20here%20who%20remembers%20who%20and%20what%20was%20Sun%3F)%20This%20tape%20robot%20runs%20very%20well%2C%20so%20why%20should%20we%20replace%20it.%20It%20runs%20with%20Windows%202000.%20In%20our%20workshops%20we%20have%20have%20some%20CNC-machines%20what%20runs%20with%20Windows%20NT%204.0.%20Using%20an%20operating%20system%20that%20runs%20out%20of%20support%20by%20the%20origin%20publisher%20is%20never%20a%20good%20idea%20for%20such%20devices.%20On%20the%20other%20hand%20we%20use%20Windows%2010%20LTSC%20for%20control%20our%20particle%20accelerators.%20The%20control%20machines%20are%20standard%20workstations%20and%20the%20hardware%20must%20be%20replaced%20every%20five%20years.%20So%20I%20know%20some%20old-fashioned%20people%20at%20our%20institute%20who%20would%20like%20to%20stay%20on%20Windows%20XP%20forever%20will%20be%20disappointed.%20But%20in%20the%20end%20the%20change%20it%20will%20not%20really%20make%20i%20difference%20for%20us.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2149093%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2149093%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F285725%22%20target%3D%22_blank%22%3E%40ajc196%3C%2FA%3E%26nbsp%3B%40We%20understand%20the%20need%20for%20legitimate%20use%20cases%20and%20wholeheartedly%20support%20you.%20We%20recommend%20you%20look%20at%20Windows%2010%20IoT%20Enterprise%20LTSC%20for%20those%20cases.%20And%20the%20current%20versions%20of%20LTSC%20are%20keeping%20their%2010%20yr%20lifecycle%20so%20this%20announcement%20shouldn%E2%80%99t%20impact%20your%20existing%20devices.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2149097%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2149097%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F289393%22%20target%3D%22_blank%22%3E%40K_Wester-Ebbinghaus%3C%2FA%3E%26nbsp%3B%20We%20aren%E2%80%99t%20splitting%20support%20into%202-1%2F2%20%2B%202-1%2F2.%20It%E2%80%99s%20simply%205%20yrs%20support.%20With%20LTSC%20not%20receiving%20new%20features%20throughout%20its%20life%2C%20there%E2%80%99s%20virtually%20no%20difference%20between%20normal%20support%20and%20extended%20support.%20Windows%2010%20Enterprise%20LTSC%20will%20have%205%20yrs%20support%20starting%20with%20the%20next%20release.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2150043%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2150043%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70570%22%20target%3D%22_blank%22%3E%40Joe%20Lurie%3C%2FA%3E%26nbsp%3BI%20understand%20the%20points%20you've%20made%2C%20but%20I'm%20confused%20on%20the%20ultimate%20reasoning%20behind%20knocking%20down%20the%20support%20lifetime.%20I%20swear%20I'm%20not%20trying%20to%20argue%20just%20to%20argue%2C%20I%20want%20to%20understand%20Microsoft's%20logic%20is%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELook%20at%20it%20this%20way%20with%20an%20upcoming%20example%20--%20Microsoft%20has%20to%20develop%20%26amp%3B%20support%20security%20updates%20for%2010%20years%20for%20Windows%2010%20IoT%20Enterprise%20LTSC%202021.%26nbsp%3B%20It%20should%20be%20a%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fiot-core%2Fwindows-iot-enterprise%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ebinary%20equivalent%3C%2FA%3E%20to%20Windows%2010%20Enterprise%20LTSC%202021.%26nbsp%3B%20But%20the%20former%20has%2010%20years%20of%20support%2C%20the%20latter%20gets%205%20years.%20Why%3F%20I%20don't%20see%20Microsoft%20isn't%20saving%20effort%2Ftime%20on%20development%20since%20security%20updates%20have%20to%20be%20developed%20for%2010%20years%20for%20IoT%20anyway.%26nbsp%3B%20So%20this%20halving%20of%20support%20seems%20unfair%20and%20arbitrary%2C%20even%20more%20so%20when%20this%20very%20article%20implies%20that%20customers%20misusing%20LTSC%20is%20the%20entire%20reasoning%20behind%20the%20decision%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EThrough%20in-depth%20conversations%20with%20customers%2C%20we%20have%20found%20that%20many%20who%20previously%20installed%20an%20LTSC%20version%20for%20information%20worker%20desktops%20have%20found%20that%20they%20do%20not%20require%20the%20full%2010-year%20lifecycle.%20With%20the%20fast%20and%20increasing%20pace%20of%20technological%20change%2C%20it%20is%20a%20challenge%20to%20get%20the%20up-to-date%20experience%20customers%20expect%20when%20using%20a%20decade-old%20product.%20Where%20scenarios%20do%20require%2010%20years%20of%20support%2C%20we%20have%20found%20in%20our%20conversations%20that%20these%20needs%20are%20often%20better%20solved%20with%20Windows%2010%20IoT%20Enterprise%20LTSC.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2150250%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2150250%22%20slang%3D%22en-US%22%3E%3CHR%20%2F%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3Edon't%20see%20Microsoft%20isn't%20saving%20effort%2Ftime%20on%20development%20since%20security%20updates%20have%20to%20be%20developed%20for%2010%20years%20for%20IoT%20anyway.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F285725%22%20target%3D%22_blank%22%3E%40ajc196%3C%2FA%3E%26nbsp%3BI%20never%20dealt%20with%20Windows%20IoT.%20Are%20you%20sure%20that%20the%20CUs%20are%20same%20for%20LTSC%20and%20IoT%20as%20they%20are%20for%201903%20and%201909%20or%202004%20%26amp%3B%2020H2%20%26amp%3B%2021H1%2C%20except%20a%20metadata%20in%20the%20update%20catalog%3F%3CBR%20%2F%3E%3CSPAN%3E%3CBR%20%2F%3EImho%20LTSC%20is%20like%20a%20fork%20from%20the%20usual%20Windows%2010%20SAC.%20comparable%20of%20Office%202016%2F2019%2F2022%20vs%20Microsoft%20365%20Apps%20for%20Business%20%2F%20Microsoft%20365%20for%20family.%20Otherwise%20I%20would%20be%20too%20surprised%20that%20every%20time%20a%20SAC%20H2%20release%20is%20on%20the%20way%20we%20also%20get%20a%20LTSC%20in%20time%20on%20a%203%20y%20schedule.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2150545%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2150545%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F285725%22%20target%3D%22_blank%22%3E%40ajc196%3C%2FA%3E%26nbsp%3BReally%2C%20like%20we%20state%20above%2C%20we%20know%20there%20are%20legitimate%20use%20cases%20for%20LTSC%20and%20we%20offer%20IoT%20for%20those%20cases.%20Our%20support%20lifecycle%20decisions%20are%20based%20on%20direct%20and%20in-depth%20feedback%20from%20our%20customers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2150628%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2150628%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70570%22%20target%3D%22_blank%22%3E%40Joe%20Lurie%3C%2FA%3E%26nbsp%3Bwill%20licensing%20become%20more%20flexible%20for%20the%20win10%20%26nbsp%3Biot%20enterprise%20version%3F%20Today%20that%20specific%20flavor%20is%20only%20sold%20to%20a%20few%20select%20resellers.%20I%20manage%20specialty%20devices%20for%20an%20enterprise.%20We%20utilize%20our%20ms%20agreement%20for%20licensing%20and%20provide%20our%20own%20hardware%20to%20configure%20with%20our%20equipment%3A%20for%20about%2075-80%25%20of%20the%20environment.%20For%20the%20other%2020%25%20where%20we%20are%20getting%20the%20PC%2Fos%20from%20the%20supplier%20with%20the%20equipment%2C%20the%20suppliers%20do%20not%20care%20about%20our%20desire%20to%20patch%20and%20secure%20our%20systems%20so%20they%20do%20not%20take%20the%20time%20to%20get%20the%20LTSC%20flavor.%20It%20is%20not%20easy%20for%20them%20to%20understand%20the%20model%20and%20they%20do%20not%20want%20to%20be%20forced%20to%20work%20with%20the%20Microsoft%E2%80%99s%20selected%206%20vendors%20to%20get%20the%20right%20version.%26nbsp%3B%3CBR%20%2F%3EI%20understand%20the%20desire%20to%20limit%20enterprises%20from%20deploying%20LTSC%20to%20the%20office%20environment%20but%20Microsoft%20does%20a%20poor%20job%20of%20understanding%20the%20specialty%20uses%20for%20windows.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2152508%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2152508%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F972137%22%20target%3D%22_blank%22%3E%40Tammy104%3C%2FA%3E%26nbsp%3BYou've%20hit%20the%20nail%20on%20the%20head%20of%20why%20I'm%20being%20critical%20of%20this%20decision.%26nbsp%3B%20Right%20now%20our%20volume%20agreement%20allows%20the%20use%20of%20Enterprise%20LTSC%3B%20It's%20a%20line%20item%20on%20our%20annual%20contract%20along%20with%20other%20things%20like%20Windows%20Server%20licensing%2C%20M365%20A3%2FA5%20licenses%2C%20etc.%26nbsp%3B%20As%20far%20as%20I%20can%20tell%2C%20IoT%20Enterprise%20(both%20LTSC%20and%20SAC)%20is%20unavailable%20to%20us%20--%20it's%20not%20on%20our%20contract%2C%20and%20not%20in%20VLSC.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERight%20now%20we%20have%20Enterprise%20LTSC%20running%20digital%20signage%2C%20self-service%20kiosks%2C%20machines%20that%20control%20mass%20spectrometers%20and%20NMR%20in%20labs%2C%20and%20various%20medical%20devices%20in%20our%20health%20center.%26nbsp%3B%20All%20places%20where%20vendors%20don't%20provide%20the%20OS%2Fhardware%2C%20but%20Enterprise%20LTSC%20is%20perfectly%20acceptable%20and%20necessary%20because%20of%20the%20predictability%20that%20an%20OS%20provides%20when%20not%20constantly%20being%20serviced%20with%20feature%20updates.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20IoT%20Enterprise%20LTSC%20is%20going%20to%20become%20more%20readily%20available%20to%20those%20who%20already%20have%20rights%20to%20Enterprise%20LTSC%2C%20I'll%20gladly%20go%20use%20IoT%20Enterprise%20LTSC%20and%20carry%20on%20with%20life.%20But%20until%20we%20have%20more%20info%20on%20such%20plans%20or%20lack%20thereof%2C%20%22just%20use%20IoT%22%20is%20easier%20said%20than%20done.%20(Which%20makes%20the%20answers%20here%20all%20the%20more%20patronizing%2C%20frankly)%20In%20the%20mean%20time%2C%20the%20net%20result%20for%20us%20as%20an%20organization%20is%20that%20%3CEM%3Efuture%3C%2FEM%3E%20Enterprise%20LTSC%20releases%20just%20got%20their%20support%20halved%20for%20no%20valid%20reason.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2155199%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2155199%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20I%20know%20how%20to%20license%20the%20LTSC%3F%3CBR%20%2F%3EWhich%20option%20is%20correct%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-----OPTION%201-----%3CBR%20%2F%3E1.%20Windows%2010%20Pro%20(Based%20License)%3C%2FP%3E%3CP%3E2.%20Windows%2010%20Enterprise%20LTSC%20(Upgrade)%3C%2FP%3E%3CP%3E-----OPTION%202-----%3C%2FP%3E%3CP%3E1.%20Windows%2010%20Pro%20(Based%20License)%3C%2FP%3E%3CP%3E2.%20Windows%2010%20Enterprise%20(Upgrade)%3C%2FP%3E%3CP%3E3.%20Windows%2010%20Enterprise%20LTSC%20(Upgrade)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2155594%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2155594%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70570%22%20target%3D%22_blank%22%3E%40Joe%20Lurie%3C%2FA%3E%2C%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EOur%20hardware%20vendor%20does%20not%20offer%20an%20AutoPilot%20LTSC%20IoT%20solution%2C%20so%20we%20would%20be%20extremely%20limited%20in%20what%20we%20can%20do%20with%20LTSC%20IoT.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20it%20is%20too%20costly%20to%20expect%20us%20to%20have%20to%20replace%20process%20control%20equipment%20every%205%20years.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWe%20will%20be%20skipping%20LTSC%202021%20since%20it%20will%20go%20out%20of%20support%20before%20LTSC%202019%20(1809)%20does.%20We%20hope%20Microsoft%20comes%20to%20their%20senses%20and%20reverses%20this%20decision%20in%20time%20for%20the%20next%20LTSC%20version.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2155847%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2155847%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F839301%22%20target%3D%22_blank%22%3E%40jd%3C%2FA%3E%26nbsp%3BWindows%2010%20Enterprise%20LTSC%20is%20licensed%20with%20Windows%20Enterprise%20licensing%20-%20sort%20of%20a%201a%20in%20your%20options%20above.%3C%2FP%3E%0A%3CP%3E1.%20Windows%2010%20Pro%3C%2FP%3E%0A%3CP%3E2.%20Windows%20E3%20Licensing%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20E3%20you%20get%20a%20whole%20slew%20of%20features%20-%20management%20and%20security%20-%20and%20the%20rights%20to%20install%20and%20run%20Windows%2010%20Enterprise%20LTSC.%20You%20can%20install%20Windows%2010%20Enterprise%20semi-annual%20channel%20on%20the%20devices%20in%20your%20infrastructure%20that%20the%20IW%20uses%2C%20and%20LTSC%20on%20the%20specialized%20devices%20all%20with%20the%20same%20license.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2155850%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2155850%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F295699%22%20target%3D%22_blank%22%3E%40AngryJohnny75%3C%2FA%3E%26nbsp%3BThanks%20for%20that%20feedback.%20Along%20with%20the%20other%20feedback%20we've%20received%20here%20I'll%20be%20brining%20this%20back%20to%20our%20product%20group.%20In%20your%20scenario%2C%20yes%2C%20staying%20on%20LTSC%202019%20is%20probably%20the%20best%20solution%20for%20you.%20However%2C%20since%20you%20were%20considering%20going%20from%20LTSC%202019%20(released%20in%202018)%20to%20LTSC%202021%2C%20then%20perhaps%20a%205-year%20lifecycle%20might%20work%20for%20those%20devices.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2155851%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2155851%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F839301%22%20target%3D%22_blank%22%3E%40jd%3C%2FA%3E%26nbsp%3BPlease%20DM%20me%20your%20contact%20info.%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%0A%3CP%3E--Joe.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2600948%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2600948%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20our%20isolated%20electric%20%26amp%3B%20gas%20control%20systems%2C%20we%20chose%20LTSC%202019%20and%20plan%20to%20stay%20on%20that%20for%20the%20full%2010%20year%20cycle%20for%20the%20foreseeable%20future.%26nbsp%3B%20Like%20other%20industrial%20control%20systems%2C%20the%20vendor%20support%20does%20not%20keep%20up%20with%20newer%20versions%20of%20Windows%20at%20the%20consumer%2Fend-user%20pace.%26nbsp%3B%20Streamlined%20stability%20in%20the%20platform%20is%20key%20to%20stability%20in%20operations.%26nbsp%3B%20Likewise%2C%20we%20only%20deploy%20security%20updates.%26nbsp%3B%20Office%202019%20(and%20likely%20Office%20LTSC)%20has%20been%20a%20problem%20for%20us%20to%20update%20since%20we%20have%20to%20sync%20WSUS%20from%20our%20external%20network%20to%20our%20internal%20SCCM%20instance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2601153%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2601153%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1118810%22%20target%3D%22_blank%22%3E%40G_D0g%3C%2FA%3E%26nbsp%3B%40I%20agree%20we%20will%20likely%20hold%20onto%20LTSC%202019%20longer%20than%20we%20had%20planned%20however%20at%20some%20point%20with%20new%20hardware%20we%20will%20have%20to%20use%20the%20newer%20release.%20I%20also%20deal%20with%20systems%20used%20to%20control%20specialized%20equipment%20%26nbsp%3Bso%20I%20get%20that%20the%20vendors%20are%20always%20behind%2C%20but%20we%20should%20be%20pushing%20them%20to%20align%20closer%20with%20Microsoft%20and%20their%20OS%20roadmap%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2604417%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2604417%22%20slang%3D%22en-US%22%3E%3CP%3ETammy%20and%20G_DOg%2C%20and%20those%20are%20both%20still%20listed%20as%20recommended%20use%20cases.%20I%20just%20got%20permission%20to%20reach%20out%20to%20our%20Microsoft%20rep%2C%20I'm%20going%20to%20be%20asking%20about%20LTSC%20very%20soon%20because%20even%20on%20a%205%20year%20support%20rotation%2C%20that's%20enough%20for%20many%20of%20us.%20I'm%20able%20to%20update%20as%20my%20software%20updates%20but%20vendors%20got%20burned%20years%20ago%20when%20the%20new%20audio%20subsystem%20was%20put%20in%20place.%20The%20release%20to%20manufacturing%20version%20was%20different%20(I%20think%20this%20was%20win7)%20and%20everyone%20built%20there%20code%20to%20work%20with%20preview%20and%20RTM%20versions...%20Then%20suddenly%20over%20night%20none%20of%20the%20software%20worked.%20Took%20the%20radio%20station%20automation%20and%20video%20editing%20companies%20that%20I%20use%206%20months%20to%20work%20out%20the%20changes.%20They%20no%20longer%20build%20against%20what%20might%20be%2C%20they%20only%20build%20against%20what%20is%20actually%20shipping%20which%20means%20about%20a%206%20month%20lag.%20LTSC%20allows%20us%20to%20remain%20somewhat%20current%2C%20yet%20maintain%20support%20for%20as%20long%20as%20needed.%20It's%20not%20like%20any%20of%20us%20change%20to%20the%20newest%20hardware%20every%206%20months%20where%20we%20need%20this%20newest%20hardware%20support.%20I'm%20lucky%20i%20plain%20old%20regular%20PC's%20get%20recycled%20every%205%20to%206%20years%2C%20we%20can't%20afford%20to%20go%20every%202%20years%20like%20some%20places%20that%20lease%20hardware.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20then%20there%20is%20the%20embedded%20systems%20like%20both%20of%20you%20mention%20that%20control...%20Well%20control%20all%20of%20modern%20life.%20I'd%20really%20like%20these%20to%20be%20stable%20and%20secure%2C%20and%20off%20the%20internet%20when%20possible.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2147232%22%20slang%3D%22en-US%22%3EThe%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2147232%22%20slang%3D%22en-US%22%3E%3CP%3EWindows%2010%20introduced%20Windows%20as%20a%20service%2C%20a%20method%20of%20continually%20providing%20new%20features%20and%20capabilities%20through%20regular%20feature%20updates.%20Semi-Annual%20Channel%20versions%20of%20Windows%2C%20such%20as%20version%201909%2C%20version%202004%2C%20and%20version%2020H2%2C%20are%20released%20twice%20per%20year.%3C%2FP%3E%3CP%3EIn%20addition%20to%20Semi-Annual%20Channel%20releases%20of%20Windows%2010%20Enterprise%2C%20we%20also%20developed%20a%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fwindows%2Fwhats-new%2Fltsc%2F%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3ELong%20Term%20Servicing%20Channel%3C%2FA%3E%20for%20Windows%2C%20known%20as%20Windows%2010%20Enterprise%20LTSC%2C%20and%20an%20Internet%20of%20Things%20(IoT)%20version%20known%20as%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fwindows%2Fiot-core%2Fwindows-iot-enterprise%23long-term-servicing-channel-ltsc%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3EWindows%2010%20IoT%20Enterprise%20LTSC%3C%2FA%3E.%20Each%20of%20these%20products%20was%20designed%20to%20have%20a%2010-year%20support%20lifecycle%2C%20as%20outlined%20in%20our%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Flifecycle%2Fproducts%2F%3Fproducts%3Dwindows%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3Elifecycle%20documentation%3C%2FA%3E.%3C%2FP%3EWhat%20are%20we%20announcing%20today%3F%3CP%3EToday%20we%20are%20announcing%20that%20the%20next%20version%20of%20Windows%2010%20Enterprise%20LTSC%20and%20Windows%2010%20IoT%20Enterprise%20LTSC%20will%20be%20released%20in%20the%20second%20half%20(H2)%20of%20calendar%20year%202021.%20Windows%2010%20Client%20LTSC%20will%20change%20to%20a%205-year%20lifecycle%2C%20aligning%20with%20the%20changes%20to%20the%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fmicrosoft-365%2Fblog%2F2021%2F02%2F18%2Fupcoming-commercial-preview-of-microsoft-office-ltsc%2F%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3Enext%20perpetual%20version%20of%20Office%3C%2FA%3E.%20This%20change%20addresses%20the%20needs%20of%20the%20same%20regulated%20and%20restricted%20scenarios%20and%20devices.%20Note%20that%20Windows%2010%20IoT%20Enterprise%20LTSC%20is%20maintaining%20the%2010-year%20support%20lifecycle%3B%20this%20change%20is%20only%20being%20announced%20for%20Office%20LTSC%20and%20Windows%2010%20Enterprise%20LTSC.%20You%20can%20read%20more%20about%20the%20Windows%2010%20IoT%20Enterprise%20LTSC%20announcement%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FWindows10IoTLTSC%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3EWindows%20IoT%20blog%3C%2FA%3E.%3C%2FP%3EFrequently%20asked%20questions%20(FAQ)%20Why%20are%20you%20making%20this%20change%20to%20Windows%2010%20Enterprise%20LTSC%3F%3CP%3EWindows%2010%20Enterprise%20LTSC%20is%20meant%20for%20specialty%20devices%20and%20scenarios%20that%20simply%20cannot%20accept%20changes%20or%20connect%20to%20the%20cloud%2C%20but%20still%20require%20a%20desktop%20experience%3A%20regulated%20devices%20that%20cannot%20accept%20feature%20updates%20for%20years%20at%20a%20time%2C%20process%20control%20devices%20on%20the%20manufacturing%20floor%20that%20never%20touch%20the%20internet%2C%20and%20specialty%20systems%20that%20must%20stay%20locked%20in%20time%20and%20require%20a%20long-term%20support%20channel.%3C%2FP%3E%3CP%3EThrough%20in-depth%20conversations%20with%20customers%2C%20we%20have%20found%20that%20many%20who%20previously%20installed%20an%20LTSC%20version%20for%20information%20worker%20desktops%20have%20found%20that%20they%20do%20not%20require%20the%20full%2010-year%20lifecycle.%20With%20the%20fast%20and%20increasing%20pace%20of%20technological%20change%2C%20it%20is%20a%20challenge%20to%20get%20the%20up-to-date%20experience%20customers%20expect%20when%20using%20a%20decade-old%20product.%20Where%20scenarios%20do%20require%2010%20years%20of%20support%2C%20we%20have%20found%20in%20our%20conversations%20that%20these%20needs%20are%20often%20better%20solved%20with%20Windows%2010%20IoT%20Enterprise%20LTSC.%3C%2FP%3E%3CP%3EThis%20change%20also%20aligns%20the%20Windows%2010%20Enterprise%20LTSC%20lifecycle%20with%20the%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fblog%2F2021%2F02%2F18%2Fupcoming-commercial-preview-of-microsoft-office-ltsc%2F%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3Erecently%20announced%20Office%20LTSC%20lifecycle%3C%2FA%3E%20for%20a%20more%20consistent%20customer%20experience%20and%20better%20planning.%3C%2FP%3EYou%20state%20that%20you%20are%20making%20this%20change%20to%20Windows%2010%20Enterprise%20LTSC%20to%20align%20with%20the%20changes%20to%20Office%20LTSC.%20Has%20your%20guidance%20changed%20on%20installing%20Office%20on%20Windows%2010%20Enterprise%20LTSC%3F%3CP%3EOur%20guidance%20has%20not%20changed%3A%20Windows%2010%20Enterprise%20LTSC%20is%20designed%20for%20specialty%20devices%2C%20and%20not%20information%20workers.%20However%2C%20if%20you%20find%20that%20you%20have%20a%20need%20for%20Windows%2010%20Enterprise%20LTSC%2C%20and%20you%20also%20need%20Office%20on%20that%20device%2C%20the%20right%20solution%20is%20Windows%2010%20Enterprise%20LTSC%20%2B%20Office%20LTSC.%20For%20consistency%20for%20those%20customers%2C%20we%20are%20aligning%20the%20lifecycle%20of%20the%20two%20products.%3C%2FP%3EWhat%20about%20the%20current%20versions%20of%20LTSC%20%E2%80%93%20Windows%2010%20Enterprise%20LTSC%202015%2F2016%2F2019%3F%3CP%3EWe%20are%20not%20changing%20the%20lifecycle%20of%20the%20LTSC%20versions%20that%20have%20been%20previously%20released.%20This%20change%20only%20impacts%20the%20next%20version%20of%20Windows%2010%20Enterprise%20LTSC%2C%20scheduled%20to%20be%20released%20in%20the%20second%20half%20of%20the%202021%20calendar%20year.%3C%2FP%3EWhat%20should%20I%20do%20if%20I%20need%20to%20install%20or%20upgrade%20to%20the%20next%20version%2C%20but%20I%20need%20the%2010-year%20lifecycle%20for%20my%20device%3F%3CP%3EWe%20recommend%20that%20you%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-it-pro-blog%2Fltsc-what-is-it-and-when-should-it-be-used%2Fba-p%2F293181%22%20target%3D%22_blank%22%3Ereassess%20your%20decision%20to%20use%20Windows%2010%20Enterprise%20LTSC%3C%2FA%3E%20and%20change%20to%20Semi-Annual%20Channel%20releases%20of%20Windows%20where%20it%20is%20more%20appropriate.%20For%20your%20fixed%20function%20devices%2C%20such%20as%20kiosk%20and%20point-of-sale%20devices%2C%20that%20need%20to%20continue%20using%20LTSC%20and%20are%20planning%20to%20install%20or%20upgrade%20to%20the%20next%20version%2C%20consider%20moving%20to%20Windows%2010%20IoT%20Enterprise%20LTSC.%20Again%2C%20we%20understand%20the%20needs%20for%20IoT%2Ffixed%20purpose%20scenarios%20are%20different%20and%20there%20is%20no%20change%20to%20the%2010-year%20support%20lifecycle%20for%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fwindows%2Fiot-core%2Fwindows-iot-enterprise%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3EWindows%2010%20IoT%20Enterprise%20LTSC%3C%2FA%3E.%20For%20information%20on%20how%20to%20obtain%20Windows%2010%20IoT%20Enterprise%20LTSC%2C%20please%20reach%20out%20to%20your%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fwindows%2Fiot-core%2Fwindows-iot-enterprise%23getting-started%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3Elocal%20IoT%20distributor%3C%2FA%3E.%3C%2FP%3EIs%20there%20a%20difference%20in%20the%20Windows%2010%20operating%20system%20between%20Windows%2010%20Enterprise%20LTSC%20and%20Windows%2010%20IoT%20Enterprise%20LTSC%3F%3CP%3EThe%20two%20operating%20systems%20are%20binary%20equivalents%20but%20are%20licensed%20differently.%20For%20information%20on%20licensing%20Windows%2010%20IoT%20Enterprise%20LTSC%2C%20please%20reach%20out%20to%20your%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fwindows%2Fiot-core%2Fwindows-iot-enterprise%23getting-started%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3Elocal%20IoT%20distributor%3C%2FA%3E.%3C%2FP%3EWhere%20can%20I%20find%20more%20information%20about%20Windows%2010%20IoT%20Enterprise%20LTSC%3F%3CP%3EYou%20can%20learn%20about%20the%20different%20Windows%20for%20IoT%20editions%2C%20and%20for%20which%20scenarios%20each%20edition%20is%20optimized%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fwindows%2Fiot-core%2F%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3EWindows%20for%20IoT%20documentation%3C%2FA%3E.%20You%E2%80%99ll%20also%20find%20tutorials%2C%20quick%20start%20guides%2C%20and%20other%20helpful%20information.%20Check%20it%20out%20today!%3C%2FP%3EWhen%20will%20Windows%2010%20IoT%20Enterprise%20LTSC%20announce%20their%20release%3F%3CP%3EWindows%2010%20IoT%20Enterprise%20LTSC%20will%20be%20released%20in%20the%20second%20half%20of%202021.%20You%20can%20read%20more%20about%20the%20Windows%2010%20IoT%20Enterprise%20LTSC%20announcement%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FWindows10IoTLTSC%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3EWindows%20IoT%20blog%3C%2FA%3E.%3C%2FP%3E%20%3CP%3E%3CBR%20%2F%3EContinue%20the%20conversation.%20Find%20best%20practices.%20Visit%20the%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fcommunity%2FWindows10%22%20rel%3D%22noopener%20noreferrer%22%20target%3D%22_blank%22%3EWindows%20Tech%20Community%3C%2FA%3E.%3C%2FP%3E%3CP%3EStay%20informed.%20For%20the%20latest%20updates%20on%20new%20releases%2C%20tools%2C%20and%20resources%2C%20stay%20tuned%20to%20this%20blog%20and%20follow%20us%20%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Fmswindowsitpro%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%40MSWindowsITPro%3C%2FA%3E%20on%20Twitter.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2147232%22%20slang%3D%22en-US%22%3E%3CP%3EFind%20out%20when%20the%20next%20LTSC%20release%20will%20be%20available%20plus%20when%20and%20how%20LTSC%20versions%20are%20best%20utilized%20in%20an%20organization.%3C%2FP%3E%3CP%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2147232%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-2155953%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2155953%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F285725%22%20target%3D%22_blank%22%3E%40ajc196%3C%2FA%3E%26nbsp%3BPlease%20DM%20me%20your%20contact%20info%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2156288%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2156288%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F295699%22%20target%3D%22_blank%22%3E%40AngryJohnny75%3C%2FA%3E%26nbsp%3Bwe%20will%20have%20issues%20with%20the%20fact%20that%20LTSC%202019%20only%20supports%20up%20to%2010th%20generation%20intel%2C%20right%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2172014%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2172014%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20to%20speak%20generally%20on%20this%20subject%20(not%20my%20area%20of%20responsibility)%20but%20there%20are%20many%20orgs%20that%20are%20under%20State%2Fgov%2FEU%20regulations%20when%20it%20comes%20to%20purchasing.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EToday%20it's%20easy%20because%20there%20is%20only%20one%20Microsoft%20to%20buy%20our%20Licenses%20from%20(including%20LTC).%3CBR%20%2F%3EIf%20we%20have%20to%20get%20them%20from%20an%20IOT%20vendor%20it%20will%20force%20many%20orgs%20to%20do%20purchasing%20rounds%20with%20increased%20costs%20as%20result.%3CBR%20%2F%3EWorse%20is%20the%20loss%20of%20flexibility.%20A%20License%20bought%20through%20Dell%20for%20example%20can't%20be%20moved%20to%20an%20HP.%20That%20will%20also%20increase%20license%20and%20operational%20costs.%3CBR%20%2F%3EThe%20use%20case%20here%20is%20a%20desktop%20used%20as%20kiosk%20machine%20and%20the%20need%20for%20the%20kiosk%20goes%20away%20-%20the%20desktop%20gets%20reimaged%20with%20standard%20enterprise%20making%20it%20org%20standard%20and%20freeing%20that%20ltsc%20license.%20The%20next%20day%20a%20new%20kiosk%20need%20arises%20in%20an%20office%20400%20miles%20away.%20Today%20you%20would%20take%20a%20spare%20usable%20desktop%20at%20that%20office%20and%20reimage%20it%20with%20the%20ltsc%20image%20and%20done.%20With%20IoT%20you%20now%20must%20have%20machines%20of%20both%20types%20(standard%20and%20IoT)%20in%20store%20and%20you%20as%20result%20again%20will%20have%20increased%20costs%20for%20logistics%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2172041%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2172041%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%3A%3CBR%20%2F%3E%3CBR%20%2F%3EWith%20a%2010%20year%20support%20cycle%20and%20a%20three%20year%20release%20cycle%20you%20can%20get%209%20years%20out%20of%20your%20LTSC%20build%20with%20a%20year%20for%20dev%20and%20deployment.%3C%2FP%3E%3CP%3EWith%20a%205%20year%20support%20and%203%20year%20release%2C%20you%20will%20have%20to%20reimage%20for%20every%20release%20once%20again%20increasing%20operational%20costs%20a%20lot%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2175732%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2175732%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F375670%22%20target%3D%22_blank%22%3E%40matsmcp%3C%2FA%3E%26nbsp%3Bdepends%20how%20you%20deploy.%20even%20in%20small%20businesses%20we%20achieved%20a%20near%20zero%20touch%20deployment%20using%20MDT%2C%20WinPKG%20and%20MSI%20based%20GPO%20installations%20with%20no%20golden%20images.%20If%20you%20need%20the%20profiles%20USMT%20is%20a%20thing%20or%20UE-V%20if%20you%20have%20SA.%20Is%20this%20is%20a%20way%20to%20go%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2175737%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2175737%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EA%20License%20bought%20through%20Dell%20for%20example%20can't%20be%20moved%20to%20an%20HP.%20That%20will%20also%20increase%20license%20and%20operational%20costs.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CSPAN%3Eplease%20revisit%20Terms%20Of%20Use%20of%20LTSC%201809%20and%20later.%20Windows%20Server%20OEM%20licenses%20can%20be%20transferred%20in%20EU%20(finally).%20So%20I%20would%20be%20shocked%20if%20they%20applied%20local%20legislation%20only%20into%20the%20ToS%20of%20Server%20LTSC%20and%20not%20Client%20LTSC.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2177359%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2177359%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F289393%22%20target%3D%22_blank%22%3E%40K_Wester-Ebbinghaus%3C%2FA%3E%26nbsp%3BI%20don't%20understand%20what%20you%20mean%20depends%20on%20how%20you%20deploy.%3CBR%20%2F%3EIt%20still%20means%20costs%20and%20downtime%20on%20that%20box%20regardless%20of%20how%20you%20do%20it.%20If%20you%20have%20to%20do%20it%20three%20times%20it%20costs%203X%20as%20much%20as%20doing%20it%20once%3CBR%20%2F%3E%3CBR%20%2F%3ESince%2010%20year%20support%20only%20will%20apply%20to%20IoT%20not%20to%20standard%20OEM%20you%20must%20get%20the%20IoT%20version%20and%20none%20of%20my%20vendors%20can%20supply%20it%20without%20selling%20it%20as%20a%20part%20of%20a%20HW%20-%20Can%20you%20buy%20it%20as%20a%20license%20only%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2771712%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2771712%22%20slang%3D%22en-US%22%3E%3CP%3EKeeping%20this%20up%20to%20date...%20I%20found%20some%20information%20that%20says%2021h2%20will%20be%20the%20next%2Flast%20Win10%20LTSC%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2021%2F07%2F15%2Fintroducing-the-next-feature-update-to-windows-10-21h2%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2021%2F07%2F15%2Fintroducing-the-next-feature-update-to-windows-10-21h2%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20date%20set%20but%20several%20sites%20are%20guessing%20October%202021%20release.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20as%20far%20as%20being%20able%20to%20get%20this%2C%20I%20truly%20hope%20that%20MS%20has%20changed%20direction%20and%20will%20just%20offer%20this%20as%20a%20download%20through%20the%20normal%20licensing%20portal.%20For%20those%20of%20you%20stuck%20in%20the%20past%20(like%20me)%20WDS%20is%20not%20going%20to%20be%20able%20to%20deploy%20Win11%20without%20some%20work%20in%20MDT%20to%20prepare%20the%20boot.wim%20image.%20And%20then%20you%20might%20as%20well%20keep%20using%20MDT%20to%20deploy%20the%20install%20images%20and%20applications%2C%20but%20I'm%20looking%20at%20127%20pages%20of%20document%20and%20probably%20hours%20of%20%22hands%20on%22%20to%20make%20sure%20I%20have%20a%20decent%20grasp%20before%20trying%20to%20deploy%20Win11.%20Not%20to%20mention%20that%20half%20of%20the%20media%20editing%20apps%20we%20use%20will%20not%20support%20Win11%20for%20several%20months%20(to%20a%20year).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20after%20playing%20with%20the%20Win10%2021h1%20Enterprise%20Eval%20in%20my%20virtual%20lab%2C%20uggg!%20Why%20can't%20we%20start%20with%20something%20like%20LTSC%2C%20then%20have%20a%20%22stuff%22%20installer%20to%20add%20all%20the%20other%20%22stuff%22%20if%20we%20want%20it.%20Take%20something%20that%20normally%20uses%20under%2010GB%20and%20make%20it%20just%20over%2020GB%20with%20all%20the%20extra%20%22stuff%22%20that%20we%20then%20need%20to%20try%20and%20remove.%20Grrr!%20This%20makes%20me%20appreciate%20the%20LTSC%20releases%20even%20more.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2771762%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2771762%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1033918%22%20target%3D%22_blank%22%3E%40Greg_E999%3C%2FA%3E%26nbsp%3Bre%3A%26nbsp%3B%3CSPAN%3ENo%20date%20set%20but%20several%20sites%20are%20guessing%20October%202021%20release...we%20say%20above%20that%20it%20will%20be%20the%202nd%20half%20of%20this%20calendar%20year.%20Correct%2C%20that%20we%20have%20not%20published%20a%20release%20date.%20But%20it%20will%20be%20the%20same%20day%20that%20Windows%2010%2C%20version%2021H2%20is%20released.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20haven't%20made%20any%20changes%20to%20how%20you%20get%20LTSC%20versions%20-%20if%20you%20are%20licensed%20for%20Enterprise%2C%20you%20can%20get%20it%20from%20the%20Volume%20Licensing%20Servicing%20Center%20(VLSC).%20The%20next%20LTSC%20is%20for%20certain%20going%20to%20be%20Windows%2010%2C%20so%20not%20sure%20what%20you%20are%20asking%20with%20the%20Windows%2011%20part%20of%20your%20comment.%20If%20you%20want%20Windows%2011%2C%20that%20will%20be%20released%20on%20Oct.%205%2C%202021%2C%20and%20will%20be%20available%20to%20be%20deployed%20via%20all%20normal%20channels%3A%20WSUS%2C%20ConfigMgr%2C%20Windows%20Update%20for%20Business%2C%20MDT%2C%20etc...%20view%20our%20Windows%2011%20docs%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwhats-new%2Fwindows-11%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%2011%20overview%20-%20What's%20new%20in%20Windows%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2771784%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2771784%22%20slang%3D%22en-US%22%3E%3CP%3EJoe%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20mentioned%20the%20download%20because%20way%20up%20in%20the%20above%20article%2C%20it%20mentions%20that%20LTSC%20will%20only%20be%20available%20from%20selected%20partners%2C%20reading%20that%20it%20will%20be%20available%20from%20our%20normal%20download%20options%20is%20frankly%20great%20news!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Win11%20stuff%20with%20MDT%20is%20just%20something%20%22new%22%20to%20me%20(not%20really%20new%20to%20most%20admins).%20I%20haven't%20studied%20up%20on%20MDT%20even%20though%20I%20should%20have%20been%20using%20it%20for%20years.%20One%20of%20those%20conditions%20that%20happens%20when%20you%20%22wear%20too%20many%20hats%22%20and%20never%20have%20time%20to%20stay%20up%20to%20date%20on%20things.%20Thankfully%20I%20finally%20have%20an%20XCP-NG%20system%20set%20up%20for%20a%20lab%20to%20test%20with%20and%20I'll%20get%20started%20on%20this%20as%20time%20allows.%20Either%20that%20or%20I'll%20scrap%20WDS%2FMDT%20for%20something%20like%20a%20FOG%20server.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2771800%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2771800%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1033918%22%20target%3D%22_blank%22%3E%40Greg_E999%3C%2FA%3E%26nbsp%3BOnly%20IoT%20LTSC%20requires%20certain%20partners%20to%20obtain.%20But%20for%20windows%2010%20Enterprise%20LTSC%202021%2C%20you'll%20be%20able%20to%20download%20it%20from%20VLSC.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2771866%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2771866%22%20slang%3D%22en-US%22%3E%3CP%3EGreg%2C%3C%2FP%3E%3CP%3EThe%20change%20that%20was%20announced%20is%20that%20the%20new%20release%20of%20LTSC%20we%20get%20through%20EA%20will%20now%20have%20a%205%20year%20life%20not%2010.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3Efor%20people%20like%20me%20who%20use%20specialized%20devices%20in%20an%20enterprise%20environment%20that%20means%20we%20are%20forced%20to%20work%20with%20one%20of%205%20IOT%20providers%20to%20figure%20out%20how%20to%20get%20the%2010%20year%20iot%20version.%20Microsoft%20is%20disconnected%20from%20the%20smaller%20niche%20use%20cases%20because%20we%20don%E2%80%99t%20make%20up%20enough%20of%20their%20business%20to%20care%20about%20impact.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2211209%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2211209%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CSPAN%3Eplease%20revisit%20Terms%20Of%20Use%20of%20LTSC%201809%20and%20later.%20Windows%20Server%20OEM%20licenses%20can%20be%20transferred%20in%20EU%20(finally).%20So%20I%20would%20be%20shocked%20if%20they%20applied%20local%20legislation%20only%20into%20the%20ToS%20of%20Server%20LTSC%20and%20not%20Client%20LTSC.%3C%2FSPAN%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EThese%20terms%20of%20use%20for%20Windows%2010%20LTSC%201809%20are%20likely%20not%20applicable%20to%20Windows%2010%20LTSC%20%3CSTRONG%3EIoT%3C%2FSTRONG%3E%20going%20forward.%20The%20concern%20here%20is%20how%20do%20we%20maintain%2010%20year%20support%20by%20obtaining%20LTSC%20IoT%20licenses%20that%20can%20be%20transferred%20between%20hardware%20manufacturers.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2807612%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2807612%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20why%20have%20a%20channel%20called%20the%20%22Long%20Term%20Servicing%20Channel%22%20if%20you%20won't%20be%20%22servicing%22%20it%20%22long%20term%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can't%20think%20that%20it%20would%20cost%20all%20that%20much%20to%20keep%20LTSC%20updated%20considering%20there's%20no%20feature%20improvements%20and%20you're%20supporting%20a%20bunch%20of%20similar%20branches%20anyway.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20only%20assume%20this%20is%20a%20jab%20at%20people%20using%20LTSC%20%22incorrectly%22%20but%20also%20defeats%20the%20whole%20point%20of%20the%20existence%20of%20the%20Channel.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20if%20there's%20anyone%20at%20Microsoft%20listening%2C%20please%20consider%20revising%20this%20decision.%20This%20doesn't%20help%20anyone%20but%20is%20worse%20for%20the%20people%20using%20LTSC%20correctly%20than%20the%20few%20not.%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2808981%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2808981%22%20slang%3D%22en-US%22%3E%3CP%3EAdamC%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20not%20try%20and%20defend%20MS%2C%20but%20the%20only%20reason%20I%20can%20think%20of%20for%20the%20shorter%20term%20of%20this%20LTSC%20release%20is%20that%20Windows%2011%20is%20here%20and%20they%20don't%20want%20to%20deal%20with%20a%20long%20term%20OS%20past%20the%20new%205%20year%20period.%20Just%20my%20guess.%20They%20have%20committed%20to%20an%20LTSC%20for%20win11%20and%20maybe%20that%20will%20have%20longer%20terms%20again%20(but%20probably%20not).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20far%20as%20using%20it%20incorrectly...%20This%20should%20be%20an%20option%20for%20anyone%20that%20has%20a%20license%20to%20Pro%20(or%20similar%20level).%20There%20are%20a%20bunch%20of%20business%2Fprofessional%20use%20cases%20that%20don't%20require%20or%20desire%20a%20lot%20of%20the%20stuff%20put%20into%20Pro.%20The%20entire%20motion%20picture%20industry%20is%20one%20very%20clear%20example%2C%20a%20large%20number%20of%20those%20machines%20are%20truly%20walled%20off%20from%20the%20rest%20of%20the%20world%20to%20try%20and%20prevent%20movies%20leaking%20out%20into%20%22the%20wild%22.%20Decades%20ago%20%22The%20Hulk%22%20leaked%20on%20the%20web%20without%20the%20special%20effects%2C%20this%20being%20one%20concrete%20example%20I%20can%20cite.%20Obviously%20having%20a%20person%20inside%20to%20sneaker%20net%20the%20contraband%20out%20is%20something%20that%20no%20OS%20can%20prevent%2C%20but%20with%20the%20number%20of%20%22electronic%20break-ins%22%20on%20the%20rise%2C%20having%20a%20true%20air%20gap%20is%20required.%20Netflix%20might%20specify%20this%20in%20their%20workflow%20document%2C%20if%20you%20are%20getting%20funding%20from%20Netflix%2C%20you%20need%20to%20conform%20to%20their%20workflow%2C%20from%20cameras%20to%20file%20handling%20practices.%20I%20think%20a%20web%20search%20will%20find%20those%20documents%20for%20anyone%20wanting%20to%20look%2C%20they%20definitely%20have%20a%20list%20of%20approved%20cameras.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20movie%20companies%20also%20don't%20need%20all%20the%20wiz%20bang%20consumer%20oriented%20stuff%2C%20they%20come%20in%2C%20get%20to%20work%2C%20and%20if%20they%20are%20lucky%20go%20home%20at%20the%20end%20of%20the%20day.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Long%20Term%20channel%20should%20be%20available%20to%20%22normal%22%20users%2C%20might%20cut%20down%20on%20all%20the%20debloat%20script%20stuff%20floating%20around%20the%20web%20that%20you%20never%20know%20if%20you%20can%20really%20trust!%20If%20you%20can't%20code%20the%20script%20yourself%2C%20you%20have%20no%20way%20of%20knowing%20if%20it%20contains%20a%20%22surprise%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2256948%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2256948%22%20slang%3D%22en-US%22%3E%3CDIV%3EMicrosoft%20still%20doesn't%20get%20it.%20After%20reading%20the%20comments%20above%2C%20the%20admins%20who%20are%20angry%20about%20LTSC%20dropping%20to%205%20years%20have%20a%20point.%20LTSC%20%3CEM%3Eshould%3C%2FEM%3E%20be%2010%20years%2C%20standard%20Enterprise%20%3CEM%3Eshould%3C%2FEM%3E%20be%205%20years.%20The%20push%20back%20you%20are%20getting%20from%20standard%20desktops%20is%20that%20admins%20don't%20want%20twice%20yearly%20upgrades.%26nbsp%3B%20How%20about%20this%3A%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EWindows%2010%20Home%20and%20Pro%3A%26nbsp%3B%20Semi-Annual%20Channel%3C%2FDIV%3E%3CDIV%3EWindows%2010%20Enterprise%3A%26nbsp%3B%205%20years%3C%2FDIV%3E%3CDIV%3EWindows%2010%20Enterprise%20LTSC%2FIoT%3A%26nbsp%3B%2010%20years%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2810821%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2810821%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20all%20for%20your%20comments.%26nbsp%3B%20%26nbsp%3BI%20can%20assure%20you%20that%20the%20change%20in%20policy%20is%20not%20meant%20as%20a%20%22jab%22%20to%20anyone%20but%20rather%20to%20align%20with%20our%20overall%20lifecycle%20policies%20with%20Office%20-%26nbsp%3B%20we%20do%20see%20instances%20where%20customers%20use%20LTSC%20for%20everyday%2C%20%22knowledge%20worker%22%20scenarios%20and%20for%20that%2C%20we%20have%20alignment%20of%20five%20years%20with%20the%20Office%20LTSC%20release.%26nbsp%3B%20%26nbsp%3BFor%20use%20cases%20which%20require%20longer%20servicing%20without%20any%20new%20feature%20updates%2Fchanges%20to%20the%20device%20itself%2C%20we%20do%20suggest%20you%20look%20at%20the%20IoT%20LTSC%20edition%20as%20that%20is%20supported%20for%2010%20years%20directly%20by%20the%20OEM%2C%20which%20would%20have%20the%20hardware%20driver%20support%20necessary%20to%20support%20a%20static%20environment%20required.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJason%20Leznek%3C%2FP%3E%0A%3CP%3EPrincipal%20Program%20Manager%20-%20Windows%20Lifecycle%3C%2FP%3E%0A%3CP%3EMicrosoft%20Corporation%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2810881%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2810881%22%20slang%3D%22en-US%22%3E%3CP%3EJason%20Leznek%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20assumes%20that%20we%20obtain%20computers%20with%20all%20of%20our%20equipment.%20In%20my%20environment%20we%20have%20thousands%20of%20these%20types%20of%20scientific%20devices%20ranging%20from%20simple%20plate%20readers%20to%20complex%20mass%20spectrometers.%20In%20an%20enterprise%20why%20would%20we%20want%20to%20have%20thousands%20of%20unique%20images%20to%20manage%20on%20our%20company%20network%3F%20We%20have%20strived%20over%20the%20last%2020%20years%20to%20do%20the%20opposite%20and%20allow%20vendors%20to%20work%20with%20us%20so%20we%20can%20use%20corporate%20provided%20systems%20so%20we%20can%20better%20secure%20and%20patch%20them.%26nbsp%3B%3CBR%20%2F%3EMicrosoft%20made%20this%20decision%20without%20input%20from%20its%20customers.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2810915%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2810915%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F117352%22%20target%3D%22_blank%22%3E%40Jason%20Leznek%3C%2FA%3E%26nbsp%3B%26nbsp%3BI%20hate%20to%20beat%20a%20dead%20horse%20at%20this%20point%2C%20especially%20after%20the%20product%20team%20reached%20out%20to%20me%20in%20recent%20months%20based%20on%20previous%20feedback%20in%20these%20comments...%20but%20I%20still%20agree%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F153032%22%20target%3D%22_blank%22%3E%40TammyM%3C%2FA%3E's%20sentiment.%20If%20you're%20a%20massive%20enterprise%20that%20is%20developing%20your%20solutions%20in-house%20or%20in%20close%20relationship%20to%20a%20vendor%2C%20this%20may%20be%20an%20acceptable%20answer%20as%20they're%20likely%20to%20be%20providing%20hardware%2C%20or%20you'll%20have%20a%20deployment%20scale%20large%20enough%20to%20warrant%20making%20your%20own%20partnership%20with%20an%20OEM%20like%20Dell%20where%20IoT%20Enterprise%20LTSC%20would%20be%20obtainable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20if%20you're%20only%20semi-large%20(say%20a%20university%20of%2030%2C000%20students%20%2B%204%2C000%20employees)%2C%20you%20deal%20with%20a%20ton%20of%20hardware%20and%20deployment%20scenarios%20where%20vendors%20for%20all%20sorts%20of%20embedded%2Fspecialized%20devices%20(signage%2C%20spectrometers%2C%20kiosks%2C%20other%20scientific%2Fmedical%20devices)%20are%20*NOT*%20providing%20the%20computers%20or%20the%20OS%20to%20run%20them.%20We%20supply%20them.%20These%20machines%20also%20A)%20cycle%20out%20with%20lifespans%20exceeding%205%20years%2C%20and%20B)%20have%20historically%20been%20broken%20when%20deploying%20feature%20updates%20if%20we%20entertained%20running%20them%20on%20Win10%20Semi-Annual%20Channel%2C%20and%20subsequently%20poorly%20supported%20by%20vendors.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20carrying%20on%20and%20making%20the%20best%20of%20the%20shortened%20lifecycle%20going%20forward%2C%20but%20I%20really%20just%20want%20to%20drive%20the%20point%20home%20that%20%22use%20IoT%20Enterprise%20LTSC%22%20seems%20a%20rather%20flippant%20response%20for%20organizations%20like%20us%2C%20because%20it's%20simply%20not%20as%20easily%20obtainable%20as%20it's%20being%20made%20out%20to%20be.%26nbsp%3B%20Similar%20orgs%20may%20not%20have%20the%20resources%2C%20size%2C%20or%20scale%20to%20justify%20pursuing%20OEMs%20in%20such%20a%20fashion.%20We%20feel%20like%20we're%20a%20forgotten%20side-effect%20of%20this%20matching%20of%20lifespans%20between%20Windows%20Enterprise%20LTSC%20and%20Office%20LTSC%2C%20for%20a%20crowd%20that%20was%20never%20using%20Enterprise%20LTSC%20correctly%20in%20the%20first%20place.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2811021%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2811021%22%20slang%3D%22en-US%22%3E%3CP%3EI%20appreciate%20the%20feedback%20-%20truly%20-%20and%20we%20are%20always%20listening%20to%20our%20customers%20of%20all%20sizes%20to%20better%20understand%20your%20processes%20and%20needs.%26nbsp%3B%20%26nbsp%3BI%20will%20keep%20this%20your%20comments%20and%20keep%20them%20in%20consideration%20as%20iterate%20on%20our%20LTSC%20and%20IoT%20roadmap.%26nbsp%3B%20%26nbsp%3BThank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2812476%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2812476%22%20slang%3D%22en-US%22%3E%3CP%3EComing%20from%20an%20enterprise%20admin%20that%20specializes%20in%20Windows%20deployments%3A%20the%205%20year%20support%20of%20LTSC%202021%20makes%20no%20sense%20to%20us.%20We%20aren't%20concerned%20about%20the%20alignment%20of%20its%20support%20schedule%20with%20Office%20LTSC.%20We%20don't%20even%20use%20Office%20on%20most%20of%20our%20LTSC%20deployments.%20LTSC%202021%20will%20go%20end%20of%20support%20sooner%20than%20LTSC%202019%20will.%20So%20it%20makes%20sense%20for%20us%20to%20continue%20deploying%20LTSC%202019%20for%20as%20long%20as%20we%20can.%20This%20includes%20on%20VMs%20which%20we%20will%20have%20no%20way%20to%20deploy%20LTSC%20IoT%20on%20due%20to%20the%20licensing%20of%26nbsp%3BLTSC%20IoT.%20Also%20the%20complexity%20of%20the%20licensing%20of%20LTSC%20IoT%20makes%20it%20virtually%20unobtainable.%20Microsoft's%20decision%20of%20making%20LTSC%202021%20only%20have%205%20year%20of%20support%20just%20goes%20to%20show%20how%20Microsoft%20is%20out%20of%20touch%20with%20its%20enterprise%20customers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2813046%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2813046%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20a%20lot%20of%20different%20industries%20represented%20here%2C%20kind%20of%20neat.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere's%20an%20idea%20for%20Win11%20(too%20late%20for%20Win10).%20You%20have%20roles%20and%20features%20for%20server%2C%20so%20this%20is%20a%20known%20method%20of%20expanding%20an%20OS...%20How%20about%20use%20this%20method%20to%20produce%20Windows%2011.%20Start%20with%20LTSC%20as%20the%20base%20of%20Pro%2FEnterprise%2FEducation%2C%20then%20allow%20simple%20clicks%20to%20add%20the%20other%20features%20to%20%22scale%20up%22%20to%20Pro.%20You%20would%20of%20course%20need%20to%20pay%20for%20a%20Pro%2FEnterprise%2FEducation%20license%2C%20but%20it%20would%20give%20more%20flexibility%20to%20both%20parties.%20Sure%20would%20save%20a%20lot%20of%20time%20making%20GPO's%20to%20remove%20games%2C%20and%20do%20plenty%20of%20other%20things%20to%20try%20and%20tame%20all%20the%20consumer%20oriented%20things%20that%20we%20just%20don't%20want%20in%20most%20of%20a%20business%20environment.%20I%20would%20consider%20this%20for%20consumer%20oriented%20computers%20as%20well%2C%20not%20everyone%20plays%20games%20on%20a%20%22gaming%22%20machine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20yes%20I'm%20that%20jerk%20that%20removes%2Fblocks%20solitaire%2C%20I'm%20guessing%20I'm%20not%20the%20only%20one%20in%20this%20crowd.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20will%20tell%20you%20that%20the%20worst%20thing%20that%20can%20happen%20is%20you%20forget%20to%20postpone%20feature%20updates%20for%20a%20classroom%20full%20of%20computers%2C%20and%20then%20they%20update%20over%20night.%20You%20come%20in%20the%20next%20day%20and%20the%20key%20piece%20of%20software%20that%20they%20are%20trying%20to%20use%20in%20class%20now%20no%20longer%20functions.%20That's%20what%20pushed%20me%20to%20LTSC%20in%20the%20first%20place.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20keep%20Home%20the%20way%20it%20is%2C%20kind%20of%20the%20%22canary%20in%20the%20coal%20mine%22%2C%20oddly%20it%20seems%20to%20run%20just%20fine%20on%20my%20laptop%20at%20home.%20I%20must%20be%20the%20only%20one%20that%20finds%20it%20acceptable.%20No%20de-bloat%20scripts%20either%2C%20but%20that%20will%20probably%20change.%20Going%20to%20be%20stuck%20on%20this%20because%20I%20don't%20think%2011%20is%20allowed%20to%20run%20on%20my%20hardware.%20But%20that's%20another%20topic.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2155895%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2155895%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70570%22%20target%3D%22_blank%22%3E%40Joe%20Lurie%3C%2FA%3E%3CSPAN%3E%2C%3C%2FSPAN%3E%26nbsp%3Bthanks%20for%20your%20prompt%20response.%20To%20be%20perfectly%20clear%2C%20since%20LTSC%202021%20has%20only%205%20years%20of%20support%20-%20we%20see%20no%20valid%20reason%20for%20adopting%20this%20new%20version%20whatsoever.%20For%20new%20LTSC%20deployments%20going%20forward%2C%20we%20will%20continue%20to%20roll%20out%20LTSC%202019%20(1809).%20For%20new%20information%20worker%20desktops%2C%20we%20will%20continue%20to%20deploy%20Windows%2010%20SAC%20as%20originally%20instructed%20by%20Microsoft.%3C%2FP%3E%3CP%3EWe%20may%20look%20into%20LTSC%20IoT%202021.%20But%20as%20others%20have%20already%20mentioned%20-%20we%20find%20the%20current%20distribution%20and%20licensing%20of%20IoT%20to%20be%20extremely%20constraining%20therefore%20making%20deployment%20of%20IoT%20limited%20and%20impractical%20in%20most%20cases.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2882838%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2882838%22%20slang%3D%22en-US%22%3E%3CP%3EI%20guess%20I'll%20be%20the%20one%20to%20bring%20up%20a%20forgotten%20part%20of%20the%20'information%20workers'%20that%20are%20getting%20over-looked%20by%20the%20SAC%5CLTSC%20argument.%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20not%20sure%20why%20this%20isn't%20just%20more%20of%20a%20'Enterprise%20vs%20Retail-fluffy-crap'%20in%20the%20first%20place%2C%20but%20I%20digress.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20guess%20this%20is%20also%20'slightly'%20off%20topic%20as%20stated%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70570%22%20target%3D%22_blank%22%3E%40Joe%20Lurie%3C%2FA%3E%26nbsp%3Bas%20just%20the%20change%20from%2010-yr%20to%205-yr%20support%20for%20the%20LTSC.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPolice%20Officers%20%5C%20EMT%20%5C%20Small%20Gov%20Emergency%20Responders%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWho%20wants%20to%20be%20the%20first%20to%20call%20911%20and%20have%20the%20dispatcher%20say....%22Tell%20the%20guy%20with%20the%20gun%20to%20hold%20on%20for%20a%20few%20minutes%2C%20while%20I%20get%20my%20new%20Feature%20Update%20with%20the%20latest%20version%20of%20Candy%20Crush%20!%22%3C%2FP%3E%3CP%3Eor%3C%2FP%3E%3CP%3E%22Sorry%2C%20unconscious%20person%20with%20blunt-force%20trama%2C%20I%20was%20trying%20to%20access%20your%20medical%20records%20but%20I'm%20waiting%20for%20the%20Feature%20Release%20to%20get%20that%20important%20Xbox%20%26amp%3B%20virtual%20reality%20function%20to%20be%20installed%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20some%20might%20say%2C%20this%20is%20an%20admin%20issue%20to%20control%5Clockdown%5Cmanage%20the%20SAC.%20You%20might%20suggest%20that%20I%20use%205%20or%2010%20or%2020%20different%20%22free%22%20things%20for%20me%20to%20properly%20manage%20SAC.%20You%20might%20suggest%20100%20different%20GPO's%20to%20help%20me...%20I%20respectfully%20say%2C%20I%20simply%20do%20not%20have%20the%20time%20for%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20(and%201%2C000's%20of%20other%20small%20municipalities)%2C%20simply%20do%20not%20have%20the%20resources%20to%20deal%20with%20a%20retail%20SAC%20version%20of%20Windows.%3C%2FP%3E%3CP%3EWe%20need%20a%20%22Pro%22%20version%20of%20an%20O%2FS.%20No%20fluff.%20No%203D%20Paint.%20No%20Store.%20No%20virtual%20assistants.%20No%20Cortana.%20No%20Xbox.%20No%20Candy%20Crush.%20No%20TV%20%26amp%3B%20Movies.%20Simple%20%26amp%3B%20easy%20to%20manage.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20sorry%20if%20this%20offends%20all%20of%20the%20Millennials%20that%20work%20at%20MS%20and%20have%20created%20all%20of%20these%20%3CEM%3Eincredible%3C%2FEM%3E%20apps%20for%20the%20home%20user%20and%20a%20small%20number%20of%20businesses%20that%20benefit%20from%20them...Pro%20or%20Ent%20version%20should%20simply%20have%20an%20opt-in%20for%20this%20stuff.%20Win98SE%20is%20a%20good%20example%20of%20this%20(yes%2C%20this%20shows%20my%20age).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20use%20SmartDeploy%20right%20now%20as%20the%20best%20way%20to%20easily%20manage%20my%20images.%3C%2FP%3E%3CP%3EI%20do%20have%20SCCM%2C%20but%20I%20use%20it%20in%20very%20limited%20ways.%20I%20do%20have%20some%20GPOs%20to%20do%20some%20simple%20things.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERespectfully%2C%26nbsp%3B%3C%2FP%3E%3CP%3E'You're%20not%20the%20intended%20user%20of%20LTSC'%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2882865%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2882865%22%20slang%3D%22en-US%22%3E%3CP%3EPolice%2C%20fire%2C%20emt%2C%20and%20other%20emergency%20services%20aren't%20on%20LTSC%3F%20That's%20a%20scary%20eye%20opener!!!%20Might%20even%20be%20better%20to%20be%20on%20an%20IOT%20release%20that%20is%20%22ultra%20stable%22%20like%20the%20old%20embedded%20releases.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20going%20to%20have%20to%20ask%20our%20campus%20police%20what%20OS%20they%20have%20on%20their%20computers%2C%20they%20are%20kind%20of%20separate%20from%20the%20rest%20of%20campus.%20If%20they%20aren't%20on%20LTSC%20I'll%20have%20to%20explain%20why%20it%20might%20be%20a%20better%20choice%20than%20Pro%20or%20Enterprise.%20I%20know%20they%20aren't%20really%20part%20of%20our%20domain%20controllers%2C%20so%20not%20really%20part%20of%20the%20GPO%20that%20delays%20the%20feature%20updates.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2883055%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2883055%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1033918%22%20target%3D%22_blank%22%3E%40Greg_E999%3C%2FA%3E%26nbsp%3BI%20almost%20got%20burned%20with%20LTSC%202019%20only%20running%20on%20%22current%22%20hardware%2C%20meaning%20(iirc)%20Kabylake%20processors...and%20not%20newer.%20So%2C%20next%20year%2C%20I%20have%20to%20find%20systems%20with%2010th-gen%20Intel%20(%3F)%20or%20older%20hardware%20-%20or%2C%20most%20likely%2C%20start%20deploying%20Win11%20LTSC.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20will%20start%20to%20look%20at%20IoT%20as%20well%2C%20more%20time%20I%20don't%20have.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eedit%3A%20I%20guess%20W10LTSC%20H2.%20But%20I%20do%20need%20to%20create%20%26amp%3B%20deploy%20this%20next%20version.%20I%20can't%20just%20upgrade%20an%20existing%202019LTSC.%3C%2FP%3E%3CP%3ELTSC%20is%20a%20wipe%5Creplace.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2883114%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2883114%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%20no%20in%20place%20upgrade%20on%20these.%20And%20I%20checked%20today%20and%20the%20latest%20LTSC%20is%20still%20not%20out.%20I%20need%20to%20get%20things%20ready%20for%20my%20little%20network%20and%20it%20would%20be%20nice%20to%20get%20to%20work%20sooner%20than%20later.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2883136%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2883136%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1033918%22%20target%3D%22_blank%22%3E%40Greg_E999%3C%2FA%3E%26nbsp%3BYou%20can%20IPU%20WIndows%2010%20LTSC%20from%20an%20ealier%20version%20to%20a%20newer%20version.%20Version%202021%20will%20be%20released%20in%20a%20few%20weeks%20when%20the%20next%20SAC%20version%20is%20released.%20And%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1195495%22%20target%3D%22_blank%22%3E%40Spoot%3C%2FA%3E%2C%20for%20planning%20purposes%2C%20do%20not%20expect%20a%20Windows%2011%20LTSC%20version%20until%20the%20next%20one%20in%20about%203%20years.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2883153%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2883153%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70570%22%20target%3D%22_blank%22%3E%40Joe%20Lurie%3C%2FA%3E%26nbsp%3BI've%20never%20heard%20nor%20seen%20information%20on%20IPU%20of%20an%20existing%20LTSC%20to%20a%20newer%20version....%3F%3C%2FP%3E%3CP%3EI%2C%20too%2C%20will%20watch%20for%20LTSC%202021.%20I%20mis-spoke%20earlier%20about%20Win11LTSC.%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20it%20be%20%22W10LTSC%202019%20H2%22%20or%20W10LTSC%202021%22%20that%20gets%20released%20in%20a%20couple%20weeks%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2883162%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2883162%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20says%20that%20it%20listens%20to%20its%20customers.%26nbsp%3B%20Okay.%26nbsp%3B%20What%20Enterprise%20users%20asked%20for%20two%20updates%20per%20year%3F%26nbsp%3B%20And%20Candy%20Crush%3F%26nbsp%3B%20And%20a%20store%20where%20the%20end%20users%20can%20download%20more%20unapproved%20apps%3F%26nbsp%3B%20And%20a%20major%20changes%20to%20the%20UI%20(in%20Windows%2011%20Enterprise)%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeriously%2C%20what%20is%20called%20Enterprise%20LTSC%20%3CEM%3Eshould%20be%3C%2FEM%3E%20Enterprise.%26nbsp%3B%20LTSC%20should%20be%20really%20special%2C%20maybe%20to%20the%20point%20that%20IoT%20is%20special%20just%20through%20an%20Enterprise%20channel%20rather%20than%20being%20available%20with%20OEM%20hardware.%26nbsp%3B%20But%20today%2C%20LTSC%20is%20the%20only%20way%20to%20get%20around%20a%20bunch%20of%20the%20garbage%20that%20Microsoft%20dumps%20into%20Enterprise.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20really%20want%20to%20listen%20to%20customers%2C%20fix%20the%20networking%20that%20still%20has%20references%20to%20Microsoft%20LAN%20Manager%20and%20Windows%20for%20Workgroups.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2883742%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2883742%22%20slang%3D%22en-US%22%3E%3CP%3ENow%20that's%20direct%20requests%2C%20no%20%22beating%20around%20the%20bush%22%20here.%20Can't%20say%20that%20I%20don't%20feel%20the%20same%20way%2C%20and%20it%20should%20be%20allowed%20to%20set%20up%20personal%20computers%20to%20this%20%22less%20featured%22%20enterprise%20version.%20Anyone%20that%20has%20a%20Pro%20license%20should%20be%20allowed%20to%20%22remove%22%20features%20that%20they%20don't%20want%20or%20need%2C%20and%20do%20it%20easily.%20I%20don't%20want%20candy%20crush%20at%20home%20either%2C%20nor%20do%20I%20want%20a%20lot%20of%20things%20that%20people%20commonly%20refer%20to%20as%20%22junk%22%20or%20%22bloat%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20that%20junk%20and%20bloat%20are%20paying%20the%20bills%2C%20so%20not%20likely%20to%20be%20removed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2883870%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2883870%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1033918%22%20target%3D%22_blank%22%3E%40Greg_E999%3C%2FA%3E%26nbsp%3BI'm%20OK%2C%20as%20well%2C%20with%20bloat%20on%20'Home'.%20Maybe%20even%20'Pro'%2C%20as%20that%20now%20serves%20%3CEM%3Ecertain%3C%2FEM%3E%20customers.%20'ENT'%2C%20though...we%20pay%20a%20lot%20more%20-%20and%20not%20just%20so%20I%20can%20get%20bitlocker%20or%20something%20in-addition-to.%20This%20(my%20subscription%20to%20an%20EA)%20should%20cover%20any%20loss%20of%20revenue%20from%20not%20including%20Candy%20Crush.%3C%2FP%3E%3CP%3E'Enterprise'%20should%20easily%20LACK%20all%20the%20fluff%5Cbloat%20unless%20I%20opt-in.%3C%2FP%3E%3CP%3EIt%20shouldn't%20be%20an%20'Everything-including-the-kitchen-sink'%20O%2FS.%3C%2FP%3E%3CP%3EBut%2C%20I%20think%20this%20ship%20sailed%20years%20ago.%3C%2FP%3E%3CP%3E%2Frant%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2886004%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2886004%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20that%20ship%20is%20well%20over%20the%20horizon%20now.%20I'll%20go%20back%20to%20Roles%20and%20Features%20in%20server%2C%20set%20up%20ENT%20and%20EDU%20so%20you%20can%20add%20that%20stuff%20back%20in%20if%20you%20want.%20Or%20at%20least%20make%20it%20easier%20to%20remove%20with%20GPO%2C%20not%20just%20suppress%20but%20remove.%20A%20one%20stop%20GPO%20to%20remove%20the%20%22junk%22%20would%20be%20OK%20and%20strip%20it%20down%20to%20LTSC%20features%2C%20maybe%20tick%20boxes%20to%20remove%20stuff%20but%20still%20in%20an%20easy%20to%20find%20GPO.%20Yes%20I%20do%20kill%20games%20through%20GPO%2C%20that%20goes%20back%20to%20XP%20Pro%20days%20and%20it%20will%20stay%20in%20case%20I%20ever%20need%20to%20go%20back%20to%20a%20Pro%2FENT%20version.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20handle%20the%20contract%20details%2C%20so%20not%20sure%20what%20we%20are%20paying%20each%20year%2C%20but%20I%20bet%20it%20isn't%20pocket%20change.%20I%20think%20we%20are%20E5%20and%20I'm%20not%20sure%20if%20they%20charge%20us%20per%20student%20or%20if%20students%20are%20free.%20And%20how%20they%20determine%20each%20computer%20considering%20that%20the%20majority%20are%20student%20use.%20It%20says%20per%20user%2C%20and%20I%20know%20we%20pay%20for%20employees%20so%20around%20%24680%20per%20year%20just%20for%20me.%20That's%20a%20lot%20more%20than%20someone%20buying%20a%20laptop%20with%20Pro%20to%20use%20at%20home%2C%20and%20most%20of%20our%20hardware%20comes%20with%20a%20Pro%20sticker%20on%20the%20side%20even%20though%20we%20are%20only%20required%20to%20have%20Home%20to%20be%20able%20to%20upgrade%20to%20ENT%2FEDU%20versions.%20Paying%20on%20the%20front%20end%20and%20back%20end.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2904336%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2904336%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20we%20have%20an%20interesting%20discussion%20here%2C%20I'll%20add%20my%20thoughts%20and%20make%20it%20brief.%26nbsp%3B%20I%20work%20in%20the%20IT%20Department%20for%20the%20largest%20non-profit%20air%20ems%20agency%20in%20the%20US.%26nbsp%3B%20We%20have%20just%20under%201000%20employees%20and%20about%20450%20Windows%2010%20computers.%26nbsp%3B%20Every%20single%20one%20of%20those%20Windows%2010%20computers%20runs%20either%201609%20LTSB%20(end%20of%20support%20Oct%202026)%20or%201809%20LTSC%20(end%20of%20support%20Sept%202029).%26nbsp%3B%20As%20a%20result%20our%20environment%20is%20incredibly%20stable.%26nbsp%3B%20We%20approve%20security%20fixes%20only%20using%20WSUS%20and%20have%20completely%20side%20stepped%20the%20feature%20update%20twice%20a%20year.%26nbsp%3B%20Let's%20be%20honest%2C%20these%20are%20really%20in%20place%20OS%20upgrades.%26nbsp%3B%20When%20the%20next%20build%20of%20LTSC%20becomes%20available%2C%20we%20will%20build%20that%20image%20and%20make%20it%20our%20standard%20for%20new%20deployments.%26nbsp%3B%20Not%20sure%20why%20this%20next%20release%20is%20taking%20so%20long%2C%20I%20thought%20it%20was%20supposed%20to%20be%20available%20in%20Q4%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20read%20over%20and%20over%20again%20that%20LTSC%20is%20only%20to%20be%20used%20for%20niche%20implementations%20when%20it%20is%20only%20absolutely%20necessary.%26nbsp%3B%20At%20first%20I%20was%20concerned%2C%20I%20mean%20what%20if%20there%20is%20an%20app%20in%20the%20Windows%20store%20that%20is%20critical%20to%20our%20business%3F%26nbsp%3B%20Never%20happened.%26nbsp%3B%20Furthermore%20I%20have%20been%20able%20to%20watch%20from%20the%20sidelines%20as%20a%20constantly%20changing%20mainstream%20Windows%2010%20build%20introduces%20vulnerability%20after%20vulnerability.%26nbsp%3B%20Suggesting%20that%20everyone%20should%20perform%20regular%20OS%20upgrades%20is%26nbsp%3Bludicrous%20in%20my%20opinion%20and%20this%20rebrand%20to%20the%20name%20IoT%20with%20half%20the%20support%20term%20is%20concerning.%26nbsp%3B%20The%20prospect%20of%20one%20day%20being%20forced%20to%20conform%20to%20a%20Microsoft%20on%20high%20mandate%20seems%20like%20a%20direct%20slap%20in%20the%20face.%26nbsp%3B%20Microsoft%20has%20proven%20they%20are%20incapable%20of%20producing%20secure%20products%20on%20the%20release%20cycle%20they've%20adopted%20and%20it%20should%20stop%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20started%20with%20Windows%20very%20young%20and%20have%20maintained%20MCSE%2FMCSA%20through%202003%2C%202008%2C%202012%2C%20and%20216.%26nbsp%3B%20Today%20I%20have%20only%20disdain%20for%20Microsoft%20products.%26nbsp%3B%20The%20second%20there%20is%20a%20viable%20alternative%20to%20AD%20and%20GPOs%20for%20management%2C%20I%20will%20be%20recommending%20a%20move%20to%20that%20platform.%26nbsp%3B%20They%20can%20only%20get%20away%20with%20this%20behavior%20because%20they've%20been%20the%20only%20game%20in%20town.%26nbsp%3B%20Linux%20with%20domainless%20enterprise%20technology%20from%20jumpcloud%20is%20looking%20pretty%20good%20right%20about%20now.%26nbsp%3B%20Never%20thought%20I%20would%20see%20the%20day%20when%20I%20would%20hope%20Microsoft%20would%20fail.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EAdam%20Tyler%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2908564%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2908564%22%20slang%3D%22en-US%22%3E%3CP%3EAdam%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20%22played%22%20with%20Zentyal%20for%20AD%2C%20but%20not%20really%20devoted%20the%20kind%20of%20time%20needed%20to%20learn%20it.%20They%20have%20a%20relatively%20decent%20book%20put%20together%20for%20certification%20training%2C%20you%20can%20buy%20PDF%20or%20printed%20version%20for%20v7.%20The%20one%20thing%20they%20can't%20do%20is%20integrate%20GPO%20into%20the%20server%20role%20like%20all%20of%20the%20MS%20server%20products%20can%20do.%20What%20they%20suggest%20is%20installing%20full%20RSAT%20tools%20on%20a%20client%20device%20and%20managing%20GPO%20through%20RSAT...%20Again%20not%20tested%20by%20me.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20WSUS%20you%20are%20likely%20still%20going%20to%20need%20an%20MS%20server%2C%20not%20sure%20if%20you%20can%20accomplish%20this%20through%20Chocolately%20or%20FOG.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2978962%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2978962%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70570%22%20target%3D%22_blank%22%3E%40Joe%20Lurie%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20clarify%20the%20mainstream%20and%20extended%20support%20dates%20for%20the%20client%20LTSC.%20Microsoft%20provides%20conflicting%20information%20as%20of%20today.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20this%20blog%20post%20you%20state%3C%2FP%3E%3CP%3E%3CEM%3EWindows%2010%20Client%20LTSC%20will%20change%20to%20a%205-year%20lifecycle%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EAre%20you%20talking%20about%20the%20mainstream%20support%2C%20extended%20support%2C%20or%20the%20total%3F%26nbsp%3B%3C%2FSTRONG%3EThe%20word%20%3CEM%3Echange%3C%2FEM%3E%20makes%20sense%20only%20in%20the%20context%20of%20%3CEM%3Ethe%20total%3C%2FEM%3E%2C%20because%20LTSC%201809%20has%205%20years%20of%20mainstream%20and%205%20years%20of%20extended%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20page%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwhats-new%2Fltsc%2Fwhats-new-windows-10-2021%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWhat's%20new%20in%20Windows%2010%20Enterprise%20LTSC%202021%20-%20What's%20new%20in%20Windows%20%7C%20Microsoft%20Docs%3C%2FA%3E%26nbsp%3B%20says%20the%20same%20thing%20without%20clarifying%20the%20support%20type.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22VadimSterkin_0-1637214787673.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F327876iCE3F57EEA70C4C19%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22VadimSterkin_0-1637214787673.png%22%20alt%3D%22VadimSterkin_0-1637214787673.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EBut%20this%20page%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fwin10releaseinfo%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fwin10releaseinfo%3C%2FA%3E%26nbsp%3Blists%205%20years%20of%20mainstream%20and%205%20years%20of%20extended%20support%20for%20LTSC%2021H2%20(2021)%2C%20%3CSTRONG%3Ethe%20total%20of%2010%20years%3C%2FSTRONG%3E.%20This%20is%20what's%20posted%20as%20of%20today%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22VadimSterkin_1-1637215144610.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F327877i5E4FBBA4B34416D7%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22VadimSterkin_1-1637215144610.png%22%20alt%3D%22VadimSterkin_1-1637215144610.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EWhat%20have%20you%20changed%20then%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDigging%20into%20this%20a%20bit%20deeper%2C%20we%20can%20compare%20the%20lifecycle%20pages%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Flifecycle%2Fproducts%2Fwindows-10-enterprise-ltsc-2021%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%2010%20Enterprise%20LTSC%202021%20-%20Microsoft%20Lifecycle%20%7C%20Microsoft%20Docs%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22VadimSterkin_1-1637215814526.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F327879i5D1409A592737785%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22VadimSterkin_1-1637215814526.png%22%20alt%3D%22VadimSterkin_1-1637215814526.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3Evs%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Flifecycle%2Fproducts%2Fwindows-10-enterprise-ltsc-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%2010%20Enterprise%20LTSC%202019%20-%20Microsoft%20Lifecycle%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22VadimSterkin_0-1637215783416.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F327878i5CA61FEDB5473B33%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22VadimSterkin_0-1637215783416.png%22%20alt%3D%22VadimSterkin_0-1637215783416.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EThe%20difference%20is%20that%20LTSC%202021%20does%20not%20have%20the%20extended%20support.%20If%20that's%20the%20case%2C%20why%20wouldn't%20you%20have%20said%20that%20straight%3F%3C%2FP%3E%3CP%3EBut%20then%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fwin10releaseinfo%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fwin10releaseinfo%3C%2FA%3E%26nbsp%3Bis%20wrong.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2979907%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2979907%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F226354%22%20target%3D%22_blank%22%3E%40Vadim%20Sterkin%3C%2FA%3E%26nbsp%3BThank%20you%20for%20reaching%20out%20for%20clarification.%20The%20entire%20lifecycle%20for%20LTSC%202021%20is%205%20years.%20Previously%20we%20marked%20LTSC%20as%205%2B5%20(mainstream%2Bextended)%20but%20in%20the%20LTSC%20world%2C%20there's%20no%20difference%20between%20mainstream%20and%20extended%20since%20LTSC%20does%20not%20receive%20new%20features%20-%20not%20even%20in%20the%20first%205%20years.%20So%20we%20dropped%20the%20extended%20and%20changed%20LTSC%20from%202021%20and%20forward%20to%20a%20full%205%20year%20lifecycle.%20Any%20previous%20LTSB%20or%20LTSC%20version%20retains%20their%20existing%2010%20years%20lifecycle%20support%2C%20and%20IoT%20LTSC%202021%20retinas%20its%2010%20years%20lifecycle%20support.%20But%20Windows%2010%20Enterprise%20LTSC%202021%20is%20changed%20to%205%20years.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20are%20correct%20that%20the%20%2Fwin10releaseinto%20page%20is%20wrong%20or%20misleading.%20IoT%20LTSC%20will%20be%20supported%20for%2010%20years%2C%20whilst%20LTSC%20Enterprise%20is%205%20years%2C%20I%20will%20have%20that%20page%20clarified.%3C%2FP%3E%0A%3CP%3EThanks%2C%20and%20sorry%20for%20the%20confusion.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2980096%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2980096%22%20slang%3D%22en-US%22%3E%3CP%3ENow%20that%20the%202021%20releases%20are%20out%2C%20I%20am%20still%20waiting%20for%20an%20answer%20from%20Microsoft%20on%20how%20to%20move%20forward%20with%20the%20changes%20they%20made.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToday%20in%20a%20large%20enterprise%20my%20IT%20team%20provides%20computers%20to%20be%20used%20with%20equipment.%20We%20deploy%20our%20own%20computer%20with%20LTSC%20and%20work%20with%20the%20device%20vendors%20to%20support%20this%20because%20in%20a%20very%20large%20environment%20we%20need%20standardization%20to%20maintain%20a%20secure%2C%20manageable%20environment.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20is%20making%20an%20assumption%20that%20any%20specialized%20device%20needing%20the%2010%20year%20LTSC%20is%20sold%20with%20that%20device%20and%20that%20is%20a%20problem.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIts%20not%20appropriate%20for%20us%20to%20go%20to%20the%205%20select%20Microsoft%20preferred%20IoT%20vendors%20to%20buy%20the%20licenses%20either.%20Microsoft%20assumes%20that%20the%20Vendor%20of%20the%20specialized%20device%20is%20going%20to%20do%20that%20and%20then%20sell%20it%20to%20us.%20This%20is%20not%20practical%20or%20realistic.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20a%205%20year%20version%20is%20also%20not%20practical%20when%20dealing%20with%20this%20type%20of%20equipment.%20My%20world%20has%20a%20longer%20refresh%20cycle%20due%20to%20the%20vendors%20taking%20longer%20to%20update%20their%20software.%20Additionally%2C%20keeping%20up%20with%20the%20existing%2010%20year%20span%20is%20difficult%20enough%20with%20compliance%20requirements%20and%20dealing%20with%20regulatory%20agencies.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIm%20sure%20we%20will%20be%20sticking%20with%202019%20for%20quite%20some%20time%20given%20that%20its%20supported%20beyond%20the%202021%20LTSC%20however%20we%20will%20have%20to%20get%20a%20better%20path%20forward%20from%20Microsoft%20at%20some%20point.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2980150%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2980150%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70570%22%20target%3D%22_blank%22%3E%40Joe%20Lurie%3C%2FA%3E!%3C%2FP%3E%3CP%3EI%20truly%20appreciate%20your%20quick%20response%20and%20clarification.%20Hopefully%2C%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fwin10releaseinfo%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fwin10releaseinfo%3C%2FA%3E%26nbsp%3Bwill%20get%20updated%20soon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegarding%20the%20extended%20support%2C%20I%20totally%20understand%20what%20you%20mean%20by%20saying%3C%2FP%3E%3CP%3E%3CEM%3Ebut%20in%20the%20LTSC%20world%2C%20there's%20no%20difference%20between%20mainstream%20and%20extended%20since%20LTSC%20does%20not%20receive%20new%20features%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20these%20intricacies%20are%20beyond%20understanding%20for%20the%20vast%20majority%20of%20your%20audience.%20We%20look%20at%20the%20LTSC%202019%20lifecycle%20page%20or%20even%20a%20freshly%20baked%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Flifecycle%2Fproducts%2Fwindows-10-iot-enterprise-ltsc-2021%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%2010%20IoT%20Enterprise%20LTSC%202021%20-%20Microsoft%20Lifecycle%20%7C%20Microsoft%20Docs%3C%2FA%3E%20and%20see%20both%20the%20mainstream%20and%20extended%20support%20listed.%20We%20have%20no%20choice%20but%20take%20this%20at%20the%20face%20value%20and%20use%20this%20terminology.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2980654%22%20slang%3D%22en-US%22%3ERe%3A%20The%20next%20Windows%2010%20Long%20Term%20Servicing%20Channel%20(LTSC)%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2980654%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F972137%22%20target%3D%22_blank%22%3E%40Tammy104%3C%2FA%3E%2C%26nbsp%3Bthank%20you%20for%20your%20comment.%26nbsp%3B%20%26nbsp%3BWe%20are%20exploring%20options%20to%20address%20the%20problem%20you%20are%20describing.%26nbsp%3B%20I%20don't%20have%20a%20timetable%20for%20if%2Fwhen%20we%20have%20a%20solution%2C%20but%20we%20are%20looking%20into%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Feb 18 2021 12:00 PM
Updated by: