Windows 10 LTSC Lockdown

%3CLINGO-SUB%20id%3D%22lingo-sub-307356%22%20slang%3D%22en-US%22%3EWindows%2010%20LTSC%20Lockdown%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-307356%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20the%20desktop%20deployment%20guy%20for%20a%20manufacturing%20company.%20We%20currently%20use%20windows%207%20machines%20that%20are%20locked%20down%20to%20the%20point%20that%20the%20user%20can%20only%20run%20apps%20that%20are%20specified%20in%20the%20Start%20Menu.%26nbsp%3BThey%20are%20only%20presented%20with%20the%20taskbar%20and%26nbsp%3Bcustomized%20start%20menu.%26nbsp%3BI%20have%20been%20asked%20to%20migrate%20this%20to%20Windows%2010.%20Ideally%20this%20would%20be%20running%20on%20LTSC%2C%20as%20I%20want%20the%2010%20years%20of%26nbsp%3B%20extended%20support%20without%20having%20to%20worry%20about%20upgrading%20them%20to%20a%20%22supported%22%20version%20every%2018%20months.%20I%20tried%20customizing%20the%20start%20layout%20as%20a%20multi-app%20kiosk%2C%20from%20%3CA%20title%3D%22Set%20up%20a%20multi-app%20kiosk%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fconfiguration%2Flock-down-windows-10-to-specific-apps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fconfiguration%2Flock-down-windows-10-to-specific-apps%3C%2FA%3E%26nbsp%3B%26nbsp%3Bbut%20that%20doesn't%20appear%20to%20work.%20If%20there%20is%20any%20documentation%20that%20anyone%20has%20seen%2C%20it%20would%20be%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309302%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20LTSC%20Lockdown%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309302%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Farquea.%20Microsoft%20is%20basically%20trying%20for%20force%20everyone%20onto%20the%20Windows%20SAAS%20model.%20What%20MS%20is%20saying%20is%20that%20the%20current%20version%20of%20windows%20LTSC%20may%20not%20be%20supported%20on%20future%20chipsets.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20using%20the%20LTSC%20as%20my%20base%20for%20everything%2C%20as%20I%20liked%20the%20stability%2C%20until%20we%20purchased%20a%20Dell%20XPS%2013.%20My%20deployment%20strategy%20uses%26nbsp%3B%20LTSC%20and%20the%20latest%20drivers%20from%20dell%2C%20the%20graphics%20driver%2C%20synaptics%20driver%20and%20something%20else%20would%20not%20work%20correctly.%20Once%20I%20switched%20the%20operating%20system%20in%20the%20task%20sequence%20from%20LTSC%20to%20the%20SAAS%20version%20it%20worked%20perfectly.%20I%20wasted%20a%20couple%20of%20days%20trying%20to%20figure%20that%20out.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20the%20same%20as%20the%20BS%20they%20pulled%20with%20the%20Skylake%2FKabylake%20processor%20to%20force%20users%20off%20of%20Windows%207.%26nbsp%3B%20Unlike%20previous%20versions%20of%20windows%20you%20can't%20download%20and%20install%20an%20updated%20.net%2C%20its%20baked%20in.%20So%20unless%20you%20get%20the%20SAAS%20version%20you%20are%20stuck%20with%204.7%20on%201809.%20When%20the%20next%20version%20of%20LTSC%20comes%20out%2C%20it%20will%20have%20that%20version%20of%20.Net%20and%20the%20cycle%20will%20continue.%26nbsp%3B%20I%20have%20PC's%20that%20run%20a%20manufacturing%20process.%20I%20don't%20need%20anything%20other%20than%20the%20basic%20windows.%26nbsp%3B%20The%20LTSC%20is%20actually%20a%20requirement%20for%20some%20of%20the%20software%20we%20have.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOriginally%2C%20this%20was%20posted.%3C%2FP%3E%3CP%3EMicrosoft%20also%20plans%20to%20end%20support%20for%20Office%20365%20ProPlus%20on%20the%20following%20Windows%2010%20versions%2C%20starting%20on%20Jan.%2014%2C%202020%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CI%3EAny%20Windows%2010%20LTSC%20release%3C%2FI%3E%3C%2FLI%3E%3CLI%3E%3CI%3EWindows%20Server%202016%20and%20older%3C%2FI%3E%3C%2FLI%3E%3CLI%3E%3CI%3EWindows%208.1%20and%20older%3C%2FI%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EThe%20Jan.%2014%2C%202020%20end-of-support%20date%20seems%20rather%20accelerated.%20For%20instance%2C%20Windows%208.1%20will%20fall%20out%20of%20support%20on%20Jan.%2010%2C%202023%2C%20according%20to%20a%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F13853%2Fwindows-lifecycle-fact-sheet%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20support%20page%3C%2FA%3E%2C%20so%20users%20of%20Windows%208.1%20and%20Office%20365%20ProPlus%20will%20have%20about%20three%20years%20less%20support%20under%20Microsoft's%20revised%20policy%20than%20might%20have%20been%20anticipated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20was%20revised%20again%20in%20September.%3C%2FP%3E%3CP%3EOffice%20365%20ProPlus%20support%20on%20those%20systems%20was%20supposed%20to%20end%20on%20Jan.%2014%2C%202020.%20Here%20are%20Microsoft's%20revised%20support%20dates%20for%20Office%20365%20ProPlus%2C%20as%20announced%20Thursday%20by%20Spataro%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CEM%3EOffice%20365%20ProPlus%20will%20continue%20to%20be%20supported%20on%20Windows%208.1%20through%20January%202023%2C%20which%20is%20the%20end%20of%20support%20date%20for%20Windows%208.1.%3C%2FEM%3E%3C%2FLI%3E%3CLI%3E%3CEM%3EOffice%20365%20ProPlus%20will%20also%20continue%20to%20be%20supported%20on%20Windows%20Server%202016%20until%20October%202025%3C%2FEM%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3BI%20think%20the%20best%20part%20of%20this%20conversation%20is%20he%20obviously%20didn't%20even%20read%20what%20I%20was%20asking%20for%20and%20just%20saw%20LTSC%20and%20started%20spouting%20the%20typical%20MS%20BS.%20My%20scenario%20is%20precisely%20what%20LTSC%20was%20designed%20for.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308587%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20LTSC%20Lockdown%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308587%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Ken%2C%20could%20you%20expand%20on%20%22%3CSPAN%3EOffice%20ProPlus%20also%20isn't%20supported%20with%20LTSC.%22%20please%20as%20this%20is%20a%20statement%20i've%20become%20confused%20with%2F%20I%20can%20install%20Office%20Pro%20Plus%20versions%20onto%20LTSC%202016%20and%202019%20no%20problem%20so%20what%20is%20the%20'not%20supported'%20aspect%20of%20this%20and%20what%20does%20that%20actually%20mean%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-307804%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20LTSC%20Lockdown%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-307804%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Scott%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20sure%20you%20know%20more%20about%20your%20environment%20than%20I%20do%2C%20however%20if%20you're%20only%20looking%20to%20leverage%20LTSC%20to%20avoid%20having%20a%20Windows%20Servicing%20plan%20for%20your%20organization%20then%20you're%20really%20not%20solving%20this.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20are%20other%20things%20to%20consider%20with%20looking%20to%20leverage%20LTSC%3A%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EApplication%20Support%3C%2FSTRONG%3E%3A%20There%20are%20ISVs%20that%20don't%20support%20LTSC.%20There's%20also%20potentially%20a%20gap%20in%20APIs%20being%20used.%20Office%20ProPlus%20also%20isn't%20supported%20with%20LTSC.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ESilicon%20Support%3A%3C%2FSTRONG%3E%20%3CSPAN%3EWindows%2010%20Enterprise%20LTSC%20will%20support%20the%20currently%20released%20processors%20and%20chipsets%20at%20the%20time%20of%20release%20of%20the%20LTSC.%20When%20choosing%20to%20utilize%20the%20LTSC%2C%20you%20must%20factor%20hardware%20into%20your%20decision%2C%20making%20sure%20you%20have%20a%20long-term%20supply%20of%20devices%20and%20service%20components%20for%20the%20life%20of%20your%20expected%20usage%20of%20the%20device.%20If%20the%20hardware%20your%20device%20is%20using%20needs%20to%20be%20replaced%20in%20five%20years%2C%20do%20you%20have%20a%20replacement%20supply%20to%20support%20the%20version%20you%20are%20running%3F%20You%20also%20want%20to%20be%20sure%20you%20have%20a%20hardware%20solution%20that%20will%20provide%20you%20with%20extended%20driver%2Ffirmware%20support%20to%20match%20your%20expected%20lifecycle%20use%20of%20the%20LTSC%20for%20that%20device.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EIf%20you%20haven't%20already%20checked%20it%20out%2C%20look%20at%20the%20Ignite%20session%20around%20LTSC%20in%20the%20Enterprise%3A%26nbsp%3B%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Fmyignite.techcommunity.microsoft.com%2Fsessions%2F64512%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmyignite.techcommunity.microsoft.com%2Fsessions%2F64512%3C%2FA%3E%3C%2FFONT%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I am the desktop deployment guy for a manufacturing company. We currently use windows 7 machines that are locked down to the point that the user can only run apps that are specified in the Start Menu. They are only presented with the taskbar and customized start menu. I have been asked to migrate this to Windows 10. Ideally this would be running on LTSC, as I want the 10 years of  extended support without having to worry about upgrading them to a "supported" version every 18 months. I tried customizing the start layout as a multi-app kiosk, from https://docs.microsoft.com/en-us/windows/configuration/lock-down-windows-10-to-specific-apps  but that doesn't appear to work. If there is any documentation that anyone has seen, it would be appreciated.

3 Replies

Hi Scott,

 

I'm sure you know more about your environment than I do, however if you're only looking to leverage LTSC to avoid having a Windows Servicing plan for your organization then you're really not solving this.

 

There are other things to consider with looking to leverage LTSC:

Application Support: There are ISVs that don't support LTSC. There's also potentially a gap in APIs being used. Office ProPlus also isn't supported with LTSC.

 

Silicon Support: Windows 10 Enterprise LTSC will support the currently released processors and chipsets at the time of release of the LTSC. When choosing to utilize the LTSC, you must factor hardware into your decision, making sure you have a long-term supply of devices and service components for the life of your expected usage of the device. If the hardware your device is using needs to be replaced in five years, do you have a replacement supply to support the version you are running? You also want to be sure you have a hardware solution that will provide you with extended driver/firmware support to match your expected lifecycle use of the LTSC for that device.

 

If you haven't already checked it out, look at the Ignite session around LTSC in the Enterprise: https://myignite.techcommunity.microsoft.com/sessions/64512

 

Hi Ken, could you expand on "Office ProPlus also isn't supported with LTSC." please as this is a statement i've become confused with/ I can install Office Pro Plus versions onto LTSC 2016 and 2019 no problem so what is the 'not supported' aspect of this and what does that actually mean?

Hey Farquea. Microsoft is basically trying for force everyone onto the Windows SAAS model. What MS is saying is that the current version of windows LTSC may not be supported on future chipsets.

 

I was using the LTSC as my base for everything, as I liked the stability, until we purchased a Dell XPS 13. My deployment strategy uses  LTSC and the latest drivers from dell, the graphics driver, synaptics driver and something else would not work correctly. Once I switched the operating system in the task sequence from LTSC to the SAAS version it worked perfectly. I wasted a couple of days trying to figure that out.

 

This is the same as the BS they pulled with the Skylake/Kabylake processor to force users off of Windows 7.  Unlike previous versions of windows you can't download and install an updated .net, its baked in. So unless you get the SAAS version you are stuck with 4.7 on 1809. When the next version of LTSC comes out, it will have that version of .Net and the cycle will continue.  I have PC's that run a manufacturing process. I don't need anything other than the basic windows.  The LTSC is actually a requirement for some of the software we have.

 

Originally, this was posted.

Microsoft also plans to end support for Office 365 ProPlus on the following Windows 10 versions, starting on Jan. 14, 2020:

  • Any Windows 10 LTSC release
  • Windows Server 2016 and older
  • Windows 8.1 and older

The Jan. 14, 2020 end-of-support date seems rather accelerated. For instance, Windows 8.1 will fall out of support on Jan. 10, 2023, according to a Microsoft support page, so users of Windows 8.1 and Office 365 ProPlus will have about three years less support under Microsoft's revised policy than might have been anticipated.

 

This was revised again in September.

Office 365 ProPlus support on those systems was supposed to end on Jan. 14, 2020. Here are Microsoft's revised support dates for Office 365 ProPlus, as announced Thursday by Spataro:

  • Office 365 ProPlus will continue to be supported on Windows 8.1 through January 2023, which is the end of support date for Windows 8.1.
  • Office 365 ProPlus will also continue to be supported on Windows Server 2016 until October 2025

 I think the best part of this conversation is he obviously didn't even read what I was asking for and just saw LTSC and started spouting the typical MS BS. My scenario is precisely what LTSC was designed for.