The positive side to my waiting for the new LTSC, is that I took the time to install, Linux Mint, as a temporary OS. I must admit, this OS is awesome. I got my games to work after watching a Linus video on YouTube. Additionally, to my surprise, I even had two games in my Steam library that had native support. It now brings up the question for me, do I need LTSC for a lightweight OS? Anyhow, I’ll continue to check here for the latest release, but I am mad that I didn’t try Linux Mint before. I also learned in the past few hours about, Pop!_OS. I may give that a try as I continue to wait.
The main reason is Outlook, you will have a hell of a time to configure your accounts if you`re on GMail, you`ll have to disable the automatic configuration, even after that the mail stops synchronizing randomly for no reason. I had to use Thunderbird as a replacement and LibreOffice until LTSC comes out.
Well for me it`s W10 LTSC until W11 LTSC comes out and nothing else. If not then I might switch to Linux indefinitely.
Regular Windows IOT Enterprise (without LTSC) is just like regular Windows with all the bloat that nobody wants. Only LTSC offers the less bloated experience.
So how is it that no ISOs of IOT LTSC have shown up? Can Microsoft track it back to the OEM that is responsible? As far as i understand the IOT LTSC ISO contains the non-IOT LTSC (or can be switched to it by entering the gvlk key)
I definetly agree. We should also open a fake company, and register as employees, this way we don't need to wait for the leak either, and get it on day-zero via valid ways of course I would be willing to pay for it as well (up to 20$ ) I also wonder about this, maybe this is the reason why it has not been leaked so far. Can you elaborate more on this please?
I used to work for an Embedded OEM, which is slightly different contract with MS than regular OEM. We also got the ISOs and keys quite early. MS can only track if one would leak the key. The ISOs could be spread as much as wanted. Edit: We always got MAK as key for the Iot Enterprise LTSC. During install the key had to be entered. So the behaviour of the installation was the same as today's retail/msdn ISOs for Server 2022 for example.
I think he means if your board has some crappy consumer level chipset (LAN or so) where .inf hacking is necessary to get the drivers installed. If one has a server mainboard for example, you have much smoother experience as all drivers install fine and there's no need for tinkering. I am running a Supermicro X11SSM-F board and there's a big difference in quality of life compared to the ASUS consumer board I had (Z87-PRO).
I meant, if all your software and hardware works fine on server, there's no reason not to use it. For example on my laptop sleep mode is not working which is essential to me, so that's why I am waiting for LTSC.
As we speak I am wondering if a dual socket Xeon motherboard with 128GB RAM on a raid 10 would run better with Server 2022 than LTSC. If it's the case then I might keep the server and not bother with LTSC.
only problem I have with server is the drivers available & including via windows update on LTSC 1908 it just get my VGA driver off windows update on Sever 1908 I have to find them manually install it & maintain it but if someone knows a switch or method to make server be able to use the normal windows update drivers I would love to know ?
Well for the VGA drivers like mine (Radeon Vega 56), all I have to do is get the latest drivers from AMD (the .exe won't install on the server) and then extract the executable and let windows search the folder to install the drivers and voila!
Big if true, but how would one go about doing this? This would solve so many people’s issues, they just need to download IoT LTSC and then activate it