4/21/2023 0 Comments Ltsb windowsAs a company they’re an order of magnitude bigger than the likes of Citrix and VMware, so it might be unfair to expect them to respond in the same way those two would, but I think the reason they won’t engage in this way is that either a) no-one can really answer the questions we’re asking, much like the problem you have when talking licensing, or b) no-one wants to take responsibility for putting an official line on something that could change pretty quickly. But I don’t know what it says about Microsoft that they are so difficult to get community engagement from in this way. It’s a shame we can’t get anyone from Microsoft directly to join in on these things, but Aaron and Simon in particular are very clued-in Microsoft guys so they gave us some excellent insight. In this instance, they were as good as their word, so we had a good discussion on this subject last night. So when I was challenged again about it, I was a little bit snappy about it and invited the commenters to a discussion around it. The first time this happened I asked the commenter if they’d mind taking some questions from me about this to justify their stance, but I never received a reply from them. After publishing this, I seemed to attract comments from some people on Twitter along the lines of “you’re doing it wrong, no-one should use LTSB”. I penned an article recently over on the AppSense (now Ivanti, of course) blog which went into a discussion of the relative merits of Windows 10’s two main servicing branches, Current Branch for Business (CBB), and Long-Term Servicing Branch (LTSB).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |