We still need a Windows Version for small customers getting easy connection to Azure and Office 365. So do NOT remove the Essential Role out of Version 2019.

You know, Drag & Drop is a useful feature.
It's annoyoing, that RDP does not support Drag & Drop from / to the remote session.

Add native ACME Client v2 to Windows Server and IIS include auto renewal feature.

I currently use a Windows 10 VM with Remote Server Administration Tools to manage our servers (about 3 years running now). Would be super sweet if you put together a version that runs natively on Mac. Super sweet.

Many of your Windows users depend upon DISM repair so I suggest you revert to .WIM. .ESD can convert to .WIM but the level required to do so is above the majority of your users.
Please escalate.

Hi! There is currently no official support for Windows Server 2016 to run ADMT. It remains an important tool and I'm sure many will appreciate not needing to install older versions of Windows to migrate between AD's.

Dear Microsoft Windows Server team. We would like _complete control_ over when we would like our our WS2016 to install windows updates! No more slow / timeconsuming server restarts because of "Getting Windows ready. Do not turn off your computer" messages when we just would like a quick restart of a production server.. No more TiWorker.exe using 100% of a CPU core during "*********" and so on.. And please fix the issues with '2017-08 Update for Windows Server 2016 for x64-based Systems (KB4035631)' asap. Thank you.

It would be very useful and helpful to have better line ending support in Notepad.
Third party software often comes with config files that's origin is from a Linux world and only having LF inside.
Notepad just shows one big line and editing such files is almost impossible.
As WordPad supports LF since years it would be that feature to have notepad.exe be aware of CRLF and LF files.

https://blogs.msdn.microsoft.com/commandline/2017/12/08/cross-post-wsl-interoperability-with-docker/

After upgrading a machine to Windows 10 1803 (build 17115) the Essentials Connector no longer connects to the server, does not run any of the apps and deinstallation/reinstallation including fresh install clearing down registry and ProgramData does not fix it. This will block upgrading my estate to Windows 10 1803 if not fixed urgently. Have also reported back through Feedback App on Windows 10.

Windows Admin Center is fantastic but we all manage a mix of Linux and Windows Servers. Add the ability to add Linux Servers, SSH over the browser, and a few basic items would be phenomenal (process list, disk info, file explorer)

Please post the methods to upgrade Short Term Service Branch Servers. If we are going to be living with these servers for less then 18 months we need to understand the methods for upgrades.

If any .NET version after 4.5.2 is installed, some dashboard functionality fails (can't remove computer, can't ignore alert) and the dashboard crashes randomly. Removing and blocking .NET 4.6.1, 4.7, and 4.7.1 works around the issue, but that means the server is limited to the 4-year-old .NET 4.5.2. This article has more details:

https://www.mcbsys.com/blog/2018/02/essentials-2012-r2-dashboard-fails-with-net-4-6-and-4-7/

When modifying file permissions on a server, it would be a HUGE time saver if you could simply double click the group name and have it open the AD properties of the selected group.

Implementing this saves the time of having to open ADUC, then typing in the group name in search, then make the required group changes.

This is a Windows Server 2016 Verizon or a Windows Server 2012 or 2013, Please Get it now, Because If You Are Still Grounded, Than We Are Not Have This Everything, Also, Go To Your Room, Go To Bad, And Never Ever Ever Get It! I Dont Know Why, Enjoy The Windows Server 2016 Anyway.

DDNS service in Windows Server Essentials needs to support not only IPv4 but also IPv6 address.

Microsoft should strongly consider implementing support for Azure AD join in future builds of Windows Server 2016. I how a couple of customers that have nearly finished the transition to all cloud and is left with a couple of servers due to legacy software. They are currently left with the option to deploy Azure AD Domain Services for supporting a couple (2-5) servers.

I have set up production servers for Intel, and used an R&D and test server to develop new tools and to test configurations before I pushed them to production servers. As such, I needed the GUI tools and the GUI interface. Those machines were my primary work environment every day.

The Server should retain the option to install the GUI, as not every server is a production server.