First, I have been supporting Microsft since Win 3.1 and NT 3.1, I am stating I am one of your longtime engineers and hope you will take my suggestion into consideration.

As an Administrator I access a lot of different areas that users do not. These areas are critical to my day to day oerations and help me keep your products in a good light. Recently, you have removed the control panel and our work arounds get removed with each update. As an engineer I realize that these tools are totally unecessary for the standard user, but critical to me.

What I am asking as a near 30 year supporter\administrator\engineer, is that you consider making a custom GUI install for engineers. One that keeps our tools where we need them at and are used to. Speed and accuracy are very crucial, and when you all move these tools around to make things look pretty and exciting for end users, it makes life horrific for us.

A great example was a few years back when I worked on my first server 2012 I was at a clients office with an emergency and the shutdown restart was hidden in charms. I looked like a complete idiot that I could not figure out how to shutdown or restart the server. I had to pull the power plug, real professional. We lost that client due to that situation.

With these tools there are some fine tuning and updating that also needs to be addressed. A great example is the DHCP panel, everytime I have opened this tool in all my years it never remembers its settings, and although you have a single or AD integrated DHCP server I have to manually pick and connect to it. The I have to strectch all the areas out appropriatly to be able to use the tool. There are other applications that are the same way and it would be nice to have them updated also.

What I am trying to be nice about is I along with many of my era engineers would like for Microsoft to acknowledge our importance and to work with us to be able to provide the best support we can. Evertime you move, take away or change our tools you cripple us, and that cripples your reputation.

Please take a minute to work with us, your life long dedicated engineers that promote and support your many servers OS'/Application and desktops OS's. I have given you almost 30 years, please work with me/us to make our lives easier and our users and mangement far more happy with your products.

Thanks
Matt

Hello,

I want to report one issue that is easy to reproduce, it occurs with any rdp client that connects to Windows10 Pro with enabled RDP connections, actually used mstsc.exe to connect from one Windows10 pro machine to another Windows10 pro machine with enabled RDP.

After ~100 tries to restore interrupted connection the server refuses future rdp connection tries with internal error occurred message reported by mstsc.exe.

It doesn't matter if you have logged off the session during running, as example did 20 connection restorings then logged off, logged in and did next 80 connection restorings, that was only example, only what matters is that you have only to restore any interrupted session at least ~100 times to send server to nirvana. As example after WiFi lost connection or during any network problem that requires rdp connection restoring. Only what helps to restore functionality is to restart remote desktop service in services.msc

I highly assume by restoring connection with reconnection cookie the bug counter counts up and by reaching 100 (the counter seems to be not reset by any action) so finally it completely stops to accept any future connections with internal error occurred message.

Such error doesn't exist on Windows2016 but Windows10 pro is affected.

More over few months ago this bug didn't exist on Windows10 too.

Please forward this issue to your RDP server developers, thank you!

Sincerely yours.

I manage a PC that runs Broadcast Software International's Simian application in production 24/7 for a radio station. It is royally impossible to manage the PC via mstsc which reports "An Internal Error Occurred." There is a VPN involved provided by WatchGuard's appliance. The VPN is NOT the problem. Remote Desktop works for the brother PC that also runs Windows 7 with University of Kansas's Telephone Reader application in production 24/7. My hypothesis is that the broadcast-quality sound card is being accessed, with catastrophic results, by the server part of RDP in Windows 7 even in the case where I configure the setup to not send sound across the Internet. There is also an odd log entry in the System log entries. I have been asking Microsoft to fix this defect for one full year. Microsoft is busy rolling out Windows 10 releases in accord with the DevOps philosophy (sometimes referred to as a methodology). Just a message from one one thousandth of one percent of Windows users worldwide. In closing, I use UltraVNC which provides the remote desktop functionality that Microsoft, the World's Premiere maker of consumer operating systems, does not.