Oh, this sounds really bad if true. Do you know why Microsoft decided not to release GUI version.. are they dropping Desktop Experience completely for new Windows Server releases? Don't they realize how many users this will inconvenience? There was a good reason for it to exist in the first place. Windows isn't always meant to be used as Linux, sometimes Windows Server is chosen because it feels familiar to administrators who aren't used to work with headless OS. You can't know all of this, rather; do you know any MS publication where they explain their motives? And most importantly (for me): is there any way to get around this problem? I just located this post now: https://forums.mydigitallife.net/th...r-2019-build-17763.78021/page-33#post-1529725 But i cannot find the tutorial it refers to, as it states: "You can make it yourself by adding the client GUI packages to Windows Server v1903 Core edition" Perhaps, alternatively, anyone can summarize the procedure, or provide a finished image that integrates GUI? Also I really doubt if it's true (or relevant to the quest of finding a new ISO) to begin with, since, in line with my original story, I also cannot find an ISO of Server 2019 version 1903 that is not GUI/desktop experience; also the Microsoft evaluation center issues only build 1809 there. It still gives me this sense of failed roll-out of "public available 1903" The supposedly "headless" ISO that is being issued: 17763.379.190312-0539.rs5_release_svc_refresh_SERVERESSENTIALS_OEM_x64FR.iso for the non-GUI version
Here's the rundown: Only Server LTSC versions have the GUI. The semi-annual releases are always Core-only. GUI is not dropped completely, just restricted to LTSC. The Server versions using years (2016, 2019, ...) are the one with GUI. The others are named after the client counterparts (Server 1903, ...) and are Core releases.
Does anyone that is more familiar with Microsoft policy on Windows Server know if we can expect a LTSC / GUI version of build 1903 in the near future, or at all? There may not be any experience with this kind of policy, since the whole core & GUI server split hasn't happened with most releases in the past. It's something of recent times (2016 & 2019).. Personally I am really disappointed that, having specific needs for the GUI version, I cannot benefit from new features 1903 brings. Again, as I mentioned someone on MDL (@MSMG at https://forums.mydigitallife.net/th...r-2019-build-17763.78021/page-33#post-1529725) described the possibility to merge one and one together and still get a 1903 GUI build; can anyone provide details on how to achieve that, or help me do that? It would still be very welcome. Thanks for enlightening me about the situation though, @ here
There will be NO official Server 1903 with a GUI, ever. Next LTSC is expected around 2021/2022. Note that building a Server 1903 with added GUI creates a Frankenbuild. You can expect some problems with updating down the road, as MS does not expect 1903 Server to have any GUI.
one could probably install one of the explorer alternatives, and desktop app like stardock, but that would be a strange system
Is the following true? 1. Retail Edition with "2019" in the name is SAC(?) but has GUI: en_windows_server_2019_updated_march_2019_x64_dvd_2ae967ab.iso en_windows_server_2019_updated_aug_2019_x64_dvd_cdf24600.iso 2. Retail Edition with "1809", "1903" in the name is SAC and is CORE only: (*): en_windows_server_version_1809_updated_march_2019_x64_dvd_7aa55a22.iso (**): en_windows_server_version_1903_updated_aug_2019_x64_dvd_d0c9413d.iso Btw, is (**) the updated version of (*) or are they two different server versions of different channels? 3. Volume Edition - is LTSC and has GUI, only has one release in Nov 2018 and will never have another fresh updated ISO: SW_DVD9_Win_Server_STD_CORE_2019_64Bit_English_DC_STD_MLF_X21-96581.iso
en_windows_server_version_1809 = 17763 SAC = Core only = Retail + Volume en_windows_server_2019 = 17763 LTSC = Core/GUI = Retail + Volume each SAC version is separate build
Thanks! I took some more time to search and was finally able to write out these notes. There are two versions of Windows Server: 1. Long-Term Servicing Channel (LTSC): Windows Server 2016, 2019 etc., which is actually a new build of traditional Windows Server. Includes GUI Refreshed ISO contains only security and non-security updates, NO new features and functionality Released in 2 editions: Retail through MSDN; Volume or VL via VLSC. For example, for "2019 Update 2019-03 build 17763.379": MSDN Retail: en_windows_server_2019_updated_march_2019_x64_dvd_2ae967ab.iso VLSC Volume: SW_DVD9_Win_Server_STD_CORE_2019_1809.1_64Bit_English_DC_STD_MLF_X22-02970_2.ISO 2. Semi-Annual Channel (SAC): Windows Server version 1709, 1809, 1903 etc., is the new generation of Windows Server without a graphical user interface. NO GUI, Core only Refreshed ISO is actually newly released ISO, contains security updates, new features and functionality. Released in one edition (i.e. same hashsum) on both MSDN and VLSC, but may have different names. For example, these following names point to the same ISO of "1809 Update 2019-03 build 17763.379": MSDN Name: en_windows_server_version_1809_updated_march_2019_x64_dvd_7aa55a22.iso VLSC Name: SW_DVD9_Win_Server_STD_CORE_1809.1_64Bit_English_DC_STD_MLF_X22-03530_2.iso
Thanks for clearing it up and making it overviewable! I really hope that one day Microsoft will de-complicate the process and just release all editions (i mean both Core and GUI) for any major update. They gotta understand that while there are sysops that like headless environments (sometimes making the jump from Linux) there will always equally be people that want (or really need) the classic GUI experience, and that this group of people deserve the same pace of major updates. I am personally afraid of the day that MS completely abolishes the GUI version, which will result in people like myself never upgrading away from older builds, due to preference. Microsoft has clearly started valuing sysops that like bare environment over those that do not. Less updates is just the beginning. They should value all of their professional customers equally.