Remote Desktop Internet Explorer


How to Access Windows Remote Desktop Over the Internet from PC and Cell Phone.How to Configure a DLink Router for Remote Desktop.

  1. The next time you connect, you can save yourself the time of opening Remote Desktop Connection by opening the right-click menu for the computer to which you want to connect, in the Network pane from File/Windows Explorer, and then click or tap on “Connect with Remote Desktop Connection.”.
  2. Both Internet Explorer 11 and Microsoft Edge would see this and happily start up a new remote desktop session. However now those times are over. IE11 is quickly fading away with no replacement planned. The original MS Edge is being replace with Chromium-based MS Edge.
Remote desktop internet explorer app

Hello World,

We are again speaking about Remote Desktop services in Windows 2012 R2. The journey is almost complete for this first serie. In my current assignment, we had to develop a concept where applications would be centralized and would have been offered as remoteapp applications. This was an interesting project. During this project, a lot of users (and managers) were complaining about the fact that you needed to login to the web page in order to access the applications offered.

So, the customer asked us if it was possible to have a Single Sign on (SSO) experience by enabling Windows Integrated authentication (WIA) capability. We had to look a little bit about that and we quickly found out that this case scenario was foreseen by Microsoft. By modifying the IIS configuration and some web config file, we could easily achieve our goal.

This post will walk you through the process of enabling Windows Authentication Integration mechanism with RDS.

Step by Step Process


In this post, we assume that you have followed the steps described in the previous posts related to RDS

The scenario described hereafter make sense when you have corporate users that needs to access your RemoteApp service. We assume that the users haved logged on into their corporate workstation (i.e. part of the Active Directory Domain) and that these users will be able to access their remoteapp application without being prompted for credentials or redirected to a login web page.

Step 1 – Configure IIS to support Windows Authentication method

We will first need to configure the IIS server to support the Windows Authentication method. To perform this configuration change, you will execute the following steps

  • Login into the Remote Web Access server (RWeb)
  • Open the run command or search command and type inetmgr.msc
  • The Internet Information services console open
  • In the left menu, expand sites and select the RDWeb Site
  • in the mid pane, click on authentication icon.
Remote desktop internet explorer

Click on Picture for better Resolution

In the authentication page, you will see something like this. Notice that the windows authentication option is set to disabled.

Click on Picture for better Resolution

In order to enable Windows Authentication protocol, you have to disable the anonymous access and enable the Windows Authentication protocol. You configuration should look like the screenshot below

Click on Picture for better Resolution

Step 2 – Modify the Web.config file for RDWeb

Now, we have to say to the web application that the Windows Authentication protocol can be used. In order to do that, we will need to login into the Remote Web Access server and we will need to modify the following web.config file located at %SystemDrive%WindowsWebRDWebPagesWeb.config

Click on Picture for better Resolution

Remote Desktop Internet Explorer

Edit this file with notepad and locate the section outlined in the screenshot

Click on Picture for better Resolution

You will need to uncomment the section

<authentication mode=”Windows”/>

and comment the section

<!- –
<authentication mode=”Forms”>
<forms loginUrl=”default.aspx” name=”TSWAAuthHttpOnlyCookie” protection=”All” requireSSL=”true” />

– ->

It’s not finish yet. In this web config file, you will still need to comment out another section. In the file, locate the section <System.WebServer>. As shown in the screenshot below, you will need to comment out the section beneath the <System.WebServer> tag.

Click on Picture for better Resolution

If you do not comment this section, when trying to access the Remoteapp login page, you will see an error message similar to the following

Click on Picture for better Resolution

Step 3 – Modify the login page

We need to perform an additonal modification on the default login page in order to have a fully working Windows Integrated authentication mechanism. When using the form-based authentication, you can specify if the computer is a public computer or a private computer. If we are using the WIA mechanism, the form is not visible and you can specify this option anymore. By modifying the code of the login page, we can set the private computer option as default.

To perform this, edit the file located at %systemDrive%WindowsWebRDWebPagesen-usDefault.aspx.

Click on Picture for better Resolution

In the file search for the word bPrivateMode (see screenshot below).

Click on Picture for better Resolution

The default value is set to False. You have to change the value to True. This line should look like

public bool bShowPublicCheckBox = false, bPrivateMode = true, bRTL = false;

Step 4 – Configure Internet Explorer for WIA Protocol

There is a final step that should be performed at the browser level. If you try to access your remoteapp web page and you are still prompted for credentials, this might mean that the web site you are trying to access is not listed as Local Intranet Zones.

Click on Picture for Better Resolution

You have to be sure that the url of the remotapp server is configured to be part of the Local Intranet Zone. You can configure this option manually or you can use a GPO that would set this option automatically for you

Final Notes

Voila ! We have accomplished our goal. Now, when a user connect to the remoteapp url, he will have a direct access to the applications that have been published to him. Moreover, the user will be able to start the remoteapp and no more credentials would be requested. Isn’t it cool ?

Till Next Time

See ya

Réferences :


The Remote Desktop web client lets you use a compatible web browser to access your organization's remote resources (apps and desktops) published to you by your admin. You'll be able to interact with the remote apps and desktops like you would with a local PC no matter where you are, without having to switch to a different desktop PC. Once your admin sets up your remote resources, all you need are your domain, user name, password, the URL your admin sent you, and a supported web browser, and you're good to go.


Curious about the new releases for the web client? Check out What's new for Remote Desktop web client?

What you'll need to use the web client

  • For the web client, you'll need a PC running Windows, macOS, ChromeOS, or Linux. Mobile devices are not supported at this time.
  • A modern browser like Microsoft Edge, Internet Explorer 11, Google Chrome, Safari, or Mozilla Firefox (v55.0 and later).
  • The URL your admin sent you.


The Internet Explorer version of the web client does not have audio at this time.Safari may display a gray screen if the browser is resized or enters fullscreen multiple times.

Start using the Remote Desktop client


To sign in to the client, go to the URL your admin sent you. At the sign in page, enter your domain and user name in the format DOMAINusername, enter your password, and then select Sign in.


By signing in to the web client, you agree that your PC complies with your organization's security policy.

After you sign in, the client will take you to the All Resources tab, which contains all items published to you under one or more collapsible groups, such as the 'Work Resources' group. You'll see several icons representing the apps, desktops, or folders containing more apps or desktops that the admin has made available to the work group. You can come back to this tab at any time to launch additional resources.

To start using an app or desktop, select the item you want to use, enter the same user name and password you used to sign in to the web client if prompted, and then select Submit. You might also be shown a consent dialog to access local resources, like clipboard and printer. You can choose to not redirect either of these, or select Allow to use the default settings. Wait for the web client to establish the connection, and then start using the resource as you would normally.

When you're finished, you can end your session by either selecting the Sign Out button in the toolbar at the top of your screen or closing the browser window.

Web client keyboard shortcuts

Remote Desktop Internet Explorer Free

The following table describes alternate key combinations to inject standard Windows shortcut keys in the remote session.

Shortcut keyDescription
(Windows) Ctrl+Alt+End
(MacOS) fn+control+option+delete
Inject Ctrl+Alt+Del in the remote session.
Alt+F3Injects Windows key in the remote session.

Printing from the Remote Desktop web client

Follow these steps to print from the web client:

  1. Start the printing process as you would normally for the app you want to print from.
  2. When prompted to choose a printer, select Remote Desktop Virtual Printer.
  3. After choosing your preferences, select Print.
  4. Your browser will generate a PDF file of your print job.
  5. You can choose to either open the PDF and print its contents to your local printer or save it to your PC for later use.

Transfer files with the web client

To learn how to enable web client file transfer, check out Configure device redirections.

Remote Desktop Connection Internet Explorer

Follow these steps to transfer files from your local computer to the remote session:

  1. Connect to the remote session.
  2. Select the file upload icon in the web client menu.
  3. When prompted, select the files you want to upload using the local file explorer.
  4. Open the file explorer in your remote session. Your files will be uploaded to Remote Desktop Virtual Drive > Uploads.

To download files from the remote session to your local computer:

  1. Connect to the remote session.
  2. Open the file explorer in your remote session.
  3. Copy the files you want to download to Remote Desktop Virtual Drive > Downloads.
  4. Your files will be downloaded to your local default downloads folder.

Copy and paste from the Remote Desktop web client

The web client currently supports copying and pasting text only. Files can't be copied or pasted to and from the web client. Additionally, you can only use Ctrl+C and Ctrl+V to copy and paste text.

Use an Input Method Editor (IME) in the remote session

The web client supports using an Input Method Editor (IME) in the remote session in version or later. Before you can use the IME, you must install the language pack for the keyboard you want to use in the remote session on the host virtual machine. To learn more about setting up language packs in the remote session, check out Add language packs to a Windows 10 multi-session image.

Internet Explorer Remote Desktop Extension

To enable IME input using the web client:

  1. Before you connect to the remote session, go to the web client Settings panel.
  2. Toggle the Enable Input Method Editor setting to On.
  3. In the drop-down menu, select the keyboard you want to use in the remote session.
  4. Connect to the remote session.

Microsoft Remote Desktop Web App

The web client will suppress the local IME window when you are focused on the remote session. If you change the IME settings after you've already connected to the remote session, the setting changes won't have any effect. The web client doesn't support IME input while using a private browsing window.


If the language pack isn't installed on the host virtual machine, the remote session will default to the English (United States) keyboard.

Get help with the web client

If you've encountered an issue that can't be solved by the information in this article, you can get help with the web client by raising feedback on the web client's Feedback page.