Hi,   I kindly request the restoration of the Storage Sense feature in the Windows 11 multi-session image. This feature holds significant importance and is highly desirable. ... View more

After upgrade my remote desktop screen is full of vertical lines. The attached screenshot shows an example that's not too bad but this happens in all applications, and on the desktop/taskbar. Lots of lines on the login screen. The app is used daily in the same configuration and was fine until latest update. Client and host reboot did not help.   Is it possible to revert to a previous version? This is Remote Desktop Beta 10.8.2 (2057) running on macOS Monterey 12.6.3. Client is Win 10 Pro, Version 10.0.19045 Build 19045     ... View more

Since the clock change on the 29th the RD iOS app is not redirecting the correct time on the server.    I can see this was fixed over summer in the macOS RD app, but it’s still in an issue on iOS. ... View more

Using Mac OS X 12.6.8 and Remote Desktop 10.9.2.  Beginning two versions back (10.9.0?), copy and paste works for a while after launching RD, but it eventually fails when copying from the remote machine to the local Mac.  The failure manifests as a spinning beach ball in the application I'm pasting into.  The paste operation eventually times out, but the quickest way to recover is to quit Remote Desktop and start the whole operation over again with the copy. ... View more

In the current Remote Desktop Client and also in the preview of the Azure Virtual Desktop App, it is unfortunately not saved in which state, and at which position the user has closed the desktop session.   Example: The session starts by default in Fullscreen, the user now switches to window mode and moves the window to the right of the screen. If the user ends the session or disconnects it and starts it again the session is back in fullscreen mode.   With the RDP properties you can influence the window behaviour a little bit, but not in the way that the Remote Desktop Client simply "notices" how the session was ended. Every other Windows program remembers the way (maximized/fullscreen) and position where it was closed.   Please change the behaviour to remember the position in window mode and whether the session ran in fullscreen or window.   ... View more

It would be nice if the iOS RDP app could offer better support for a external display. Some other apps like shiftscreen do this but do not have RDP client support. With this added you could connect a display to your device and use RDP full screen at the external displays resolution. ... View more

Add ability to set Outlook cache to a specific number of days if the profile fails to attach. Currently, FSLogix can set Outlook to online mode if the VHDx container fails to attach to the session.   A new registry key to allow FSLogix set the sync period in Outlook and keep Outlook in cached mode.   Right now we use the “Set Outlook cached mode on successful attach” but this is a simple on/off and in some of our sites Outlook is too slow when running in online only mode, it would be nice to be able to set the cache to 30/60/90 days or whatever on successful attach but leave the fallback position to be something like 3 days. ... View more

It would be really cool if the macOS and iOS clients of Microsoft Remote Desktop sync'd the remote desktops along with passwords via iCloud (or even some other service / mechanism, but iCloud preferred). I maintain a fairly large number of servers for clients and use multiple computers / iOS devices in my day to day work. It would be great if the Remote Desktop lists were in sync across all of my devices. ... View more

RDP for Mac version 10.7.7 has broken multiple monitor support ... View more

Currently the scalability tool is not satisfying in large environment. The tool only starts/stops VM's based on load. This still means we have to provision VM's ourselves. Please provide enhancements to the scalability tool to auto-provision VM's which will save a huge amount of time for the AVD sysadmin.   Perhaps these scalability options can be embedded in the AVD management portal as well. ... View more

Microsoft Remote Desktop client for Mac has a long and ghastly history. (Yes ghastly is the right word and this is not a typo where 'glorious' should have been used.)   Version 1.x had a bug whereby anybody using a Mac with a non-US keyboard was tortured by the software failure to map keys correctly to the Windows session. The most infamous examples of this where that the Mac " (speech marks) key would generate an @ (at symbol) in Windows and vice versa although a number of other incorrect key mappings also apply.   Version 2.x did finally fix this bug.   Microsoft then bought a 3rd party RDC client and this became the next Microsoft official client and I cannot remember if this was released as version 5.x or 7.x. Regardless as this was new/different code it REINTRODUCED THE SAME BUG!!!   Note: I have just reproduced this with Microsoft Remote Desktop 10.8.1 (2048) running under macOS Ventura 13.2.1 with as mentioned a UK Mac keyboard.   Literally thousands and thousands of Mac users throughout the world except the USA have been complaining about this ever since.   When I last was personally victimised by Microsoft with this issue many years ago I also reported this but I found that the Parallels Remote Desktop Client for Mac did not have this bug. The reason being it was not written by American programmers who are wilfully ignorant regarding international keyboard layouts.   Unfortunately I now once more have to use an RDC client and I am finding that the Parallels client whilst still available is not connecting to the Microsoft RDC server whereas the Microsoft client does successfully connect even if it then inflicts cruel and unusual punishment in the form of this now ancient keyboard mapping error.   I have however been able to prove that the RDC client for Mac available here - www.jumpdesktop.com DOES connect to the same Microsoft RDC server and DOES NOT have this keyboard mapping bug. However the JumpDesktop client is a chargeable product.   Microsoft over the decades has in a number of cases committed grave offences against Mac-kind but in more recent times has been comparatively friendly to the Mac using community. Why therefore is this bug which affects potentially BILLIONS of people around the world i.e. anyone who does not have a Mac with an American keyboard still not been fixed?   PLEASE FIX IT AT LONG LAST!   How to reproduce. 1. Connect a non-US keyboard to a Mac, this could be a USB or Bluetooth keyboard, it does not have to be an Apple brand keyboard but genuine Apple keyboards would be the most common use. 2. The Mac should be configured to use the relevant keyboard layout - in my case this is UK but I know that it affects all other non-US layouts e.g. French, German, etc. 3. Connect to a Windows RDC session 4. On the Windows desktop open an app like Wordpad 5. On the Mac type in to the Wordpad document abcdefghijklmnopqrstuvwxyz these all map correctly. Now on the Mac type the @ (at) symbol, in Window you will instead see the " (speech marks) symbol, now on the Mac type the " (speech marks) symbol, in Windows an @ (at) symbol will appear. As mentioned other keys like the \ (back slash) are also incorrectly mapped. 6. Download the trial version of the JumpDesktop client 7. Use JumpDesktop to connect to the SAME Windows RDC server 8. Repeat the same typing test in to Wordpad, this time all the keys are correctly mapped with no settings having to be altered either on the Mac or in Windows.   Conclusion, Microsoft programmers are at fault. ... View more

I regularly connect to a Windows 10 Enterprise (1909) desktop using three monitors from my macOS 12 laptop. Last night the AppStore updated Microsoft Remote Desktop to version 10.7.4 and now it not longer works when "Use all monitors" is turned on. When I connect it loads on only one monitor with a resolution of 1024x768. If I turn off "Use all monitors" I get full resolution on one monitor. To make sure it is not my laptop I downloaded the beta version of 10.7.3 from https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_groups/all-users-of-microsoft-remote-desktop-for-mac and confirmed that is worked correctly with that version. ... View more

The ability to exclude specific files/directories from ODFC containers like we can with Profile containers.  We’ve discovered some pretty severe bloat occurring (specifically the issue with %APPDATA%\Microsoft\Teams\Service Worker\Cache Storage) and the ability to exclude that from the ODFC container would save a huge amount of disk space when multiplied by our thousands of users. ... View more

English is entered normally. If you type Korean, consonants and vowels are repeatedly entered and cannot be used normally. ... View more

I'm having issues after upgrading to Mac OS Sonoma with audio disconnecting when using MS RDP to access a Windows PC and use Teams. When I initially connect to Teams, audio input and audio output is working correctly. After a few minutes, Teams will report audio device microphone is disconnected or not working and then no-one can hear me speak. I can still hear them, but they can't hear me. If I leave the meeting and re-join it works again for a few minutes and then the same issue happens again. Please fix ASAP. ... View more

Currently I'm working with MS Remote Desktop for macOS Beta 10.9.2 (2147) to use customer workspace. I've left all preferences at default and only configured the workspace user. Each time I quit the app the workspace is deleted and I have to set up again. With previous (beta) versions (i.e. 10.9.0) I did not have similar problems. ... View more

Recently, my Remote Desktop application has been losing my configuration daily.  I have to click "Add Workspace" and put the URL in again.  Surprisingly, this even happens while I am actively connected to my remote workstation.   I'm on Mac OS Ventura 13.4, and recently updated the client to 10.9.0(2140), hoping that would fix the issue.  It did not.      ... View more

Cannot enter Full Screen on External display on iPad OS.   iPad Pro 12” M2 External Display Microsoft Remote Desktop App   Using Remote Desktop on External Display does not scale to entire window and will not enter full screen. ... View more

Hello, unfortunatly it is not possible to use the complete screen Size on an external Display on an IpadPro (M2) with Stage Manager.   The Microsoft-Remotedesktop app is limited to a certain size on an external Display.    Working from home would be so much better if the RDP app. would support full screen resolution on external Displays.    Thanks and best regards Michael   ... View more