Remote Desktop Client
17 TopicsmacOS Remote Desktop client app - automatic logon (no credential prompt)
Sorry if this isn't a good place to post this question. But I'm trying to locate the right place for macOS RDClient feedback now that https://support.microsoft.com/en-us/topic/uservoice-pages-430e1a78-e016-472a-a10f-dc2a3df3450a. I am trying to automate the launch of RD Client without prompting for a credential. The macOS RD client (GUI) allows storing passwords securely in the macOS Keychain and will use them to automatically log on when double-clicked from the bookmarks. On Windows, I understand there is a way to use a little-known "password 51:b:<myEncryptedPassword>" attribute to pass an encrypted string as a password from the .RDP file. AFAICT there is no way to completely automate the RDP logon without password prompt on MacOS, for the following reasons: - No way to pass a password credential (encrypted or otherwise) via https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-uri - No way to control the RDClient app via AppleScript - Bookmarks within app support saving credentials in Keychain, but there's no way to initiate a connection to a 'bookmark' via the URL scheme (bookmarks are stored in a totally separate SQLite database, and password is not contained within) - https://github.com/PowerShell/PowerShell/pull/9199, so the hidden `password 51:b:myEncryptedPassword` attribute does not work. - No way to save an .RDP file or any shortcut/alias that includes the password (this would be bad for security even if it were possible!) Anyone got an ideas here?3.7KViews1like1CommentAVD remote desktop client Bug
Remote desktop client when connected to AVD workspace, breaks desktop application drop down list and pushes it in upper right corner of the screen. Only reproducible in Remote desktop client, everything works as expected in web client. Remote desktop client: 1.2.4240.0 (x64) Bug Screen Shot. Expected behavior.Solved3.3KViews2likes5CommentsNot able to open 2 remote apps
Hi all, We're experiencing a problem when we open two remote apps at the same time using rdpw files. Those remote apps are published in different host pools and workspaces in the same tenant. When doubleclicking the first rdpw file the client will connect to AVD and the first remote app is useable. When doubleclicking the second rdpw file (while the first remote app is open) the RDP client freezes or displays error 0x3000008 when connecting. This behaviour is not reproduceablein client version 1.2.2606.0 but the error is reproduceable from version 1.2.2688.0 and above. We haven't tested the versions in between. This behaviour is not reproduceable when we use the feed in the Windows Desktop client but the error is reproduceable if we open the rdpw files in the File Exporer.3KViews0likes7CommentsScroll bug of Microsoft remote desktop android app when use Samsung Dex mode
Dear Administrator, I wrote your e-mail address: Microsoft Remote Desktop for Android But I got auto reply with link which can't work. So I write this. I realized that to scroll very hard in any application on another Windows 10 PC which I joined with Samsung Galaxy S20 FE phone in DEX mode (connect a mouse, a keyboard and a monitor to the phone). Sometimes I couldn't scroll with the mouse scroll button, what I experienced for example in Microsoft Excel, Browser. I know, I use your app in a very special way but you could fix this problem, make my job easier. Thank you in advance for their help, I look forward to your reply. Yours sincerely, Balazs2.8KViews0likes0CommentsDifferent Versions Remote Desktop Client - Google Play Store
Hi, We setup 2 ZEBRA TC26 Android devices with SOTI Mobile Device Management. Both have the same OS and build version number. We noticed that the remote desktop app’s are not the same on these phones. On the first one we have version : 10.0.11.1140 which is a version higher then there is available on the microsoft page : https://docs.microsoft.com/nl-nl/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients On this version, when we start a Workspace connection we could not click on ‘Never ask again for connections to this PC’ : The user receive always this message. On the other Zebra TC26 we noticed that they have the latest official version : 10.0.10.1129 In this version we could mark this setting as expected so no issues here. We have allready uninstalled the remote deskop app that has the higher version, but the higer version always comes back on that mobile. Is there any workaround, solution or is this a BUG ? Thanks in advance. Best regards,1.9KViews0likes0CommentsCant get the client computer name with Remote Desktop Client
When you connects to a RDG with the old MSTSC.exe, the client pass the computer name to the server and you can authorize the access by the computer name: Equipo cliente: Id. de seguridad: NULL SID Nombre de cuenta: (ComputerName) Nombre de cuenta completo: - Identificador de estación llamada: UserAuthType:PW Identificador de estación que llama: - But when you use the new remote desktop client, the app pass to the server allways the name Cadrima Equipo cliente: Id. de seguridad: NULL SID Nombre de cuenta: Cadrima Nombre de cuenta completo: - Identificador de estación llamada: UserAuthType:PW Identificador de estación que llama: - Please create a bug and fix that. Thanks!1.8KViews0likes0CommentsHow to disable usage data in Remote Desktop client
Hi, As an IT admin, I wanted to disable the "Send Usage data" in Remote Desktop Client. Can someone please tell me how can I disable this option for users? Also can you please tell where this setting information is getting stored if I disable(turn off) manually? Regards, Anique1.7KViews0likes1CommentMicrosoft Remote Desktop Client bans adding same workspace URL with different logins/emails
It's common to have multiple Azure workspaces, via logins/emails from multiple orgs. However they all have the same URL, https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery" (i.e. https://rdweb.wvd.microsoft.com). And the Microsoft Remote Desktop Client and Microsoft Remote Desktop Beta both forbid you from adding another workspace from the same URL. This is asinine. Workspaces are distinguished by login/email, not just URL. Microsoft killed the UserVoice bug reporting forum for the RDC app, even though the app's "Report an Issue" button still takes you there. So there's nowhere else to report this1.6KViews0likes0CommentsRemote Desktop client for Mac - email discovery
Dear all, we are currently offering a hybrid environment to our users (classic RDS web access servers PLUS Azure Virtual Desktop resources). For AVD, we enabled email discovery, which works perfectly fine on the Windows Remote Desktop client. On macOS clients, we need to advise users to subscribe to their AVD workspace via URL. If they put in their email address, the autodiscover offers the classic RDS web access only. Could this be changed, so users with macOS clients can use email discovery for AVD, too? Thanks in advance! BR Helena1.2KViews0likes0CommentsSecurity Risk: iOS Remote Desktop Client accepting invalid RD Gateway Certificates
After accidentally importing a wrong certificate (CN mismatch) for our RD Gateway jump host, some mobile users were starting to complain immediately because they were getting certificate warnings. After the first report, I verified using my fully updated iPhone with the latest Microsoft Remote Desktop Client (10.3.6) but did not get any certificate warnings with a pre-configured connection using that RD Gateway. However, when using the Workspace Feed (aka RD WebAccess), there was a certificate warning when refreshing the feed. I then cross checked with the Android RDP Client and it showed the RD Gateway Certificate warning as expected. Well, I was a bit baffled and did some experiments: It seems the iOS RDP Client accepts any certificate without checking, self-signed, wrong CN, ... everything seems to be happily accepted ! I even tested with an old Pad using the abandoned Version 8 iOS client and it had the same issue. I know that Apple users love it if something just works, but in this case this would go way to far 😉 And no - the client did not connect directly to the target RDP server - as in skipping the gateway. That connection would not be possible without gateway and the connection also was confirmed in RD Gateway Monitor. Is it possible that Microsoft has this "feature" in the iOS RDP Client, like forever, and I'm the first to notice?1.1KViews0likes0Comments