4 ms·
This post recommends LTSC because it has been pre-de-crappified (e.e., no Candy Crush pre-installed). However in January 2020 Microsoft will not support Office
by throw0101a 7y ago
This post recommends LTSC because it has been pre-de-crappified (e.e., no Candy Crush pre-installed).
However in January 2020 Microsoft will not support Office 365 (ProPlus?) on LTSC. This is because the 'official' LTSC use case is for things like medical devices, and not "regular" desktops. It's just that many IT sites got tired of the Windows 10 what-a-mole with non-helpful features, phone home stuff, etc, that they went with the cleaner version.
Doing a quick search, it seems people are saying "just buy Office 2019" to square this circle.
Can anyone comment the pro/cons of using Enterprise LTSC or not?
- jiggawatts 7y agoI'm facing this decision right now. To LTSC or not. I have to build a virtual desktop environment for an isolated network that is almost-but-not-quite a SCADA system. It's the monitoring and management bits, without the direct control. It's not ultra critical, but there's a strict uptime requirement, and a general preference for long-term service releases of everything where possible. Security and prevention of "data leakage" are also very important. Windows 10 just. does. not. work. out of the box as a VDI operating system. It will absolutely massacre your shared storage subsystem (even if it is all flash!) because every now and then it just "decides" on its own that applying a 4GB update to Minecraft is the most important thing in the world right now. For Enterprise editions there's on the order of 200 GPO settings and about 20 PowerShell scripts required to make it "behave", but these settings will break as soon as the next semi-annual release is applied because Microsoft is actively trying to circumvent customer controls over their own environments. For example, did you know that they use deliberately misspelled domain names such as "microsft.com" for telemetry URLs to try and trick hapless firewall admins? This is to work around their desperate customers who resorted to blocking "microsoft.com" in order to prevent the endless torrent of information leakage out of their secure networks. But Microsoft just can't have that. No sir! Got to get that juicy telemetry out, no matter what. I'm waiting for Microsoft to piggy back telemetry on DNS requests or use some other method that is indistinguishable from an Advanced Persistent Threat. It's just a matter of time, mark my words. Check this horror show out: https://docs.microsoft.com/en-us/windows/privacy/manage-windows-1803-endpoints https://docs.microsoft.com/en-gb/windows/privacy/manage-windows-1809-endpoints https://docs.microsoft.com/en-us/windows/privacy/manage-windows-1903-endpoints Notice that the list keeps changing with each release? You also can't block everything in those lists, because then legitimate functions such as Root CA updates will break. Sure, you can override that with a local Root CA update, but the complete workaround procedure for all such services is not documented in any one place, so you're looking at something like 3 months of effort. Enjoy! Or you can just use LTSC and need only about 10 settings and a couple of days... guess which one I went with? Microsoft "suggesting" to their customers that they should use the semi-annual channel is self-serving crap, and I'm not falling for it.
- user5994461 7y agoActually, there were comments on hacker news the other day about the domain, the most likely explanation is that is was too cumbersome to provision new things on microsoft.com so the devs went with what they could get their hands on instead.
- jiggawatts 7y agoYeah I know, but from the perspective of a customer it sounds absurd. Personally I'm fed up with single entities such as Microsoft using TLDs for every damned thing, it makes it very hard to identify what is and isn't legitimate traffic. It also makes it borderline impossible to configure "whitelisting" firewalls or proxy servers. I got to wonder what fraction of this is incompetence ("we can't use our own domain because of bureaucracy") and what fraction is deliberate ("everyone has blocked microsoft.com so we used something else")...
- LilBytes 7y agoWhich is ludicrous in it's self that they set entirely new domains rather than using a sub-domain with delegated access. But, we know how Microsoft works. That would require some kind of communication between departments and delegated trust.
- charwalker 7y agoIf you can afford it, it may be very helpful. However, it does have specific requirements for licensing and possibly missing components necessary for your applications or that Vendors will assume you have for theirs...
- throw0101a 7y ago> I'm waiting for Microsoft to piggy back telemetry on DNS requests or use some other method that is indistinguishable from an Advanced Persistent Threat. It's just a matter of time, mark my words. Wait until DNS-over-HTTPS (DoH) takes off so it will be impossible to have any visibility into the track. Paul Vixie, no DNS dummy he, thinks DoH is really, really dumb and is totally against it AFAICT. He's okay with DNS-over-TLS because it's a more service specific protocol and not piggybacking over something else.
- jftuga 7y agoOffice 2019 can be installed on LTSC.
- xtiansimon 7y agothis is very informative. I work in a small accounting office (<10) and our main software is only available on Windows. In addition to this, all we use is Office 365 (Excel and Outlook) and browsers. It’s an ongoing problem to keep these bog-simple machines running smoothly. Constantly slowing down, and under performing. What’s more—IT is the person who knows the most. I imagine it’s the same for many small businesses. I hoped LTS was a solution. Evidently, to the detriment of users, MS wants one option (and all the telemetry. Haha.)