In this post, you will see an end-user guide to installing & Subscribe to Windows RD Client for AVD manually. I will cover the automatic installation of the Windows RD Client for AVD in the upcoming posts.
You will need to check the following post to know more about Azure Virtual Desktop (AVD) web client access details. How To Connect AVD Remote Desktop Resources Client Browser. Also, AVD Troubleshooting Options Tips Tricks are useful too.
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! – Microsoft announced AVD is GA’d Generally Available. I’m expecting many exciting announcements in Microsoft Ignite 2019.
Download RD Client for AVD
- Download the RD Client for AVD from the following links:
Install the MSI Remote Desktop_***.msi (Admin access is required if you install it manually).
NOTE! – I will cover Intune/SCCM installation options of RD clients for AVD in the future posts.
- Click Next
Click on Accept and Next.
Select Install Just for you and click Next.
Click on Finish and Launch.
Subscribe to RD Client for AVD Feed
Let’s check how to subscript to the AVD feed. Click on Subscribe Button.
NOTE! – MFA options will be available with subscription and AAD Conditional Access
Sign in / Login with your user ID with cloud UPN (@howtomanagedevices.com) and click NEXT.
NOTE! – This will redirect to the Federated Login Page (AD FS), where you have to enter a password (username might automatically get populated) and click Sign-In
Once successfully signed in with your user ID, you will be able to see host pools and remote apps assigned to your user.
Right, Click on the host pool icon to change the display settings (the default setting is FULL Screen). Click on Settings
Please select the following options DISPLAY as per your preference (the following are my favorite settings).
- User Default Settings => Off
- Display Settings => Off
- Start in full screen => Off
- Update the resolution on resize => Yes
- Resolution => 200%
- Fit session to Windows => On
Double click on Host Pool the icon to launch the Remote Desktop. Enter the password and click OK, OK.
NOTE! – SSO is coming soon into RD AVD client.
Remote Desktop will get connected.
How to check the RD Client Update
New versions of Windows RD Client for AVD are automatically updated.
Check the version of the AVD RD Application – Click on (…) About -> Check for Updates to check whether there is any update.
Troubleshooting – RD Client for AVD
Check the version of the AVD RD Application – Click on (…) -> Update Status – Click on Update Now.
NOTE! – If there is any error here near the update status. You won’t be launching Remote Desktop and Remote Apps
Shortcuts to Launch Remote Desktops and Apps
Let’s try to control the shortcut RD client virtual desktop and virtual app shortcuts.
- AVD Video PlayList ➡➡https://aka.ms/WVDPlaylist
- AVD AMA 28th Aug 2019 Windows Virtual Desktop Microsoft AVD FAQs from AMA
- Microsoft VDI Story AVD Concept Setup Guide Myths Known Issues
- SCCM Intune Support for Persistent Non-Persistent VDI VMs
- How to Connect AVD Remote Desktop Resources Client or Browser?
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…
6 thoughts on “Install Subscribe Windows RD Client for AVD End User Step by Step Guide”
Its a great article, thank you for this. At my workplace, I have been using rdweb to connect to remote desktops and servers on the browsers, it is very slow performance as I am working in the browser. Does this AVD client has any advantages in terms of speed/performance? I would like to explore this.
It’s worth a try. I recommend RD client over Web client. I think the performance of a remote desktop depends on many factors so I don’t think only changing the client would help. I recommend performing an end to end troubleshooting study:
1. Internet connection
2. Latency between Gateway and remote desktop
3. Performance of the OS (AVD Session host)
If the SSO is enabled via ADFS, I’m unable to subscribe to cross domain workspace within the same forest. I login to the hardware device joined to domain a.forest.com and want to subscribe to workspace using domain b.forest.com
When I subscribe->use another account it keeps going in the loop pointing me back to the account I am logged in to my PC with (and not the cross domain account).
One workaround is to add the cross domain account as a new exchange account (select allow my organization to manage this computer). This way the account gets registered in “Access Work or School”, and then I can subscribe using this account.
The remote connection works for a day but next day when I double click on desktop icon it again goes into the loop of asking me to select user account. After I select the cross domain account couple of times, it tells me I dont have a workspace account.
Yes, I’ve seen this issue with some of the users as well. The inprivate window browser might work here but for the RD clients, I think it’s going to be a bit tricky.
One thing that I have not tried is to Set up email discovery to subscribe to your RDS feed https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-email-discovery
Do you think it’s worth a try?
Thanks for your quick reply Anoop,
The email discovery will only allow it to find the feed discovery URL, however, once you click on it, it says you are already subscribed to it (as I have assignments to my locally logged in account also)
The incognito mode works for browser based clients, however not a preferred method for us.
This issue with the remote desktop client is really bothering 🙂
Hi Kedar – I thought so, email discovery will only help to find the feed discovery URL. I think SSO options are not very fabulous. It seems you don’t have 2-way trust between both the domains. I would recommend raising a ticket with Microsoft.