Latest Remote Desktop client not starting on W10 LTSB 1607
Hello. We're using about 50 thin-clients to connect to our AVD systems. The HP t530 thin-clients are running Windows 10 Enterprise 2016 LTSB / ver 1607 / build 14393 / RS1 and have the Remote Desktop client for Windows (msi) installed, with auto update enabled. This all worked fine until the most recent releases of the Remote Desktop client. Starting with version 1.2.6186 the app simply doesn't start anymore. There's no gui, no errors, nothing. Just for a few seconds the spinning blue circle next to the cursor. It does create msrdcw_xxx.etl files in %temp%\DiagOutputDir\RdClientAutoTrace, however i couldn't locate any obvious errors in it. Upgrading to 1.2.6187 does fixes the problem temporary (but that's probably because it's actually based on the older 1.2.6081 version). Upgrading to the latest releases 1.2.6188, 1.2.6227 and 1.2.6228 reintroduces the problem. It's not something in the thin-client image, also did a fresh Win10 1607 install with latest Windows Updates, same problem. Is there anything i can do or try, except blocking all future updates and staying on 1.2.6187?
Single-Sign On
After troubleshooting an issue for a customer, we determined that the prerequisites for enabling SSO at the AVD host pool level is not strictly enforced when a user goes to execute the SSO workflow from MSRDC or the Windows App. Meaning, that if an administrator does not enable the -IsRemoteDesktopEnabled flag on the Service Principals "Microsoft Remote Desktop" and "Windows Cloud Login" respectively. Setup: Deploy Entra ID Joined session hosts to a host pool and enable the "Microsoft Entra single sign-on" RDP property to "Connections will use Microsoft Entra authentication to provide single sign-on" or update the RDP connection string with 'enablerdsaadauth:i:1'. Result: User will not receive the 'Windows Security' dialog box to access the session host with their Entra ID credentials. Caveat: Be aware that to sign in with Entra ID credentials, minimally, the host pool RDP settings must contain 'targetisaddjoined:i:1'. Microsoft states this is going away and blending into 'enablerdsaadauth:i:1', which also enables SSO. It seems a bit odd of a move in my opinion and having two separate RDP properties makes sense if a company does not want SSO. But it is in alignment with Microsoft's push for passwordless authentication. For the Microsoft AVD team, why does this behavior exist and is it on the roadmap to be fixed if it's a known gap?
Webclient offline download fails
I'm following the instructions here to download the webclient to install on a server without internet https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remote-desktop-web-client-admin#how-to-install-the-remote-desktop-web-client-without-an-internet-connection and getting an error when running Save-RdWebClientPackage "MethodInvocationException: Exception calling "DownloadFile" with "2" argument(s): "An exception occurred during a WebClient request.""macOS 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?AVD 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.
Remote 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 HelenaNot 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.Microsoft 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 thisDifferent 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,
