MacOS Windows App Dynamic Resolution not working
When using MacOS Windows App 11.0.5, if the AVD icon settings are left un-customised, the App does not honour the host pool setting to enable Dynamic Resolution. Dynamic Resolution only seems to work if it's explicitly enabled on each AVD icon within the Windows App on the client device. Our users expect Dynamic Resolution to work by default. It's enabled in the host pool and it previously worked on the RD Client.
Mac - Microsofft App - client - unable to change or save credentials - can't access default keychain
I'm unable to save/update credentials to my keychain with this app. Locking/unlocking/rebooting does not fix. Everything else seems to be working fine so I'm assuming this new app is broken. MBP M3, running Sonoma. As an aside, please allow us to disable the jumbo text/icons and change the font size in the device list... As is the the list is a waste of screen space for what should be a categorized list of hostnames. Maybe this makes sense for fat fingers on a phone, but not a 4k monitor w/mouse or trackpad.Remote Desktop for Mac will not connect over iPhone tethering
Remote Desktop for Mac, current shipping 10.9.6 (2188) and beta 10.9.7 (2192) will not connect workspaces to our RemoteApp servers when our MacBooks (M1 Pro 14" and 16" Sonoma 14.3.1) are tethered to our iPhones (13 Pro and 15 Pro IOS 17.3.1. It works fine using wired or WiFi Ethernet. This has also been the case with older versions of the software. We rely heavily on tethering to provide support or carry out cloud software development and have to revert to using Jump Desktop, which works perfectly when Remote Desktop continues to fail to connect. However, our clients do not have Jump Desktop as an option. We have recently swapped from Vodafone to O2 and the problem exists with both. I believe this problem has crept in with the more recent versions of Remote Desktop for Mac. Error message attached
macOS Dock Icon Does Nothing When Clicked
Steps: 1. Open Windows App Preview 2. Close the main window 3. Click on the Windows App Preview icon in the macOS Dock Expected: The main window opens again (I believe it's called the "Connection Manager") Actual: Nothing at all happens. This is frustrating to me.
Windows App does not forward YubiKey
Our organization require YubiKey to connect to VPN to access specific resources. Problem is when using YubiKey from Windows App it does not get forwarded to the server machine. When using Windows 10/11 machine to connect from everything works. YubiKeys don't work with Windows App (or old RDC app) from macOS machine
Support URI schemes like ms-avd:connect across all platforms in Windows App
https://learn.microsoft.com/en-us/azure/virtual-desktop/uri-scheme We would like to request the implementation of support for URI schemes, such as ms-avd:connect, in the latest Windows App. Currently, this feature is available only in MSRDC. We are developing a web app portal running in the browser that allows users to connect to their Azure Virtual Desktop instances. Having this feature in the Windows App across all platforms (including Windows, macOS, Android, and iOS) would significantly benefit our development and provide a seamless experience for our users.Opening rdp:// URLs seems broken on M1 or macOS 12.2
The ability top open a Microsoft Remote Desktop session from the command line on a mac is something I've used and love for years. It still works fine in the RDP (v10.7.6) running on my older machine running macOS 10.15, but the same version on a new M1 machine running 12.2 doesn't open the exact same links. Here's a stripped down minimal example: open "rdp://full address:s:server.example.com" It launches RDP client and tries to connect to the indicated server on the x86 machine, but throws this error on the M1 machine: No application knows how to open URL rdp://... There was mention of a new URL format in recent release notes, but it seems very bare-bones. I couldn't find any way to specify the options the old rdp:// format allows. Can the old format still work on M1 machines at least until the new ms-rd:// format is fleshed out more?
