Azure WVD client

0 vote

avatar

Hi,

It will be cool if we can add sessions entry with WVD client (Azure Windows Virtual Desktop)

Is it on the roadmap to support the WVD client in RDM ?

Thanks for the feedback

All Comments (36)

avatar

Unfortunately it's not on our roadmap. We have no idea how we could do that for now.

Regards

David Hervieux

avatar

Has this changed? Is there really no plan to add workspace style managed resources to RDM?

avatar

Hello,

It still an undocumented feature from Microsoft but are making progress. I can promise you anything but it's one of ou R&D project.

Regards

David Hervieux

avatar

Hello,

Any progress here will be great to hear. We are now having multiple WVD's to be accessed and have to use other tool and love to see Devolutions RDM to have the feature.

thanks

avatar

Same here. Kind of surprised it wasn't already in there. Hope you are making progress with Microsoft!

avatar

Unfortunately we haven't made any progress. There is not documentation available.

Regards

David Hervieux

avatar

Hi,

I've inquired about possible AVD integration with RDM with someone who works at Microsoft, and while there would still be a lot of research work on our side (starting with setting up a test environment!) this is something I could investigate soon.

Simply put, it's all undocumented, so we'd have to figure it out ourselves. One thing I was told, however, is that the .RDP files fetched by msrdcw.exe (the simple UI that connects to the AVD webfeed) should remain the same over a long period of time, and msrdc.exe should do its own connection to Azure with a separate prompt.

This means it should be possible in theory to copy the .RDP files and use connection entries either linked to the file on disk, or imported from the .RDP file, and launch them with MSRDC.

We now support MSRDC in RDM, so we are getting closer to a possible integration: https://blog.devolutions.net/2022/03/msrdc-is-now-supported-in-remote-desktop-manager/

I don't know where the .RDP files are stored locally by msrdcw.exe yet but that would be a first step. Try using the .RDP file link option in RDM, this should work, and then try importing the .RDP files. We would likely need to add support for a few MSRDC-specific options to make it work properly for import/export from an RDP file.

Last but not least, connecting to the webfeed and fetching the .RDP files within RDM would require us to decompile the original app and figure out the calls it makes to Azure. It's possible, but there's an unknown effort associated with it, so if what I described above would fit your needs, I say we start with that.

Best regards,

Marc-André Moreau

avatar

We'd love this too, but gut feel is Microsoft aren't going to release any documentation on this

avatar

Hi,

We are well aware of the demand for Azure Virtual Desktop support, and have been working hard on a solution, despite the lack of documentation or exposed interface from Microsoft. We've at least made some significant progress last week, with a first AVD connection launched from RDM with MSRDC in external mode. There's still a lot of work to be done, but simply put, it means we've at least got the .RDP file import/export for all the newer AVD options working, and managed to force MSRDC to accept a locally-modified .RDP file for AVD through API hooking: https://twitter.com/awakecoding/status/1553099268805869568

AVD RDP files are signed and published by a web feed, and contain all the .RDP client options. As you have probably noticed, the MSRDC UI provides very little client-side settings: that's because they cannot be controlled client-side. MSRDC rejects .RDP files for AVD connections that aren't signed, and since the original AVD RDP files are fully signed, nothing in them can be modified. Since RDM creates a temporary .RDP file locally to launch connections, I had to find a way to work around that. This slowed us down by a week of additional research, but at least we've got over it through API hooking.

We still have to expose all the newer AVD RDP options in our UI, fix credential injection for AVD connections, prepare the RDP API hooking module to be enabled by default, etc. The current focus is to at least get AVD connections working with MSRDC in external mode with credential injection for the target RDP server for the next major release, 2022.3. Injecting or managing the first login to Azure will be a project in itself, so you'll still need to select which account to use from the embedded web login that MSRDC shows on startup. As for supporting AVD connections in embedded mode, I'll try and emulate what MSRDC does internally, but I wouldn't be surprised to hit blockers there as well.

Best regards,

Marc-André Moreau

avatar

Hi,

Here is an update on our progress with Azure Virtual Desktop in Remote Desktop Manager:

https://blog.devolutions.net/2022/08/extending-the-microsoft-rdp-client-with-api-hooking/

Best regards,

Marc-André Moreau

avatar

Hi Guys,

Really appreciate your work on this! Would it be possible for us to get an update on the teams latest progress?

Kind Regards,

Jake

avatar

Hey Folks,

I, too, would love to hear about any progress on this!

Cheers...

Cary

avatar

Also keen on an update here

avatar

Hi,

We definitely need to make proper documentation for AVD support in RDM, but in the meantime, here's a summary of the current level of support.

The very first thing you need is to use MSRDC to connect to the AVD webfeed using your Azure AD account. This part is not handled by RDM, and it is required to grab a copy of the AVD .RDP file with all the right parameters (do not try and configure it from scratch, there are too many internal options you can't just figure out by other means):

Once you have the webfeed loaded in MSRDC, go to %LocalAppData%\rdclientwpf, you will see a list of GUID-named directories with .RDP files in them, this is what you need to import in RDM:

Once the entry is imported, you can rename it (it'll use the file name GUID as the initial name, so not very useful, unfortunately), then go in the Advanced tab to set "RDP Version" to "MSRDC". Also, double-check that the Display mode is set to "External": AVD connections are *not* supported with the embedded mode because of the lack of support for third-party AVD integration by Microsoft:

Try to launch the AVD connection with MSRDC - you should normally see a prompt to select the Azure AD user for the AVD connection:

Now while there is no way for RDM to manage this Azure AD authentication context or automate the login from injected credentials, it was a bit annoying to manually select the account every time. This is why I have at least made it possible to pre-select the account with RDP Gateway credentials where you set the username but no password (it'll be ignored anyway if you try to use it):

AVD is really a fancy RD Gateway in Azure that requires an Azure AD account to talk to in order to open a connection tunnel. By setting the username there, we just pass it on as a command-line argument to msrdc.exe to pre-select the account to use, but we have no control beyond that.

Last but not least, you can then set credentials for the RDP connection itself in the regular way. If you have non-Azure AD accounts on the target machine, it should work out of the box, but if it's Azure AD, you'll need to check that "Azure AD host" checkbox and go through the same level of pain required to get Azure AD + RDP NLA to work without AVD (that's an entirely different topic, unfortunately):

Best regards,

Marc-André Moreau

avatar

Thanks for the update, Marc-André

Unfortunately, I can't find the folder rdclientwpf in local appdata, even after reinstalling the MSRDC app from the windows store, and readding my workspace.

I'm wondering if MS have changed something? or am I being an idiot?

avatar

Hi,

I'm wondering if MS have changed something? or am I being an idiot?

It's not you, it's Microsoft ;)

Don't use the Microsoft Remote Desktop application from the Windows Store, it is confusingly similar to MSRDC, but it is MSIX-installed, uses weird paths like %LocalAppData%\Packages\Microsoft.RemoteDesktop_8wekyb3d8bbwe for internal storage, and worst of all, we can't integrate it because of MSIX application virtualization that prevents us from loading the RDP ActiveX DLL directly (rdclientax.dll in MSRDC).

Instead, install the real MSRDC, the one not distributed through the Windows Store and that can be installed with an MSI installer instead of MSIX:

https://learn.microsoft.com/en-us/azure/virtual-desktop/users/connect-windows

I just tried the Windows Store client again for comparison, and noticed that even for AVD you need to give it the full URL (https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery) while you can skip this step with MSRDC, so not all is lost.

Best regards,

Marc-André Moreau