How to Connect AVD Remote Desktop Resources Client or Browser?

There are two ways to access the AVD Remote desktop and remote app that you published. In this post, we will discuss both options in detail. Also, you would be able to see a video experience of the Azure Virtual Desktop (AVD) remote desktop.

The same Remote Desktop Client (RD Client) is used for end-user connectivity or launching Windows 365 Cloud PCs. More details Windows 365 Cloud PC Web Client End User Experience Walkthrough.

NOTE!AVD is GA’d Generally Available World Wide with the App Attach Feature?

Patch My PC

Related PostInstall Subscribe Windows RD Client for AVD End User Step by Step Guide

Introduction

Microsoft AVD is the new VDI story from Microsoft. I have a post in which I explained about Microsoft AVD Vs. Citrix, AVD Myths, AVD Known Issues, and AVD setup. More details are in the Microsoft VDI Story post.

Microsoft shared details about Microsoft AVD release dates (GA), and the future roadmap of AVD is explained in the Windows Virtual Desktop Ask Me Anything (AMA). I have a post that highlighted the points the AVD engineering team shared in the AVD AMA. More details are in the AVD AMA post.

Connect to Microsoft WVD Remote Desktop Resources
Connect to Microsoft AVD Remote Desktop Resources

In this post, you are going to see two methods to access AVD remote apps and remote desktops from a Thin client or physical desktop. The following are the two options available to access AVD Remote Desktops and Apps.

NOTE! – PWA (Progressive Web Apps)options are NOT enabled for the AVD web browsers yet. Maybe this is coming in the future?

NOTE! – Do you have Questions about AVD Remote/Web SSO? The following link will help you to understand better. https://www.anoopcnair.com/microsoft-wvd-ama-faq-ga-dates/#WVD_SSO_Related_Questions

AVD Web Client Browser (HTML5 based browser)

The Web browser is the easiest way to connect to AVD remote desktops and apps. AVD remote desktop resources can be accessed from any web browser which supports HTLM5.

Azure Virtual Desktop Web Client URLs are changed now. You need to transition to using the new URLs before 18 April 2022.

Update: The new web client URL works fine with all the browsers and gives the same experience as the previous web client URLs. I can’t reproduce the below explained different experiences anymore.

I think the issue was already highlighted there in the screenshot below. It seems I used the wrong URL or it got redirected to the wrong web client URL.

It seems there is consent required for new client URLs only if you access them from the Microsoft Edge browser where you logged in to your personal profile. If you don’t have appropriate permissions on Azure AD, then this is going to create some delays in the migration process to new AVD URLs.

I have tested with Firefox and other browsers and the new URLs just work just fine if the user account is assigned with the correct licenses. This means the user login details should be cached in the browser to get this working.

AVD Web Client Browser (HTML5 based browser)
AVD Web Client Browser (HTML5 based browser)

The following was the previous experience with web client URL when I tried to log in from Microsoft Edge Personal profile login and for the work profiles where you don’t have the appropriate license to access AVD.

The change in the end-user experience with the new URL is going to create some confusion within the AVD community.

How to Connect AVD Remote Desktop Resources Client or Browser? 1

▶▶▶▶ https://aka.ms/wvdARMweb

NOTE! – The end-user experience of AVD Remote Desktop Client (explained) is better than a Web browser. I have seen inconsistency in Single Sign-On(SSO) and a couple of pop-ups etc…

NOTE! – You can use the following URL to connect to AVD remote desktop resources. https://rdweb.wvd.microsoft.com/webclient/index.html (This won’t work for WVD V2 or new WVD with ARM support or AVD Spring release).

Non ARM AVD Web Client URLs

I hope you are not using the non-arm version AVD until now. If so, the following are the Web Client URLs for the non-ARM version of AVD (WVD v1.0).

Windows 10 Device

I use the web browser to connect to AVD resources during the test scenarios as it’s straightforward to test with different web browsers on my Windows 10 Surface book.

Connect to WVD Client Resource - Web Browser from Windows 10
Connect to AVD Client Resource – Web Browser from Windows 10

Mobile Devices – Non Windows Devices

The only option to access AVD resources from mobile and non Windows devices is via a Web Browser. Microsoft mentioned in their documentation that you could access AVD remote desktop resources from all non-windows devices with HTML5 support.

I tried to access AVD resources from iOS 12/13/14/15 devices on different browsers, and the following are the results.

  • ChromeWorks perfectly fine
Chrome Browser on iOS 12 device - WVD Resource Access from Client
Chrome Browser on iOS 12 device – AVD Resource Access from Client
  • SafariWorks fine
Safari Browser on iOS 12 device - WVD Resource Access from Client
Safari Browser on iOS 12 device – WVD Resource Access from Client
  • Microsoft EdgeNot able to list down the AVD resources
Microsoft Edge Browser on iOS 12 device - WVD Resource Access from Client
Microsoft Edge Browser on iOS 12 device – AVD Resource Access from Client

AVD Remote Desktop Client (Windows Devices)

The second option to connect to AVD remote desktop resources is to download and install the AVD Remote Desktop client. This client is available only for Windows devices.

Features of Update Microsoft Remote Client for AVD

Following are the features included in the latest version of the Microsoft Remote desktop client as per Freek Berson @fberson.

  • Fallback language for localized version is improved
  • Upon removing a subscription, cached credentials in the credential manager are adequately cleaned up.
  • Unattended client update process and client relaunch once completed (noticeable once the next update is available)
  • The Microsoft Remote Desktop Client can be used on Windows 10S

Once the client is installed, it will get the Automatic update from the cloud. You can see the notification within the AVD remote desktop client/Windows Action Center. The latest  Microsoft Remote Desktop client supports Windows 10S version, and it’s more stable.

Microsoft Remote Desktop - 1.2.246.0 - WVD Remote Desktop Resource
Microsoft Remote Desktop – 1.2.246.0 – AVD Remote Desktop Resource

NOTE! – In Microsoft documentation, there are only Windows 7, and Windows 10 support statement is available. I hope Windows 8.1 is also supported.

Download AVD Remote Desktop Client

You can download the latest Azure Remote Desktop (AVD) client from the Microsoft website here. Latest version ✔

Video Experience AVD Remote Desktop Client

The following video will give you the experience of Microsoft remote desktop client app installation, subscription, display settings, and automatic client update.

✔Microsoft AVD Remote Desktop Client Download
✔Microsoft Remote Desktop Client app installation
✔AVD Remote Desktop Client subscription
✔AVD Remote Desktop Client display settings
✔AVD Remote Desktop Client automatic client update

AVD Remote Desktop Client – Display Settings

Following are the AVD remote desktop client display settings available with the latest version of the client. If you don’t change the setting, it will automatically take the display settings of your physical device. This behavior is a bit troublesome user experience (when you connect to dual-screen etc..)

NOTE!Right client on your AVD Remote Resources listed down in the client and select Settings. In the settings menu, you can adjust the display setting as you need.

The following are my favorite display settings for Microsoft Remote Desktop Client when I test AVD Remote Desktops/Remote Apps.

  • Use Default Settings – OFF
    • Display Settings
    • Use All Monitors – OFF
    • Start in full screen – OFF
    • Update the resolution on resize – OFF
    • Resolution – Choose for me – 1280 x 1024
    • Change the size of the text and apps: 175% (this will show the windows inside the remote desktop much clear)
    • Fit Session to Window – ON
WVD Remote Desktop Client - Display Settings
AVD Remote Desktop Client – Display Settings

AVD Microsoft Remote Desktop Client – WIP – Conflict?

I think there is a conflict between Windows Information Protection (WIP) policies (deployed through Microsoft Intune) and Microsoft Remote Desktop Client.

You might be able to reproduce the issue once the subscription is timed out and you need to unsubscribe and subscribe again. The same issue is there with the newest version 1.2.246.0.

I could see Microsoft Remote Desktop is WIP enlighten app. But, not sure whether the RD client (msrdcw.exe) we use for AVD is enlightened or not.

How to Connect AVD Remote Desktop Resources Client or Browser? 2

Thin Client Access

Microsoft is closely working with all the thin client vendors and specifically with DELL as they mentioned in the AVD AMA. The following are the Thin client OSes that Microsoft is going to support currently/future.

  • Windows 10 IoT Enterprise (supported)
  • Linux based thin clients (Future roadmap)
  • Dell Thin Clients (Future roadmap)

Resources

Author

Anoop is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.

Categories AVD

9 thoughts on “How to Connect AVD Remote Desktop Resources Client or Browser?”

  1. Hm, i don’t have a “settings” option when i right click. The only option I have says “pin to start”. I’m trying to figure out how I can enable the WVD to span all monitors. Any thoughts?

    Reply
  2. Hey Anoop,

    im testing version 1.2.1672.0 Remote Desktop and having the WIP conflict that you mentioned briefly. Have you seen the same thing?

    I have tried to exempt the MSRDCW.EXE and MSRDC.EXE completely but they are still recognized at ‘personal’ apps on the endpoint client.
    Any ideas?

    Reply
      • Yeah, i tried that too.

        Name: MICROSOFT REMOTE DESKTOP
        Publisher: O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US
        Product Name: MICROSOFT REMOTE DESKTOP
        File: msrdc.exe
        File: msrdcw.exe
        Versions: *

        Did you add any URi’s to the network boundaries?

        Im going to try that again, and then leave the client for a bit. Intune policies seem slow to deploy to the client these days.

  3. Hi Anoop was wondering if you have seen this. I have logged into my Workspace via the AVD Remote desktop client with no issues, but when I use the Arms2 Webclient I don’t see my workspace at all.

    Reply
    • Hi Bob, I have seen this when users by mistakenly open the v1 version of the RD web client. Are you sure end users are using the correct v2 URL?

      Have you tried from different browsers?

      Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.