Forum Discussion
New Windows App with AVD remote apps/desktop
Microsoft announced that Remote Desktop app would transition to Windows App so we've been testing it out and are looking for a place to offer feedback on Windows App. Have submitted Feedback via the Feedback option but no idea if others are experience similar or if certain changes are being considered, so starting this discussion to see if other AVD users have been trying the Windows App and how their experience has been? Some of the things we have observed is launching/starting a connection to a remote app or desktop is much, much slower via the Windows App vs. the Remote Desktop app. After connected, it seems to be ok, but when launching it is painfully slow most of the time. Also, we work from multiple workspaces with some users having a large number of apps assigned to them, you can no longer hover over an icon for a remote app and see which workspace the session is from. (ex: if you work on a dev, pre-prod and prod environment, you can't easily see which session is which from task bar now)
Also, the size of the remote app 'icons' is huge - we would like to see an option to be able to size those down more like the sizes of the icons in Remote Desktop app. Understand you can pin to the home page, but depending on how many remote apps are assigned and used regularly it can be lots of scrolling to find what you are looking for (have to use the search option often as there isn't a sort by name option, or such)
And from a security perspective, the way our conditional access rules are written, the new Windows App looks like a 365 app and we have quite strict rules for this. We are hoping to see the new Windows App change how it is identifying to allow more control/flexibility with conditional access rules for the new app. Will likely create a support ticket for this issue.
Please share your experiences with the Windows App with your AVD usages.
- We started using the Windows app last month and have encountered several challenges that I’d like to highlight.
Firstly, there doesn’t seem to be a way for users to manage a connection as you can with the Azure Remote Desktop Client or the standard Remote Desktop Client (e.g., right-clicking on the app in the system tray to get session information or disconnect).
Secondly, there is a noticeable delay of 10-15 seconds before the app responds, which may be acceptable for experienced VDI users who expect some latency, but 10-15 seconds is quite long. Less experienced users may be inclined to repeatedly click the app, thinking nothing is happening, which could cause confusion.
Lastly, we've noticed that when users are prompted for their credentials, the app displays a GUID instead of the app name. Since we use multiple apps with different accounts, this can be confusing, even for our more experienced users. It may be a configuration issue on our end, but we haven't been able to identify a solution for this.
Any suggestions or insights would be greatly appreciated.- we have experienced the same - still looking for improvements for these as well, have been reluctant to have even a small set of our users outside of IT area trial it at this point, hoping to see improvements still..... thank you for sharing this as I have been struggling to find anyone else using this and sharing their experiences yet.
- If a user clicks that Send Diagnostics button, where does that go? Is it expected that an IT admin would tell a user to click that button so the IT admin knows where to look? Does it just go to log analytics if you have that configured?
If it's a localy run AVD deployment then you should see it in %LOCALAPPDATA%\Microsoft\Remote Desktop\logs.
