Remote Desktop Client For Mac Rd Gateway

Active1 year, 7 months ago
  1. Windows Remote Desktop For Mac
  2. Mac Os Remote Desktop Client
  3. Remote Desktop Connection For Mac
  4. Remote Desktop Client For Linux
  5. Torrent Client For Mac
  6. Remote Desktop For Mac Download
  7. Download Microsoft Remote Desktop Client For Mac

Jump Desktop for iOS v5.5+ and Jump Desktop for Mac v3.0+ supports Remote Desktop Gateways (RD Gateway). This article will show you how to setup a Remote Desktop Gateway server using Jump Desktop. To connect to your campus Windows PC from a Mac you will need to use the Microsoft Remote Desktop application for Mac version 10.1.8 (or higher). If you are using a university-owned Mac, you may already have this app installed. RDP: Remote app does not encapsulate traffic when connecting via remote desktop gateway server 0 How connect MS remotedesktop client 10 with Windows 2012 R2 RDS? Remote Desktop Services (RDS) Access guide for. Mac & MacBook. What is Remote Desktop Web Access? Remote Desktop Web Access is a Microsoft technology that provides remote access to applications (RemoteApp) running on a Terminal Server without any VPN connection.


  • 4 Windows 2016 RDS servers in a collection
  • 1 Windows 2016 server that serves as RD Gateway and connection broker.

Authentication is done via NAP/Radius using a 2FA (Microsoft Multi-Factor Authentication).

Connection using Windows works just fine, either via RD Web Access in Internet Explorer, a custom RDP File (adding loadbalanceinfo:s:tsv://MS Terminal Services Plugin.CollectionName) or via RemoteApp and Desktop Connections. All fine (and my users like the flexibility).

Now the Mac. Using the latest version of the Microsoft Remote Desktop App (
Remote Resources kind of works. Users get multiple authentication prompts (for the RD Gateway and the RDS server).

I found this article ( for creating an RDP uri.


The uri works fine on iOS, single logon prompt and I get connected. This does not work on the Mac, giving either an Port reset by peer error on the old version of the RDP client (v8) or an access denied error in the new MS RDP client (v10).

Mac remote desktop client

Why won't this work on the Mac? It should be supported as far as I can see. And seeing the uri works fine on iOS it seems that is ok.

RS FinanceRS Finance

1 Answer

Well apparently this issue can be fixed by adding a DefaultTsvUrl value in de registry of the RDS Broker server. This redirects incompatible RD clients to a default collection.


NOTE: This is being suggested as an alternate/workaround when you do not have upgrading the client as an option. It has the following caveats that one should be aware of:

This would only be read when the client is unable to understand the tsvurl sent in the RDP file (from the remote app) and thus does not present the tsvurl to connection broker. Whenever such a client comes the DefaultTsvUrl sends it to one single collection as specified in the registry value. DefaultTsvUrl can only point to one single collection only and thus you may want to plan and create a single collection for non compatible clients that has all their required apps in it. There is no provision of defining multiple collections in this registry so if you want to use incompatible clients over multiple collections then it won't be possible. In case you change that collection, you will have to change the defauDefaultTsvUrl lttsvurl registry value as well. This registry is only a workaround for tsvurls and will not work if the clients are not compatible with remoteapps itself. It is only for providing a workaround for clients that were able to access remoteapps earlier in Windows 2008/R2 but cannot access them through collections as explained in the section 'Change in the way we connect in 2012 -Session Hint / TSVUrl'.

So this also work for Windows 2016. Why the new RDP client for the Mac seemingly ignores the loadbalanceinfo=s: info is unkown, it should be supported.

Also this is not really a solution but more a workaround but good enough for now.

RS FinanceRS Finance

Not the answer you're looking for? Browse other questions tagged mac-osxremote-desktopwindows-server-2016rdsremote-desktop-gateway or ask your own question.

Everyone will be familiar with the Remote Desktop client called MSTSC. Since a few years, Microsoft also has a Remote Desktop client for other platforms like iOS, Mac OS X and Android, available for download from the App Store, the Mac App Store, and the Google Play Store.

Windows Remote Desktop For Mac

As a next step, Microsoft now also has a web client based on HTML5 (currently into preview), called the RD Web Client. This blog post runs through the setup, based on the early preview that I tested. The Remote Desktop Web Client is installed as an extension of the RD Web Access role.


The requirements for the Web Client are as follows;

· RD deployment with Gateway, Broker and WebAccess roles all running Server 2016 Operating System. The endpoints (RDSH or Windows Client SKUs) can be running any Windows Operating System starting from Windows 7 SP1 / Windows Server 2008 R2. The client performance will however be better when connecting to Windows Server 2016 or Windows 10 Anniversary Edition or later.

· The RD deployment should NOT be configured to use per-device license.

· The Server 2016 machine hosting RD Gateway role must have this update installed -

Mac Os Remote Desktop Client

· The Gateway and WebAccess roles should be using public trusted certificates

· The client should work on most HTML5 capable browsers and has official support for Edge, IE11, Google Chrome, Firefox and Safari. Mobile devices are not supported.


By the time the client releases, new PowerShell CmdLets will be available to deploy, manage and configure the client. Based on the current beta, here’s an example of what these cmdlets might look.

We open an Administrative PowerShell console and run the following commands:

Import-Module ($Env:ProgramFiles + 'rd-html5-manageRDWebClientManagement')

Next, we copy the certificate used by the RD Web Access role. Optionally export it first, and make sure to include the private key. Then run the following commands in the PowerShell Admin console.

Import-RDWebClientBrokerCert <cer file>
Publish-RDWebClientPackage -Production -Latest

Easy as that! HTML5 support is now added to the RD Web Access role!

Note, in the beta release the Import-RDWebClientBrokerCert currently does not accept password protected pfx files. Make sure you export the certificate using the security principal option as shown below.


To test the HTML5 web client, open a browser (currently Edge, IE 11, Google Chrome browsers are all officially supported) and browse to https://<publicdomain>/RDWeb/Pages/webclient. For example, in my case I tested an Azure IaaS setup with 2 RD Web Access servers behind an Azure Load balancer. I created a public DNS record for and pointed that to the public IP of the Azure Load Balancer. I then browsed to

At first you will see the regular RD Web Access login screen and you login with a test account as you normally would too.

After logging in you will see the following screen, this is the HTML5 web client containing the 4 sample RemoteApps I published in the RDS deployment.

Remote Desktop Connection For Mac

If you click on one of the RemoteApps an RDP session will be launched. Note that currently you will get an additional prompt for the first RemoteApp as there is no full Single Sign On yet.

Since this was the first RemoteApp, the RDS session will now process the logon.

And shortly after, the RemoteApp is now available within the browser.

From this point, you can navigate to the bar on the left-hand side and switch between applications and launch new application. All RemoteApps are available within the same screen to allow to work with multiple application easily.

Remote Desktop Client For Linux

The RD Web Client also allows you to copy-paste between your local machine. It is however currently limited to text only.

There is also support for Remote Audio.

Torrent Client For Mac

For further management, the RDWebClientManagement PowerShell module beta version also comes with a few other Cmdlets to retrieve the package information, certificate and to uninstall the package. Note that these Cmdlets might slightly change once the PowerShell module reaches general availability.

If you want all users to be redirected to the Web Client instead of the traditional RD Web Access page, you can run the following command on the RD Web Access Server

Set-WebConfiguration system.webServer/httpRedirect 'IIS:sitesDefault Web Site' -Value @{enabled='true';destination='https://<domainname>/rdweb/pages/webclient';exactDestination='false';httpResponseStatus='Permanent';childOnly='true'};

Or change the same value using IIS Manager:

Remote Desktop For Mac Download

The RD Web Client also comes with printing support. A virtual printer called “Microsoft Print to PDF” is available in the user’s session. Don’t be confused by the postfix “redirected 3”. This is not a redirected printer, the name will most likely change so that it is clear that it’s a virtual printer. By virtual printer we mean that the printing to this printer will result in a .pdf file that is transported and opened on the local client. From that local client it can then be printed to any locally available printer.

I’m able to print to this redirected printer

Download Microsoft Remote Desktop Client For Mac

Which results in the pdf being locally available

And in this case, I opened it in my local browser to then print to a locally available printer.

This concludes a first walkthrough of the RD Web Client that is coming up, based on the current preview version. I will share more details on this new client as they come in. If you are currently using RDS in a production environment and would like to test drive the RD Web Client functionality. Feel free to reach out to me so that I can help to get onboarded on the preview.