Microsoft Rd Web Mac

 
-->
  1. Microsoft Windows For Mac
  2. Microsoft Mac Software

Si applica a: Windows 10, Windows 8.1, Windows Server 2012 R2, Windows Server 2016Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2, Windows Server 2016

Nov 27, 2016  In this video, I'll show you how to use Microsoft Remote Desktop on a Mac. Simply download the application from Apple's App store, install,. Nov 05, 1934  Microsoft Remote Desktop. Use the Microsoft Remote Desktop app to connect to a remote PC or virtual apps and desktops made available by your admin. The app helps you be productive no matter where you are. Getting Started Configure your PC for remote access first. Dec 19, 2019 1. For Remote Desktop client on MAC, you can use it to work with Windows apps, resources, and desktops from your Mac computer or simply remote to the target server/PC via your Mac. You could refer to below documents and guidance to get a better image of RDC for Mac. Get started with the macOS client. Oct 22, 2019  Best practices. Use Windows Server 2019 for your Remote Desktop infrastructure (the Web Access, Gateway, Connection Broker, and license server). Windows Server 2019 is backward-compatible with these components, which means a Windows Server 2016 or Windows Server 2012 R2 RD Session Host can connect to a 2019 RD Connection Broker, but not the other way around.

Puoi eseguire il client Desktop remoto per Mac per utilizzare desktop, risorse e app di Windows dal computer Mac.You can use the Remote Desktop client for Mac to work with Windows apps, resources, and desktops from your Mac computer.Per iniziare, usa le informazioni seguenti e, se hai dubbi, consulta le domande frequenti.Use the following information to get started - and check out the FAQ if you have questions.

Nota

  • Se vuoi conoscere le nuove versioni per il client macOS,Curious about the new releases for the macOS client?vedi Novità di Desktop remoto in Mac.Check out What's new for Remote Desktop on Mac?
  • Il client Mac viene eseguito in computer con macOS 10.10 e versioni successive.The Mac client runs on computers running macOS 10.10 and newer.
  • Le informazioni in questo articolo si applicano principalmente alla versione completa del client Mac, ovvero la versione disponibile in Mac App Store.The information in this article applies primarily to the full version of the Mac client - the version available in the Mac AppStore.Prova le nuove funzionalità scaricando da qui l'app di anteprima: note sulla versione beta del client.Test-drive new features by downloading our preview app here: beta client release notes.

Ottenere il client Desktop remotoGet the Remote Desktop client

Per iniziare a usare Desktop remoto nel computer Mac, segui questi passaggi:Follow these steps to get started with Remote Desktop on your Mac:

  1. Scaricare il client di Desktop remoto Microsoft dal Mac App Store.Download the Microsoft Remote Desktop client from the Mac App Store.
  2. Configura il PC per accettare le connessioni remote.Set up your PC to accept remote connections.Se ignori questo passaggio, non puoi connetterti al PC.(If you skip this step, you can't connect to your PC.)
  3. Aggiungi una connessione Desktop remoto o una risorsa remota.Add a Remote Desktop connection or a remote resource.Una connessione consente di connettersi direttamente a un PC Windows, mentre una risorsa remota consente di usare un programma RemoteApp, un desktop basato su sessione o un desktop virtuale pubblicato in locale usando connessioni RemoteApp e Desktop.You use a connection to connect directly to a Windows PC and a remote resource to use a RemoteApp program, session-based desktop, or a virtual desktop published on-premises using RemoteApp and Desktop Connections.Questa funzionalità è in genere disponibile negli ambienti aziendali.This feature is typically available in corporate environments.

Informazioni sulla versione beta del client MacWhat about the Mac beta client?

Stiamo testando nuove funzionalità nel canale di anteprima di AppCenter.We're testing new features on our preview channel on AppCenter.Per dare un'occhiata,Want to check it out?passa a Microsoft Remote Desktop for Mac e fai clic su Download (Scarica).Go to Microsoft Remote Desktop for Mac and click Download.Non devi creare un account o accedere ad AppCenter per scaricare la versione beta del client.You don't need to create an account or sign into AppCenter to download the beta client.

Se hai già il client, puoi verificare la disponibilità di aggiornamenti per assicurarti di usare la versione più recente.If you already have the client, you can check for updates to ensure you have the latest version.Nel client beta, fare clic su Microsoft Remote Desktop Beta nella parte superiore, quindi fare clic su Controlla aggiornamenti.In the beta client, click Microsoft Remote Desktop Beta at the top, and then click Check for updates.

Aggiungere una connessione Desktop remotoAdd a Remote Desktop connection

Per creare una connessione Desktop remoto:To create a remote desktop connection:

  1. In Connection Center (Centro connessioni) fai clic su + e quindi su Desktop.In the Connection Center, click +, and then click Desktop.

  2. Immettere le informazioni seguenti:Enter the following information:

    • PC name (Nome PC): nome del computer.PC name - the name of the computer.
      • Puoi usare il nome di un computer Windows (individuabile nelle impostazioni di sistema), un nome di dominio o un indirizzo IP.This can be a Windows computer name (found in the System settings), a domain name, or an IP address.
      • Puoi anche aggiungere informazioni sulla porta alla fine del nome, ad esempio MyDesktop:3389.You can also add port information to the end of this name, like MyDesktop:3389.
    • User Account (Account utente): account utente usato per accedere al PC remoto.User Account - Add the user account you use to access the remote PC.
      • Per gli account locali o i computer aggiunti ad Active Directory (AD), usa uno dei formati seguenti: user_name, domainuser_name oppure user_name@domain.com.For Active Directory (AD) joined computers or local accounts, use one of these formats: user_name, domainuser_name, or user_name@domain.com.
      • Per i computer aggiunti ad Azure Active Directory (AAD), usa uno dei formati seguenti: AzureADuser_name oppure AzureADuser_name@domain.com.For Azure Active Directory (AAD) joined computers, use one of these formats: AzureADuser_name or AzureADuser_name@domain.com.
      • Puoi anche scegliere se richiedere una password.You can also choose whether to require a password.
      • Quando gestisci più account utente con lo stesso nome utente, imposta un nome descrittivo per distinguere gli account.When managing multiple user accounts with the same user name, set a friendly name to differentiate the accounts.
      • Gestisci gli account utente salvati nelle preferenze dell'app.Manage your saved user accounts in the preferences of the app.

  3. Puoi anche definire queste impostazioni facoltative per la connessione:You can also set these optional settings for the connection:

    • Impostare un nome descrittivoSet a friendly name
    • Aggiungere un gatewayAdd a Gateway
    • Impostare l'output audioSet the sound output
    • Scambiare i pulsanti del mouseSwap mouse buttons
    • Abilitare la modalità di amministrazioneEnable Admin Mode
    • Reindirizzare le cartelle locali in una sessione remotaRedirect local folders into a remote session
    • Inoltrare le stampanti localiForward local printers
    • Inoltrare le smart cardForward Smart Cards

  4. Fare clic su Save.Click Save.

Per avviare la connessione, fai semplicemente doppio clic su di essa.To start the connection, just double-click it.Usa la stessa modalità di selezione per le risorse remote.The same is true for remote resources.

Esportare e importare connessioniExport and import connections

Puoi esportare una definizione della connessione Desktop remoto e usarla in un altro dispositivo.You can export a remote desktop connection definition and use it on a different device.Desktop remoto vengono salvati in separato. File RDP.Remote desktops are saved in separate .RDP files.

  1. In Centro connessioni, fare clic sul desktop remoto.In the Connection Center, right-click the remote desktop.
  2. Fare clic su esportare.Click Export.
  3. Passare al percorso in cui si desidera salvare il desktop remoto. File con estensione RDP.Browse to the location where you want to save the remote desktop .RDP file.
  4. Fare clic su OK.Click OK.

Utilizzare la procedura seguente per importare un desktop remoto. File con estensione RDP.Use the following steps to import a remote desktop .RDP file.

  1. Nella barra dei menu fai clic su File > Import (File > Importa).In the menu bar, click File > Import.
  2. Individuare il. File con estensione RDP.Browse to the .RDP file.
  3. Fare clic su Apri.Click Open.

Aggiungere una risorsa remotaAdd a remote resource

Risorse remote sono programmi RemoteApp, desktop basati su sessione e i desktop virtuali pubblicati tramite connessione RemoteApp e Desktop.Remote resources are RemoteApp programs, session-based desktops, and virtual desktops published using RemoteApp and Desktop Connections.

  • L'URL visualizza il collegamento al server Accesso Web Desktop remoto che consente di accedere a connessioni RemoteApp e Desktop.The URL displays the link to the RD Web Access server that gives you access to RemoteApp and Desktop Connections.
  • Vengono elencate le connessioni RemoteApp e Desktop configurate.The configured RemoteApp and Desktop Connections are listed.

Per aggiungere una risorsa remota:To add a remote resource:

  1. In Connection Center (Centro connessioni) fai clic su + e quindi su Add Remote Resources (Aggiungi risorse remote).In the Connection Center click +, and then click Add Remote Resources.
  2. Immettere le informazioni per la risorsa remota:Enter information for the remote resource:
    • URL del feed -l'URL del server Accesso Web desktop remoto.Feed URL - The URL of the RD Web Access server.È inoltre possibile immettere l'account di posta elettronica aziendale in questo campo: in questo modo il client per cercare il Server di accesso Web desktop remoto associato l'indirizzo di posta elettronica.You can also enter your corporate email account in this field – this tells the client to search for the RD Web Access Server associated with your email address.
    • Nome utente -il nome utente da utilizzare per il server Accesso Web desktop remoto si è connessi.User name - The user name to use for the RD Web Access server you are connecting to.
    • Password -la password da utilizzare per il server Accesso Web desktop remoto si è connessi.Password - The password to use for the RD Web Access server you are connecting to.
  3. Fare clic su Save.Click Save.

Verranno visualizzate nel Centro connessioni di risorse remote.The remote resources will be displayed in the Connection Center.

Connettersi a un gateway Desktop remoto per accedere alle risorse interneConnect to an RD Gateway to access internal assets

Un gateway Desktop remoto consente di stabilire la connessione a un computer remoto in una rete aziendale da qualsiasi posizione in Internet.A Remote Desktop Gateway (RD Gateway) lets you connect to a remote computer on a corporate network from anywhere on the Internet.Puoi creare e gestire i gateway nelle preferenze dell'app o durante la configurazione di una nuova connessione desktop.You can create and manage your gateways in the preferences of the app or while setting up a new desktop connection.

Per impostare un nuovo gateway nelle preferenze:To set up a new gateway in preferences:

  1. In Connection Center (Centro connessioni) fai clic su Preferences > Gateway (Preferenze > Gateway).In the Connection Center, click Preferences > Gateways.
  2. Seleziona il pulsante + nella parte inferiore della tabella e immetti le informazioni seguenti:Click the + button at the bottom of the table Enter the following information:
    • Nome del server : il nome del computer di cui si desidera utilizzare come gateway.Server name – The name of the computer you want to use as a gateway.Puoi usare il nome di un computer Windows, un nome di dominio Internet o un indirizzo IP.This can be a Windows computer name, an Internet domain name, or an IP address.Puoi anche aggiungere informazioni sulla porta al nome del server (ad esempio: RDGateway:443 oppure 10.0.0.1:443).You can also add port information to the server name (for example: RDGateway:443 or 10.0.0.1:443).
    • Nome utente -il nome utente e la password da utilizzare per il gateway Desktop remoto si connette.User name - The user name and password to be used for the Remote Desktop gateway you are connecting to.È inoltre possibile selezionare utilizzare le credenziali di connessione da utilizzare il medesimo nome utente e la password come quelle utilizzate per la connessione desktop remoto.You can also select Use connection credentials to use the same user name and password as those used for the remote desktop connection.

Gestire gli account utenteManage your user accounts

Quando ci si connette a una risorsa remota o desktop, è possibile salvare gli account utente per selezionare nuovamente.When you connect to a desktop or remote resources, you can save the user accounts to select from again.È possibile gestire gli account utente utilizzando il client Desktop remoto.You can manage your user accounts by using the Remote Desktop client.

Does microsoft project work on mac. Per creare un nuovo account utente:To create a new user account:

  1. In Connection Center (Centro connessioni) fai clic su Settings > Accounts (Impostazioni > Account).In the Connection Center, click Settings > Accounts.
  2. Fai clic su Add User Account (Aggiungi account utente).Click Add User Account.
  3. Immettere le informazioni seguenti:Enter the following information:
    • Nome utente -il nome dell'utente da salvare per l'utilizzo con una connessione remota.User Name - The name of the user to save for use with a remote connection.Puoi immettere il nome utente in uno dei formati seguenti: user_name, domainuser_name o user_name@domain.com.You can enter the user name in any of the following formats: user_name, domainuser_name, or user_name@domain.com.
    • Password -la password per l'utente specificato.Password - The password for the user you specified.Ogni account utente che si desidera salvare da utilizzare per le connessioni remote deve avere una password associata.Every user account that you want to save to use for remote connections needs to have a password associated with it.
    • Friendly Name (Nome descrittivo): se stai usando lo stesso account utente con password diverse, imposta un nome descrittivo per distinguere gli account utente.Friendly Name - If you are using the same user account with different passwords, set a friendly name to distinguish those user accounts.
  4. Toccare salvare, e quindi toccare impostazioni.Tap Save, and then tap Settings.

Personalizzare la risoluzione dello schermoCustomize your display resolution

È possibile specificare la risoluzione dello schermo per la sessione di desktop remoto.You can specify the display resolution for the remote desktop session.

  1. Nel Centro connessioni, fare clic su Preferenze.In the Connection Center, click Preferences.
  2. Fare clic su risoluzione.Click Resolution.
  3. Fare clic su + .Click +.
  4. Immettere una risoluzione altezza e la larghezza e quindi fare clic su OK.Enter a resolution height and width, and then click OK.

Per eliminare la risoluzione, selezionarlo e quindi fare clic su - .To delete the resolution, select it, and then click -.

Displays have separate spaces (Schermi con spazi separati). Se usi Mac OS X 10.9 e hai disabilitato l'opzione Displays have separate spaces (Schermi con spazi separati) in Mavericks (System Preferences > Mission Control (Preferenze di sistema > Controllo missione) devi configurare questa impostazione nel client Desktop remoto con la stessa opzione.Displays have separate spaces If you are running Mac OS X 10.9 and disabled Displays have separate spaces in Mavericks (System Preferences > Mission Control), you need to configure this setting in the remote desktop client using the same option.

Reindirizzamento delle unità per le risorse remoteDrive redirection for remote resources

Il reindirizzamento delle unità è supportato per le risorse remote e consente di salvare localmente nel computer Mac i file creati con un'applicazione remota.Drive redirection is supported for remote resources, so that you can save files created with a remote application locally to your Mac.La cartella reindirizzata è sempre la home directory visualizzata come un'unità di rete nella sessione remota.The redirected folder is always your home directory displayed as a network drive in the remote session.

Nota

Per usare questa funzionalità, l'amministratore deve definire le impostazioni appropriate nel server.In order to use this feature, the administrator needs to set the appropriate settings on the server.

Usare una tastiera in una sessione remotaUse a keyboard in a remote session

I layout di tastiera Mac differiscono dai layout di tastiera Windows.Mac keyboard layouts differ from the Windows keyboard layouts.

  • Il tasto COMANDO sulla tastiera Mac corrisponde al tasto WINDOWS.The Command key on the Mac keyboard equals the Windows key.
  • Per eseguire le azioni che usano il tasto COMANDO in Mac, devi usare il tasto CTRL di Windows (ad esempio: Copia = CTRL+C).To perform actions that use the Command button on the Mac, you will need to use the control button in Windows (e.g.: Copy = Ctrl + C).
  • I tasti funzione possono essere attivati durante la sessione premendo anche il tasto FN (ad esempio: FN+F1).The function keys can be activated in the session by pressing additionally the FN key (e.g.: FN + F1).
  • Il tasto ALT a destra della barra spaziatrice sulla tastiera Mac corrisponde al tasto ALTGR/ALT di destra in Windows.The Alt key to the right of the space bar on the Mac keyboard equals the Alt Gr/right Alt key in Windows.

Per impostazione predefinita, la sessione remota userà le stesse impostazioni locali della tastiera del sistema operativo su cui viene eseguito il client.By default, the remote session will use the same keyboard locale as the OS you're running the client on.Se il Mac esegue un sistema operativo in lingua inglese, questo stesso sistema operativo verrà usato anche per le sessioni remote. Se le impostazioni locali della tastiera del sistema operativo non vengono usate, controlla l'impostazione della tastiera nel computer remoto e modificala manualmente.(If your Mac is running an en-us OS, that will be used for the remote sessions as well.) If the OS keyboard locale is not used, check the keyboard setting on the remote PC and change it manually.Per altre informazioni sulle tastiere e le impostazioni locali, vedi Domande frequenti sul client Desktop remoto.See the Remote Desktop Client FAQ for more information about keyboards and locales.

Supporto per l'autenticazione del plug-in gateway Desktop remoto e l'autorizzazioneSupport for Remote Desktop gateway pluggable authentication and authorization

Windows Server 2012 R2 introdotto il supporto per un nuovo metodo di autenticazione, autenticazione plug-in Gateway Desktop remoto e l'autorizzazione, che offre maggiore flessibilità per le routine di autenticazione personalizzato.Windows Server 2012 R2 introduced support for a new authentication method, Remote Desktop Gateway pluggable authentication and authorization, which provides more flexibility for custom authentication routines.Puoi ora provare questo modello di autenticazione con il client Mac.You can now try this authentication model with the Mac client.

Importante

Modelli di autenticazione e autorizzazione personalizzati prima di Windows 8.1 non sono supportati, anche se nell'articolo precedente vengono illustrate tali.Custom authentication and authorization models before Windows 8.1 are not supported, although the article above discusses them.

Per altre informazioni su questa funzionalità, consulta https://aka.ms/paa-sample.To learn more about this feature, check out https://aka.ms/paa-sample.

Suggerimento

Domande e commenti sono sempre Benvenuti.Questions and comments are always welcome.Tuttavia, NON inviare una richiesta di risoluzione dei problemi utilizzando la funzionalità di commento alla fine di questo articolo.However, please do NOT post a request for troubleshooting help by using the comment feature at the end of this article.Al contrario, andare alla forum su client di Desktop remoto e avviare un nuovo thread.Instead, go to the Remote Desktop client forum and start a new thread.Avete suggerimenti funzionalità?Have a feature suggestion?Comunicaci nel forum dedicato agli utenti di client.Tell us in the client user voice forum.

-->

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

Important

The web client does not currently support using Azure Application Proxy and does not support Web Application Proxy at all. See Using RDS with application proxy services for details.

What you'll need to set up the web client

Before getting started, keep the following things in mind:

  • Make sure your Remote Desktop deployment has an RD Gateway, an RD Connection Broker, and RD Web Access running on Windows Server 2016 or 2019.
  • Make sure your deployment is configured for per-user client access licenses (CALs) instead of per-device, otherwise all licenses will be consumed.
  • Install the Windows 10 KB4025334 update on the RD Gateway. Later cumulative updates may already contains this KB.
  • Make sure public trusted certificates are configured for the RD Gateway and RD Web Access roles.
  • Make sure that any computers your users will connect to are running one of the following OS versions:
    • Windows 10
    • Windows Server 2008R2 or later
Mac

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:

  1. Open an elevated PowerShell prompt.
  2. Run Uninstall-Module RDWebClientManagement to uninstall the new module.
  3. Close and reopen the elevated PowerShell prompt.
  4. Run Install-Module RDWebClientManagement -RequiredVersion <old version> to install the old module.
  5. Run Uninstall-RDWebClient to uninstall the old web client.
  6. Run Uninstall-Module RDWebClientManagement to uninstall the old module.
  7. Close and reopen the elevated PowerShell prompt.
  8. Proceed with the normal installation steps as follows.

How to publish the Remote Desktop web client

To install the web client for the first time, follow these steps:

  1. On the RD Connection Broker server, obtain the certificate used for Remote Desktop connections and export it as a .cer file. Copy the .cer file from the RD Connection Broker to the server running the RD Web role.

  2. On the RD Web Access server, open an elevated PowerShell prompt.

  3. On Windows Server 2016, update the PowerShellGet module since the inbox version doesn't support installing the web client management module. To update PowerShellGet, run the following cmdlet:

    Important

    You'll need to restart PowerShell before the update can take effect, otherwise the module may not work.

  4. Install the Remote Desktop web client management PowerShell module from the PowerShell gallery with this cmdlet:

  5. After that, run the following cmdlet to download the latest version of the Remote Desktop web client:

  6. Next, run this cmdlet with the bracketed value replaced with the path of the .cer file that you copied from the RD Broker:

  7. Finally, run this cmdlet to publish the Remote Desktop web client:

    Make sure you can access the web client at the web client URL with your server name, formatted as https://server_FQDN/RDWeb/webclient/index.html. It's important to use the server name that matches the RD Web Access public certificate in the URL (typically the server FQDN).

    Note

    When running the Publish-RDWebClientPackage cmdlet, you may see a warning that says per-device CALs are not supported, even if your deployment is configured for per-user CALs. If your deployment uses per-user CALs, you can ignore this warning. We display it to make sure you're aware of the configuration limitation.

  8. When you're ready for users to access the web client, just send them the web client URL you created.

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 client

When a new version of the Remote Desktop web client is available, follow these steps to update the deployment with the new client:

  1. Open an elevated PowerShell prompt on the RD Web Access server and run the following cmdlet to download the latest available version of the web client:

  2. Optionally, you can publish the client for testing before official release by running this cmdlet:

    The client should appear on the test URL that corresponds to your web client URL (for example, https://server_FQDN/RDWeb/webclient-test/index.html).

  3. Publish the client for users by running the following cmdlet:

    This will replace the client for all users when they relaunch the web page.

How to uninstall the Remote Desktop web client

To remove all traces of the web client, follow these steps:

  1. On the RD Web Access server, open an elevated PowerShell prompt.

  2. Unpublish the Test and Production clients, uninstall all local packages and remove the web client settings:

  3. Uninstall the Remote Desktop web client management PowerShell module:

How to install the Remote Desktop web client without an internet connection

Follow 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

  1. Open a PowerShell prompt.

  2. Import the Remote Desktop web client management PowerShell module from the PowerShell gallery:

  3. Download the latest version of the Remote Desktop web client for installation on a different device:

  4. Download the latest version of the RDWebClientManagement PowerShell module:

  5. Copy the content of 'C:WebClient' to the RD Web Access server.

From the RD Web Access server

Follow the instructions under How to publish the Remote Desktop web client, replacing steps 4 and 5 with the following.

  1. You have two options to retrieve the latest web client management PowerShell module:

    • Import the Remote Desktop web client management PowerShell module:
    • Copy the downloaded RDWebClientManagement folder to one of the local PowerShell module folders listed under $env:psmodulePath, or add the path to the folder with the downloaded files to the $env:psmodulePath.

  2. Deploy the latest version of the Remote Desktop web client from the local folder (replace with the appropriate zip file):

Connecting to RD Broker without RD Gateway in Windows Server 2019

This 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 server

Follow these steps if there is no certificate bound to the RD Broker server

  1. Open Server Manager > Remote Desktop Services.

  2. In Deployment Overview section, select the Tasks dropdown menu.

  3. Select Edit Deployment Properties, a new window titled Deployment Properties will open.

  4. In the Deployment Properties window, select Certificates in the left menu.

  5. In the list of Certificate Levels, select RD Connection Broker - Enable Single Sign On. You have two options: (1) create a new certificate or (2) an existing certificate.

Follow these steps if there is a certificate previously bound to the RD Broker server

  1. Open the certificate bound to the Broker and copy the Thumbprint value.

  2. To bind this certificate to the secure port 3392, open an elevated PowerShell window and run the following command, replacing '< thumbprint >' with the value copied from the previous step:

    Note

    To check if the certificate has been bound correctly, run the following command:

    In the list of SSL Certificate bindings, ensure that the correct certificate is bound to port 3392.

  3. Open the Windows Registry (regedit) and nagivate to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp and locate the key WebSocketURI. The value must be set to https://+:3392/rdp/.

Setting up the RD Session Host

Follow these steps if the RD Session Host server is different from the RD Broker server:

  1. Create a certificate for the RD Session Host machine, open it and copy the Thumbprint value.

  2. To bind this certificate to the secure port 3392, open an elevated PowerShell window and run the following command, replacing '< thumbprint >' with the value copied from the previous step:

    Note

    To check if the certificate has been bound correctly, run the following command:

    In the list of SSL Certificate bindings, ensure that the correct certificate is bound to port 3392.

  3. Open the Windows Registry (regedit) and nagivate to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp and locate the key WebSocketURI. The value must be set to https://+:3392/rdp/.

General Observations

Microsoft Windows For Mac

  • Ensure that both the RD Session Host and RD Broker server are running Windows Server 2019.

  • Ensure that public trusted certificates are configured for both the RD Session Host and RD Broker server.

    Note

    If both the RD Session Host and the RD Broker server share the same machine, set the RD Broker server certificate only. If the RD Session Host and RD Broker server use different machines, both must be configured with unique certificates.

  • The Subject Alternative Name (SAN) for each certificate must be set to the machine's Fully Qualified Domain Name (FQDN). The Common Name (CN) must match the SAN for each certificate.

How to pre-configure settings for Remote Desktop web client users

This 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 telemetry

By 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 method

Note

This setting currently only works with the RDS web client, not the Windows 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 default

To 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:

Troubleshooting

If 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 client

The 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 Resources

If the user reports that they can't connect with the web client even though they can see the resources listed, check the following things:

  • Is the RD Gateway role properly configured to use a trusted public certificate?
  • Does the RD Gateway server have the required updates installed? Make sure that your server has the KB4025334 update installed.

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 log

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

  • Select the ellipsis in the upper-right corner and navigate to the About page in the dropdown menu.
  • Under Capture support information select the Start recording button.
  • Perform the operation(s) in the web client that produced the issue you are trying to diagnose.
  • Navigate to the About page and select Stop recording.
  • Your browser will automatically download a .txt file titled RD Console Logs.txt. This file will contain the full console log activity generated while reproducing the target issue.

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.

Microsoft Mac Software

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 report it on Tech Community. You can also request or vote for new features at our suggestion box.