Forum Discussion
So Windows Server Insiders is only the Core Version. How About Next Month the Full Server Is Avail..
The Semi-annual Channel will release with Server Core and Nano for container runtime. See this doc which discusses:
https://docs.microsoft.com/en-us/windows-server/get-started/semi-annual-channel-overview
A Full desktop experience version is not planned. If this is important for your adoption, this is a great forum to leave that feedback.
Thanks!
Elden
I believe the full version will be coming soon, as it's likely they are trying to solve major bugs before trying release it to public. Some serious issues came a month ago when they accidently released a broken build. I don't think they want to repeat that issue.
Also Microsoft I don't believe is encouraging Core over full editions. But rather if you can run Core you should. This reduces resource usage, reduces attack surfaces, reduces serving requirements, etc.
MicrosoftThe Semi-annual Channel will release with Server Core and Nano for container runtime. See this doc which discusses:
https://docs.microsoft.com/en-us/windows-server/get-started/semi-annual-channel-overview
A Full desktop experience version is not planned. If this is important for your adoption, this is a great forum to leave that feedback.
Thanks!
Elden
Hi Elden,
RDS is the strongest use case for us - the use of Server 2016 to produce a Win10-like experience becomes less valid as the gap between the current release of each widens.
At release Server 2016 dropped support for a number of components that were included by default in Windows 10 (Edge, Store, Cortana) and Windows 10 has continued to see both feature developments (nice to have) and feature improvements/fixes (essential) - changes to Start Menu behaviour is one example.
This recent servicing change is exactly the right thing to do, but it needs to cover the Desktop Experience as well - the "How it works" diagram on the blog explaining this change indicates that the vNext LTSC release is TBD, but drawn in somewhere beyond the start of 2019.
IMHO, there's a very large group of user base with a shallow-to-deep dependence on a GUI (within which RDS alone has to be a substantial number).
Excluding the Server with Desktop Experience means that RDS user groups will be on a platform which was missing components at the start, has faults which are already fixed in Win10 and won't see changes until 3 years later (that's conceivably 6 releases behind the Win10 codebase).
The RDS user base has always been serviced on the same timeframe or a little behind the traditional client user base. This model seems a *very* long way from that experience. At a point where remote working ought to be going up, the RDS platform will seem to have been sidelined.
I don't see many talking about that right now (I think because a greater bulk of those groups are just jumping to Server 2016 around now), but I don't think it will be long before they notice the shortcomings in the current release and start asking.
Thanks
Matthew
To layer intrigue on RDS intrigue - Windows Server 2019 TP doesn't actually include the RDS session host role.
No RDS in the future then?
- Something is coming. We have to be patient!
I have a standalone (home) server/workstation that I manage directly on the hardware with a GUI, but it's also not really a 'production' server so I was really looking forward to trying out insider builds.
I'm perfectly okay with Server Core being the default install, but the GUI isn't even included in the sources\install.wim, and can't be installed afterward, so that's a dealbreaker for me.- Just read this, I do think it may be important later down the road but not critical.
I do however find this could be considered critical for certain products that may rely on the Desktop component. Unless Microsoft plans to restructure the dependency issues that can come from not having the package included.
To avoid confusion, do you mean that the desktop component is being stripped from Server 2016 in the near future? Or just for this insiders test? Thanks Elden, I don't personally have an issue with using server core, however in the past there were always small things that would pop up that I couldn't do on the core box. I am pretty sure most of these things can now be done with powershell or cmd now. If not I'll run into them pretty soon and I will post here, however, I was thinking about my friends and coworkers who are not as nice with powershell as I am. Also I know lots of guys myself included that like to run Server with a gui on one or two of our laptops and desktops, now we will have to use Hyper-V Core and run Windows 10 for audio, video, and other necessary functions on a laptop running server. Sometimes it's nice to be able to get all the functions and features of windows 10 on a server version, since it eliminates a lot of the unnecessary cruft like MAPS, and all the UWP services shoved into Windows 10. Even the Server with a desktop version of 2016 had the Maps and Xbox services, but at least they weren't really doing anything. It would be nice to see a server 2016 version of all the new security updates and features that windows 10 now has. I hope you can understand why people would still want the GUI.
