Windows Server Essentials Remote Desktop Services

Installing Remote Desktop Services (RDS) on Windows Server 2019 appears to take many steps, but in reality is quite easy. In this article, we dive into how to install these services in a domain environment that requires two servers. Go to the following certificate section: Remote Desktop Certificates; Right click your self-signed certificate RDP cert and delete it (if there are several RDP certs, remove them all); Restart the Remote Desktop Services as described above. You can try to change the maximum outstanding connections limit on your RDP server via the registry. Troubleshooting VPN connections on a Windows 10 Pro to Windows Server 2016 Essentials Anywhere Access. A VPN connection on a Windows 10 Pro to a Windows Server 2016 Essentials will fail with 'the remote connection was denied or the selected authentication protocol was not correct. September 20, 2016 Jared 0 Comments 2012, 7000, 7041, 87, Essentials, Event, Fail, MediaAdmin$, Microsoft, R2, Server, ServerAdmin$, Windows When configuring the Windows Server Essentials role on Windows Server 2012 R2, the configuration may fail right away, or after 87%. Remote Desktop Gateway (RD Gateway) grants users on public networks access to Windows desktops and applications hosted in Microsoft Azure's cloud services. The RD Gateway component uses Secure Sockets Layer (SSL) to encrypt the communications channel between clients and the server.

In some cases, when connecting to remote computers/RDS server via RDP, users may encounter an “An internal error has occurred” error. This error may appear due to various reasons related to both the settings of the RDP/RDS server and the client (Windows settings, or settings in the Remote Desktop Connection window).

The error “An internal error has occurred” usually appears after user credentials is entered in the mstsc.exe window or immediately after clicking the Connect button.

Since there may be several causes for this RDP error, try to use the following tips one by one until you find a solution that helps you.

The easiest way to fix the problem is to reboot the remote RDP/RDS server and your computer from which you are establishing RDP connection. If you cannot restart the server right now, you should try to restart the Remote Desktop Service. You can do this with the following commands running in the elevated cmd.exe:

Or you can restart Remote Desktop Services from the services.msc console.

Open the properties of your RDP connection in Remote Desktop Connection windows and make sure the ‘Reconnect if the connection is dropped‘ option is enabled on the Experience tab

READ ALSOUsing RDCMan to Manage Multiple RDP sessions

Next, try to recreate the RDP certificate:

Open local computer certificates MMC snap-in, by running the certlm.msc command;
Go to the following certificate section: Remote Desktop > Certificates;
Right click your self-signed certificate RDP cert and delete it (if there are several RDP certs, remove them all);
Restart the Remote Desktop Services as described above.

You can try to change the maximum outstanding connections limit on your RDP server via the registry. Set the following registry value via regedit.exe:

Or with PowerShell:

Check the current MTU size oy your Windows with the command:

If the current MTU size for your network interface is equal or more than 1500 (default Windows value), reduce it by using the command:

Try to change some Group Policy setting using the Local GPO editor (gpedit.msc) or domain Group Policy Management Console (gpmc.msc).

Disable UDP protocol for RDP connection on clent side: Computer configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client > Turn Off UDP on Client = Enabled;
Enable FIPS compliant algorithms: Computer configuration > Windows Settings > Security Settings > Local Policies > Security Options > System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing = Enabled;
Disable the hardware encoding and enforced AVC:444 mode on the RDP server side: Computer configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Prioritize H.264/AVC 444 Graphics mode for Remote Desktop Connection = Disabled;
Try to change the RDP security level to RDP mode (use the policy ‘Require use of specific security layer for remote connections’ according to the

After changing the policy settings, you need to apply them on the client and server using the

READ ALSOHow to Add User to Remote Desktop Group?

Now check that your RDP client connects without errors.

AuthorRecent PostsCyril KardashevskyI enjoy technology and developing websites. Since 2012 I'm running a few of my own websites, and share useful content on gadgets, PC administration and website promotion.Latest posts by Cyril Kardashevsky (see all)

On September 5, 2018 the Microsoft Windows Server Team announced via theWindows Server Blog that they are killing off Windows Server Essentials as it currently exists today:

While Microsoft will still be releasing an “Essentials” SKU for Windows Server 2019, it will be completely devoid of everything that we recognize as being part of Windows Server Essentials in its current form. Small Business Server MVP Robert Pearman summarizes the upcoming release of Windows Server 2019 Essentials as follows:

“With the release of Server 2019 Essentials, the end of an era has been reached. Gone are the wizards and tools designed for the small business owner.

Gone is the Remote Web Access feature.

Gone is the Essentials Connector.

Gone is Client PC Backup.

Gone is Office 365 Integration.

Gone, is the Dashboard.

Windows Server Remote Desktop Service

Gone, indeed, is the Essentials Role.

All that remains of Essentials, is the name Essentials and the licensing limits of the Essentials SKU, of 25 client access licenses.

What we are presented with, is now more in line with Windows foundation server from several years ago.“

Basically, Microsoft is releasing their first (and last) non-essentials Windows Server Essentials release that is completely gutted of anything even remotely resembling Windows Server Essentials as we currently know it. And obviously, without the underlying “Essentials” bits, there can be no more new WSE RemoteApp or WSE WorkFolders product releases going forward.

It’s been a fun run, but we have indeed now come to the end of an era for Windows Server Essentials.

My suggestion to those who want to continue running an on-premises Essentials server would be to grab up as many Windows Server 2016 (Standard, Datacenter, or Essentials) licenses as you possibly can (before they’re all gone), and then ride it out with that particular version for as long as Microsoft will be providing support for it (see: Windows Server 2016 Essentials servicing timeline).

Le Roi Est Mort, Vive Le Roi!

UPDATE #1: It’s quite obvious that Microsoft wants small businesses to dump Windows Server Essentials and move to the(ir) cloud, but personally, I don’t want my business (nor personal) data on anyone’s cloud. See:
US-CERT – Common Risks of Using Business Apps in the Cloud

UPDATE #2: Fear not, as all may not be lost after all… See:
Installing Windows Server Essentials Experience On Windows server 2019 / 2022

Comments are closed.