Thank you. To be fair, the LTSC Branch does still really fit our needs though, in that we want the basic OS, which is functional and responsive, to allow Office Applications to run up, and to work in a roaming profile manner. This is why Ive come to the forum, to try and find a good/better/best approach to this. There is a big benefit in not having to revisit the gold image every six months, and all the associated GPO/optimisation which would be necessary at each stage, and just do the necessary security patching, and to have the support for this to run past the 12-18 months per build (as per SAC). Time is always a premium, and if there is any way to minimise the admin effort every six months that would be good. The SAC branch would be optimized right down, with UWP apps removed, and Cortana etc, and Edge, etc..... So you kind of end up with a LTSC build, but with the additional overhead every six months... Both LTSC and SAC are supported as deployed VDI (given the support matrix of what is/isnt by build), so it is really difficult to provide a true/definitive answer to just what is the recommended path. I personally think the MS stance of what LTSC is used for is wrong, it should include devices that are not bleeding edge for feature releases, and require to be a simple/stable platform allowing security patching... but thats just my view on it...
Thank you for you input and the link.
Phil
