Windows Server, version 1709 Code: 4f413236ef3d47efaf61cdd3e33b3f6ab8944718 *cn_windows_server_version_1709_x64_dvd_100090901.iso 9ad071f33b60728ad99536aa5172b7c084c37f9c *cs_windows_server_version_1709_x64_dvd_100090905.iso 1824cf8404a31c6afebbcf3f16c9ebd8c19dadd0 *ct_windows_server_version_1709_x64_dvd_100090899.iso d0783a1ed3ffa3e6c53ffe4f46c45b32f92b653a *de_windows_server_version_1709_x64_dvd_100090898.iso 9b901a2ce6a8e126496efb0d2440c0187fe614b8 *en_windows_server_version_1709_x64_dvd_100090904.iso 2e1dd7f9da53b16c3d56b627e3943c82045ba041 *es_windows_server_version_1709_x64_dvd_100090885.iso 42d61151247be36602893455b34b7660c9e19e85 *fr_windows_server_version_1709_x64_dvd_100090897.iso d8bfcbaca26a2706e56628f3c7c628d4eb598b21 *hu_windows_server_version_1709_x64_dvd_100090768.iso 6775abc61bc96d064af35d36d81c3fab3a204925 *it_windows_server_version_1709_x64_dvd_100090900.iso 2f0bb8cb987ccf49d0a4fa3294eb906a6e5fd3fa *ja_windows_server_version_1709_x64_dvd_100090902.iso b767d7aad62e61700d0c463b06320365505bdd80 *ko_windows_server_version_1709_x64_dvd_100090769.iso b73b292bd7f8d12b973fc0e05c55e33a1ce1c8ee *nl_windows_server_version_1709_x64_dvd_100090892.iso 687950cd447ef6030bcc7ba333bace9316bd0adb *pl_windows_server_version_1709_x64_dvd_100090772.iso f8310cd50e42dca0ec2cf133a5627a0b6b543d78 *pp_windows_server_version_1709_x64_dvd_100090886.iso 6d705ad3ae3dadcde14e8b58dfae146f859b1cb5 *pt_windows_server_version_1709_x64_dvd_100090903.iso 9a8fbd16362a309f878cbcf95b694ffaa83c6c51 *ru_windows_server_version_1709_x64_dvd_100090907.iso ad45e21639eb13b6031385bad104553c163b020b *sv_windows_server_version_1709_x64_dvd_100090884.iso 15e2400b99519f42161abadb58cae581587bcada *tr_windows_server_version_1709_x64_dvd_100090894.iso
So the WZOR release was 16299.0, is the MSDN one 16299.15 based? I would check but got about 100 files in the download queue at the moment Whats interesting is the note on MSDN (my visualstudio) states that 1709 requires active SA, and requires new product keys (MAK type) so I guess VL only.
the datacentercore iso also no GUI so I don't think any GUI version for us going forward unless a lot of complaints to microsoft - they really don't want us using server 2016 as desktop in place of windows 10
The GUI is part of Windows Server 2016's Long Term Service Branch (LTSB) None of the in between updates will have a GUI. Learn some PowerShell or move to Linux.
Yeah this kinda sucks that the departments don't seem to communicate or plan together. I wonder how the Exchange team plan to address this going forward? Probably a way to temp you to move to there hosted offerings. I don't really think games servers are the target audience. Most of the built in roles can be managed from you Windows 10 management workstation using RSAT (much like previous versions). This move really pushes towards remote management. From a server perspective this is a good move. Also since you move your management to local tools managing remote server, you also a step closer to the remote server been hosted on Azure etc. which is really where they are heading. A minimalist core server may seem annoying but it's good from a security perspective. Reduced attack surface, resources.
Yeah that won't work cause most processes won't run without a gui. also linux isn't an option as most processes are unusable especially game servers as they hate running in wine due to not using native windows extensions.
Really? I disagree. Server roles run just fine without GUI using RSAT. I think you need to learn to use the OS properly instead of moaning about it. Maybe the developers should write PROPER server apps instead of you trying to run them under a partial emulator.
I wasn't on about the server roles themselves... I was on about 3rd party services. Most are unusable cause they refuse to run.