remote desktop
52 TopicsBug in RDS Web Client - Copied text in RD session improperly encoded
As the title describes, there appears to be a bug in the HTML5 web client for Remote Desktop Services. This bug is present in both 2.1.85.0 and 2.1.87.0, and possibly earlier. When text is copied to the clipboard within a remote session (tested via a published RemoteApp), the text will occasionally be stored into the clipboard of the local machine encoded in UTF-8 instead of UTF-16 as it is supposed to be. When pasted into an application on the client machine, the UTF-8 encoded text (stored as CF_UNICODETEXT) is interpreted as UTF-16 (as that's how it's supposed to be encoded in memory as that's what Windows uses internally), resulting in meaningless output/mojibake. As an example, the text "Given" is copied from a Remote Desktop session (via the web client). The endpoint has these formats on the clipboard: Copied text CF_UNICODETEXT hex (padded) CF_TEXT hex Decoded text - UTF-8 Decoded text - UTF-16LE Given 47 69 76 65 6E 00 00 00 3F 3F 6E 00 Given 楇敶n The behavior is seemingly random. Most of the time, text is copied without issue. Once out of every 5-10 times, however, the UTF-8 encoded text is incorrectly written to the clipboard. Some additional information about this behavior: It only happens when using the RDS web client. The native RDP client does not exhibit this behavior. This has only been observed on Windows clients. It hasn't been observed on other client platforms, but testing has been minimal. The client browser does not appear to factor into the bug. It has been observed in Edge, Chrome, and Firefox. The issue is unrelated to the text copied. The same text, from the same application, can produce both outcomes when copied. The application being pasted into seems to be irrelevant. Has anyone else seen this behavior?134Views0likes2CommentsRemote Desktop Web Audio Not Passing (Correctly)
Hello! I manage an RDS farm (WEB/GW, CB, DB, HST etc) at work, and it's been working great aside from Audio Passthrough. Clients will connect to the RD Website and then launch a remote app of their choosing. However, when the client is on the remote app PC and uses their audio (via an app or just using mmsys.cpl) the remote session will just freeze and be unusable. All RDS Infra is on at least Win. Server 2019+. All GPO Settings have been properly configured, as well as collection, CAP/RAP, and browser settings. I have confirmed launching RDP (mstsc.exe) session from my local laptop to the remote app PC (through the HST) does work without any issue, so I am led to believe there is something wrong with RD Web. RD Web Client Pkg is on the latest version. Any advice is greatly appreciated as I am banging my head against the wall trying to get it to work with RD Web. Cheers373Views0likes1CommentClassic outlook - Teams add-in not loading
We recently had a partner experience an issue that is causing the teams add-in feature to not load properly in classic outlook when creating a new meeting. For some background info, we are using a Virtual environment within remote desktop running windows 11. Our servers are provided by AWS. The issue only began as recently as December, as far as we can ascertain with the customers information. I have noticed this issue occurs with numerous partners but is inconsistent, as some load and others do not. I followed troubleshooting steps such as an uninstall/reinstall, verifying the load behavior in the registry was set to 3, and tried to re-register the related teams.addinLoader.dll. A colleague did implement a script to the environment task scheduler that will run every time outlook is launched to re-install that add-in as a break fix, but this still requires closing outlook and reloading it to work. I was curious if anyone else had encountered this within remote desktop with classic outlook, and if they had any success in fixing it. The easiest thing, obviously, is moving over to new outlook since teams' integration is native, but we have some that prefer classic. Though, with it being retired in 2029 it may be worth starting the move away while in a remote environment.1.4KViews0likes2CommentsMultiple terminal servers setup
I'm looking to replace my old (like really old 2k8 r2) terminal server with 3 new ones (win2k5). Instead of each department going to one server as it is now, I would like to break up the departments to a specific server. For example. HR and Fiscal go to server 1, C suites go to server 2, etc. How can this easily be achieved? Can I give them all the same virtual server name, group the servers together, and terminal knows which one to go to based on the users group or do I have to make 3 individual servers and tell each division to go to server1 or server2? I've thought about just grouping them together, having roaming profiles and allowing terminal to pick the server based on load but, I don't want to have to fight the terminal server vs their desktop computer when they are in the office. Not to mention the amount of storage needed for all of the profiles. Any help or suggestions would be appreciated.148Views0likes0CommentsRemote Access via HTTPS RDP Web Client on Windows Server 2022 - Installation Issue Solved .
Step 1: Install Remote Desktop Services** * Install the **Remote Desktop Services** role using (note role and feature installation) * Choose **Quick Start** for the deployment type. * Select **RD Connection Broker** as the default server. * Choose **Session-based desktop deployment**. > *Note: If you need a virtual machine–based environment, ensure Hyper-V or another virtualization platform is installed on the server.* * The following roles will be installed automatically: * Remote Desktop Session Host * Remote Desktop Gateway * Remote Desktop Licensing * Remote Desktop Web Access --- Step 2: Configure Core RDS Components** Configure all the following roles on the **same server** (or on different servers if desired): * RD Connection Broker * RD Gateway * RD Licensing * RD Web Access Use a **domain user** account that has administrative privileges (Domain Administrator or Server Administrator group). --- Step 3: Configure Certificates** * Open **Server Manager** → **Remote Desktop Services** → **Deployment Overview**. * Click **Tasks** → **Edit Deployment Properties**. * Under **Certificates**, create a **self-signed certificate** and apply it to all roles: * RD Connection Broker * RD Gateway * RD Licensing * RD Web Access > Make sure all roles use the **same certificate**. --- Step 4: Configure RD Gateway Policies** * Go to **Tools** → **Remote Desktop Services** → **RD Gateway Manager**. * Create a policy for: * **User authentication** * **Network access** > Allow only ports **443** (HTTPS) and **3389** (RDP). --- Step 5: Configure Quick Session Collection** * If a collection is not created automatically, create one by: * Navigating to **Server Manager** → **Remote Desktop Services** → **Collections**. * Choose the same server and create a new **QuickSessionCollection**. * Under **RemoteApp Programs**, add and publish the desired programs. * Check accessibility by browsing to: `https://<your‑FQDN>/RDWeb/` --- Access via Web Only (Web Client Setup) -------------------------------------------------------------------- To access Remote Desktop only via the browser, install the **Web Client package**. --- **Step 1: Export the Self-Signed Certificate** * Open **Run** → type `certlm.msc` * Navigate to **Personal** → **Certificates** * Select the certificate created for the **RD Connection Broker** * Export the certificate (e.g., to `C:\temp\abcde.cer`) --- #### **Step 2: Install and Publish Web Client Package** Open **Windows PowerShell 5.1** and run: ```powershell Install-Module PowerShellGet -Force Install-Module RDWebClientManagement Import-Module RDWebClientManagement # Clean up any stale IIS locks Reset-IISServerManager -Confirm:$false Remove-Module IISAdministration -ErrorAction SilentlyContinue Import-Module RDWebClientManagement # Install the Web Client Install-RDWebClientPackage # Import the exported certificate Import-RDWebClientBrokerCert "C:\temp\abcde.cer" # Publish the Web Client for production Publish-RDWebClientPackage -Type Production -Latest ``` --- #### **Step 3: Access the Web Client** Visit: `https://<your-serverFQDN>/RDWeb/webclient/index.html` If the page does not appear: * Restart the **Default Web Site** in **IIS Manager**. * Ensure the **webclient** folder is present under the IIS site directory. * Check if the correct certificate is applied under **Bindings** in IIS.3.1KViews1like1CommentWindows App, pasting files hangs OS
Hi all, We’re experiencing an intermittent but frustrating issue when using the Windows App to connect to our Azure Virtual Desktop environment. Issue: When users attempt to copy and paste certain files from their local machine to the remote session, the operating system on the remote side hangs. The mouse still moves, and the clock continues to tick, but: -Start menu becomes unresponsive -Taskbar icons stop registering clicks -Desktop icons are frozen -No error messages appear This occurs sporadically and seems to affect files of varying sizes and types — 100KB up to 20MB. What we've tried: -Updating the Windows App to the latest version -Verifying clipboard redirection is enabled -Using MSTSC, and the Remote Desktop Store App. These work but don't support Session Pools, Remote -Apps, or SSO. -Using RemoteDesktop_1.2.6228.0 (MSI Install) Has the same issue as Windows App Environment: -Remote app hosted in Azure Virtual Desktop (AVD) -Users connecting from Windows 10/11 clients -Windows App version: 2.0.419.0, 2.0.420.0, and 2.0.500.0 All ideas welcome - is a major disruption to our business processes.2.8KViews0likes25CommentsRemote display not changing to 1920 x 1080
With initial versions of Mixed Reality Link the remote display in the Meta Quest was looking great, crisp and big, but suddenly it stopped doing that. Since the latest update of Mixed Reality Link the display keeps the same resolution from my physical monitor, which makes it look squeezed and with big horizontal black bars in the Quest window. Quest 3 Meta Horizon OS v72 best regards, Ramon510Views1like1Comment2025-01 Cumulative Update for Windows Server 2019 KB5050008 Causing Slow Performance and Freezing
We had this same problem back in August with the 2024-08 Cumulative Update for Windows Server 2019 KB5041578, slow performance and freezing. Here we go again with KB5050008. Remote Desktop does not respond. It freezes up for minutes. We have SQL Server and Terminal Server on this Windows Server 2019 and people can't access it through Remote Desktop. I had to uninstall KB5050008. The server went back to normal. I don't a repeat of this with every Windows Server update. Please advise.3.1KViews0likes2CommentsRemote Desktop permissions
I have setup Remote Desktop on my Server 2022. Admins are able to log in without issues. I have added users that are not part of the admin group in GP and on the remote desktop element. But the users that are not part of the admin group are not able to login. Any suggestions?232Views0likes1CommentAD DS Users in Remote Desktop Users group receive not authorized for remote login
Hello, thanks for checking! My AD DS config was lost. I have now built a new PDC for AD DS. I have recreated users and given them remote permissions via remote tab on user details, I have added them to administrators group, and I have added them to Remote Desktop Users group. I have joined "PC1" I can confirm the user can login via console, but when attempting to remote in, is receiving "The connection was denied because the user account is not authorised for remote login." The only user that can use RDP at this time is domain 'administrator'. It was working previously. I have verified that the PC1 has remote desktop enabled, and can connect via domain 'administrator' I would appreciate any insight into this matter!Solved672Views0likes2Comments