MicrosoftJason_Leznek I hate to beat a dead horse at this point, especially after the product team reached out to me in recent months based on previous feedback in these comments... but I still agree TammyM's sentiment. If you're a massive enterprise that is developing your solutions in-house or in close relationship to a vendor, this may be an acceptable answer as they're likely to be providing hardware, or you'll have a deployment scale large enough to warrant making your own partnership with an OEM like Dell where IoT Enterprise LTSC would be obtainable.
However, if you're only semi-large (say a university of 30,000 students + 4,000 employees), you deal with a ton of hardware and deployment scenarios where vendors for all sorts of embedded/specialized devices (signage, spectrometers, kiosks, other scientific/medical devices) are *NOT* providing the computers or the OS to run them. We supply them. These machines also A) cycle out with lifespans exceeding 5 years, and B) have historically been broken when deploying feature updates if we entertained running them on Win10 Semi-Annual Channel, and subsequently poorly supported by vendors.
We're carrying on and making the best of the shortened lifecycle going forward, but I really just want to drive the point home that "use IoT Enterprise LTSC" seems a rather flippant response for organizations like us, because it's simply not as easily obtainable as it's being made out to be. Similar orgs may not have the resources, size, or scale to justify pursuing OEMs in such a fashion. We feel like we're a forgotten side-effect of this matching of lifespans between Windows Enterprise LTSC and Office LTSC, for a crowd that was never using Enterprise LTSC correctly in the first place.
