How to Configure Remote Desktop in Windows Server 2008 R2 step by step
Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Set up the Remote Desktop web client for your users
In this articleThe Remote Desktop web client lets users access your organization's Remote Desktop infrastructure through a compatible web browser. They'll be able to interact with remote apps or desktops like they would with a local PC no matter where they are. Once you set up your Remote Desktop web client, all your users need to get started is the URL where they can access the client, their credentials, and a supported web browser. What you'll need to set up the web clientBefore getting started, keep the following things in mind:
Your users will see better performance connecting to Windows Server 2016 (or later) and Windows 10 (version 1611 or later). Important If you used the web client during the preview period and installed a version prior to 1.0.0, you must first uninstall the old client before moving to the new version. If you receive an error that says "The web client was installed using an older version of RDWebClientManagement and must first be removed before deploying the new version," follow these steps:
How to publish the Remote Desktop web clientTo install the web client for the first time, follow these steps:
Note To see a list of all supported cmdlets for the RDWebClientManagement module, run the following cmdlet in PowerShell:
How to update the Remote Desktop web clientWhen a new version of the Remote Desktop web client is available, follow these steps to update the deployment with the new client:
How to uninstall the Remote Desktop web clientTo remove all traces of the web client, follow these steps:
How to install the Remote Desktop web client without an internet connectionFollow these steps to deploy the web client to an RD Web Access server that doesn't have an internet connection. Note Installing without an internet connection is available in version 1.0.1 and above of the RDWebClientManagement PowerShell module. Note You still need an admin PC with internet access to download the necessary files before transferring them to the offline server. Note The end-user PC needs an internet connection for now. This will be addressed in a future release of the client to provide a complete offline scenario. From a device with internet access
From the RD Web Access serverFollow the instructions under How to publish the Remote Desktop web client, replacing steps 4 and 5 with the following.
Connecting to RD Broker without RD Gateway in Windows Server 2019This section describes how to enable a web client connection to an RD Broker without an RD Gateway in Windows Server 2019. Setting up the RD Broker serverFollow these steps if there is no certificate bound to the RD Broker server
Follow these steps if there is a certificate previously bound to the RD Broker server
Setting up the RD Session HostFollow these steps if the RD Session Host server is different from the RD Broker server:
General Observations
How to pre-configure settings for Remote Desktop web client usersThis section will tell you how to use PowerShell to configure settings for your Remote Desktop web client deployment. These PowerShell cmdlets control a user's ability to change settings based on your organization's security concerns or intended workflow. The following settings are all located in the Settings side panel of the web client. Suppress telemetryBy default, users may choose to enable or disable collection of telemetry data that is sent to Microsoft. For information about the telemetry data Microsoft collects, please refer to our Privacy Statement via the link in the About side panel. As an administrator, you can choose to suppress telemetry collection for your deployment using the following PowerShell cmdlet:
By default, the user may select to enable or disable telemetry. A boolean value $false will match the default client behavior. A boolean value $true disables telemetry and restricts the user from enabling telemetry. Remote resource launch methodNote This setting currently only works with the RDS web client, not the Azure Virtual Desktop web client. By default, users may choose to launch remote resources (1) in the browser or (2) by downloading an .rdp file to handle with another client installed on their machine. As an administrator, you can choose to restrict the remote resource launch method for your deployment with the following PowerShell command:
By default, the user may select either launch method. A boolean value $true will force the user to launch resources in the browser. A boolean value $false will force the user to launch resources by downloading an .rdp file to handle with a locally installed RDP client. Reset RDWebClientDeploymentSetting configurations to defaultTo reset a deployment-level web client setting to the default configuration, run the following PowerShell cmdlet and use the -name parameter to specify the setting you want to reset:
TroubleshootingIf a user reports any of the following issues when opening the web client for the first time, the following sections will tell you what to do to fix them. What to do if the user's browser shows a security warning when they try to access the web clientThe RD Web Access role might not be using a trusted certificate. Make sure the RD Web Access role is configured with a publicly trusted certificate. If that doesn't work, your server name in the web client URL might not match the name provided by the RD Web certificate. Make sure your URL uses the FQDN of the server hosting the RD Web role. What to do if the user can't connect to a resource with the web client even though they can see the items under All ResourcesIf the user reports that they can't connect with the web client even though they can see the resources listed, check the following things:
If the user gets an "unexpected server authentication certificate was received" error message when they try to connect, then the message will show the certificate's thumbprint. Search the RD Broker server's certificate manager using that thumbprint to find the right certificate. Verify that the certificate is configured to be used for the RD Broker role in the Remote Desktop deployment properties page. After making sure the certificate hasn't expired, copy the certificate in .cer file format to the RD Web Access server and run the following command on the RD Web Access server with the bracketed value replaced by the certificate's file path:
Diagnose issues with the console logIf you can't solve the issue based on the troubleshooting instructions in this article, you can try to diagnose the source of the problem yourself by watching the console log in the browser. The web client provides a method for recording the browser console log activity while using the web client to help diagnose issues.
The console may also be accessed directly through your browser. The console is generally located under the developer tools. For example, you can access the log in Microsoft Edge by pressing the F12 key, or by selecting the ellipsis, then navigating to More tools > Developer Tools. Get help with the web clientIf you've encountered an issue that can't be solved by the information in this article, you can report it on the Azure Virtual Desktop forum of Microsoft Tech Community. FeedbackSubmit and view feedback for How do I setup Remote Desktop on Windows Server 2008?Enable Windows Server 2008 R2 Remote Desktop Services. On the Windows ® Server 2008 R2 computer, click Start > Administrative Tools > Server Manager. ... . Click Roles, and then click Add Roles. ... . Select Remote Desktop Services, and then click Next. ... . Select the Remote Desktop Session Host and Remote Desktop Licensing check boxes.. What is the correct procedure in configuring Remote Desktop in Windows Server 2008 R2?How to configure Remote Desktop in Windows Server 2008 R2 step by.... Step 1: Begin the installation. ... . Step 2: Select Remote Desktop Services roles you want to install. ... . Step 3: Pick the license mode. ... . Step 4: Allow access to Remote Desktop Session Host (not required) ... . Step 5: Configure the client experience.. How do I setup a Remote Desktop server?Use Remote Desktop to connect to the PC you set up: On your local Windows PC: In the search box on the taskbar, type Remote Desktop Connection, and then select Remote Desktop Connection. In Remote Desktop Connection, type the name of the PC you want to connect to (from Step 1), and then select Connect.
What are the 6 components of Remote Desktop Services?In this article. Remote Desktop Session Host.. Remote Desktop Connection Broker.. Remote Desktop Gateway.. Remote Desktop Web Access.. Remote Desktop Licensing.. |