Windows Server Essentials Remote Desktop Services



Windows Server Essentials Remote Desktop Services

The Remote Desktop Gateway RDG role enables you to access your RDS environment remotely over 443. RDS Architecture. VBoring Blog Series: Setup Remote Desktop Services in Windows Server 2012 R2. 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:

  1. Open local computer certificates MMC snap-in, by running the certlm.msc command;
  2. Go to the following certificate section: Remote Desktop > Certificates;
  3. Right click your self-signed certificate RDP cert and delete it (if there are several RDP certs, remove them all);
  4. 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:

Desktop

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).

  1. 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;
  2. 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;
  3. 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;
  4. 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)
-->

Applies To: Windows Server 2016 Essentials, Windows Server 2012 R2 Essentials, Windows Server 2012 Essentials

Windows

There are multiple ways to access resources that are located on the server when you are away from your network if Anywhere Access functionalities (Remote Web Access, virtual private network, and DirectAccess) are configured on the server.

The following topics can help you access your server resources remotely:

Note Roblox studios download for mac.

For information about configuring Anywhere Access on your server, see Manage Anywhere Access.

Use Remote Web Access in Windows Server Essentials

Remote Web Access helps you stay connected to your Windows Server Essentials network when you are away. For more information, see the topic Use Remote Web Access.

Use VPN to connect to Windows Server Essentials

If you have a client computer that is set up with network accounts that can be used to connect to a hosted server running Windows Server Essentials through a VPN connection, all the newly created user accounts on the hosted server must use VPN to log on to the client computer for the first time. Complete the following procedure from the client computer that is connected to the server.

To use VPN to remotely access server resources

  1. Press Ctrl + Alt + Delete on the client computer.

  2. Click Switch User on the logon screen.

  3. Click the network logon icon on the bottom right corner of the screen.

  4. Log on to the Windows Server Essentials network by using your network user name and password.

Use the My Server app to connect to Windows Server Essentials

The My Server app lets you connect to resources and perform light administrative tasks on your Windows Server Essentials server from your Windows-based PC, laptop, or Surface device. If your server is running Windows Server 2012, download the original My Server app from Apps for Windows. If your server is running Windows Server Essentials, you must download the My Server 2012 R2 app instead.

With the expanded My Server 2012 R2 app, you can connect to the server or client computers by using Remote Desktop. If your Windows Server Essentials server is integrated with Microsoft 365, and your subscription includes SharePoint Online, you also can work with documents in your SharePoint Online libraries and open your SharePoint team sites from My Server 2012 R2.

For information about installing and using these apps, see Use the My Server App.

For information about installing and using these apps, see Use the My Server App.

Use the My Server app for Windows Phone

The My Server Windows app for Windows Phone (for Windows Server 2012) and the My Server 2012 R2 app for Windows Phone (for Windows Server Essentials) are designed to help you stay seamlessly connected to your servers through smart phones while working at remote locations. This is one of the various ways to access Windows Server Essentials after you configure your server for remote access.

Windows Server Essentials Remote Desktop Services License

You can download either app from the Windows Phone store:

  • For more information about the My Server phone app, see the blog entry My Server phone app for Windows Server Essentials. For more information about the My Server 2012 R2 phone app, see the blog entry My Server 2012 R2 Windows and Windows Phone apps.

Use Microsoft 365 with Windows Server Essentials

Microsoft 365 is an easy-to-use set of web-enabled tools that let you access your email, important documents, contacts, and calendar from almost anywhere and any device. For more information, see the Quick Start Guide to Using Microsoft 365.

Remote Desktop Services Windows 10

Desktop

See also