We have a remote desktop infrastructure with multiple Brokers and Gateways that redirect connections to a pool of servers. All of the servers are Windows Server 2019. After a user logs off of their session that was connected through the gateway, the rdp
client never exits and stays at a black screen.
Is there a solution to this issue?
Thanks
Hello all,
I have some remote desktop services servers that enable me to access workers computers for repairs. Inside of server manager every day I have to re-add my three RDS servers, they never save from day to day. Does anyone know a solution to this?
I have RDS farm deployed on server 2019. We have published remote desktop app so that the users can remote on to their work PCs from home. This works fine for windows and mac users from home.
For windows users I can see the session on one of the session host servers, but for Mac users using the "Microsoft Remote Desktop" app i can't see the session.
Also we have applied the setting so that users cannot copy and paste to and from the remote PC but this doesn't get applied to the Mac users. Is there a way to disable copy paste?
Hello,
We have a potentially unique use of RDS to broker/load balance the connection to a 30+ physical (not vms) windows 10 machines pool (educational computer lab). The intent is to have individuals interface with the RDS broker, which will connect them to an available Windows 10 machine. What we'd like to avoid, is publishing IP/HOSTNAME of all available computers in the lab and have individuals manual cycle through each until they find availability, or to assign groups to a single machine, as this seems to be an administration nightmare.
Is this possible with RDS, as I've unfortunately not been able to find anybody asking a similar question? Is it as simple as using the redirection function to a VM pool, but pointing it towards a physical machine pool?
Any resources are appreciated, as well as any other methods of achieving the intend connection brokering to available machines.
Thank you,
J
Ok so after battling a few config options I finally have a new RDS environment running. Its on Server 2019 hosted in Azure, sitting behind an Azure WAF v2, with MFA authentication on the Gateway (using NPS extension).
So evrything is working now, users can connect and all is behaving as it should, except for a small few users who are experiencing performance issues with slow performance, but only with published Remoteapp's.
Just to confirm, the RDS servers are all very high spec and none of them are remotely approaching resource limits (none even going above 40%). Also one of the test machines experiencing performance is my own Desktop, an AMD Ryzen 9 3900X CPU with 64gb ram, 11gb RAM video card. Im pretty certain the local resources on this desktop are not a problem. However if I try to connect to a published remoteapp the redraw rate is very bad and it appears as if the connection is very laggy. Yet, it I connect to a remote desktop session (same environment, same servers, same everything) the performance is lightning quick. This lag only occurs with remoteapp.
Also to confirm its not a connection speed issue. I have 3 other Windows 10 devices here and performance on remote app and remote desktop session is fine, so theres no bandwidth issues from where Im connecting from.
If it helps, the clients experiencing issues are all Windows 10, fully patched and latest W10 build. However there are many other devices also W10 same build, same patch level that are fine.
Has anyone experienced this before with Remoteapp's? Any suggestions?
Hi All,
My RDS Farm setup is setup as follows...All servers are Windows Server 2019 STD.
Office Subnet...
DMZ Subnet...
The "legacy" RDWeb portal works a treat, everything connects and my users can work 100%.
Yesterday I decided to install the new HTML Client. I successfully installed version 1.0.21.0
I can successfully connect to the RDSSH01 & RDSH02 resources but not the RDSSH03 resource. I get a certificate error...
The Connection Broker certificate is trusted and successfully imported, RDSH01 launches a full RDS desktop 100%, RDSH02 launches it's RemoteApps 100%, but RDSH03 persists on giving me this error!?
What have I tried?
The certificate in the error is not the connection broker certificate, it is the local self signed "Remote Desktop" certificate on the RDSH03 session host server underCert:\LocalMachine\My\Remote Desktop certificate store.
Additionally and this may be a bug - the cert is NOT an SHA1 certificate it is SHA2.
Any ideas how I can fix this as the neatly web page packaged RDS resources in the HTML client are exactly what my users are wanting...nice neat single pane of glass overview of ALL their RDS resources.
Hello,
for example I have two session hosts and one connection brokers with gateway role.
I want set primary session host for custom users group.
How I can do that?
Or can I do that at all?
Yes I can do new collection and Set-RDPersonalSessionDesktopAssignment but I have two session host and I want set priority for custom users not for all of them. Like LoadBalancing, but for some special group.
Thank you.
Pretty much self explanatory title....
After setting the high dpi compatibility thing (set to "Application"), a program (Namely Toad 13.3) is no more blurry on Windows 10 (1909, also through RDP) but stays blurry on Windows 2019 RDSH.
Any hint ?
Hello All,
I need a solution on below:
Is it possible to run Remote Desktop Session Services from a Single VM in Azure and Use Azure AD services instead of provisioning of separate VM as a domain Controller and DNS server.
This has a reference to run Tally ERP(Single User) application from a Azure VM and accessed from multiple user PC. Also to keep in mind that the client will need to buy additional additional RD CAL licenses for multiple remote sessions from their PCs.
As we need to provide cost effective solutions to as many as new probable clients to work from home in these COVD19 situations. So we will have to go with single VM solution to run the application only.
Thanks and Bye
Ranjit S
Hi,
As per my requirement i wanted to remove completely the 'Settings' and 'Windows Security' icon from start menu in windows 10.
It would be great if anyone helps me out.
Thanks,
Mike
Hi,
I am using RDGateway Pluggable Authorization for multi factor authentication using below sample-
https://github.com/microsoftarchive/msdn-code-gallery-community-m-r/tree/master/Remote%20Desktop%20Gateway%20Pluggable%20Authentication%20and%20Authorization%20Sample
Everything works fine. But the local drives of client machine are not available in RDP machine when used pluggable RDGateway Authorization.
Done all the configuration necessary to allow local drive to be shared.
1. In Rdp file ->Local Devices and Resources.
2. Allow all device redirection in Connection Authorization policy.
While with native RDGAuthorization, it's working fine. I can access the Local Drive of client machine in RDP machine.
Can anyone please help, what am I doing wrong?
Hi. We have a new WS2016 RDS deployment (VMs on Hyper-V):
- 2x WS2016 RDGW in NLB
- 2x RDCB in HA configuration
- couple RDSH servers
The problem is that in 30-50% of the connection attempts via these gateways, the connection is stuck at the "Configuring remote session" message. The connection is never successfully estabilished when this happens and it is closed without any error couple minutes later. When you try again (or just immediatelly cancel the connection and reconnect), the connection may or may not go through.
When this problem happens, I can see there's single HTTP connection on the RDGW that accepted the connection with 0 bytes transferred in either direction. There are no related errors at this time.
Can anyone help? Btw. this problem also happens when connecting to a different single-host RDS deployment through these gateways.
I suspected the problem might be in the NLB, but removing either of the gateways from the NLB configuration (and from RDS farm) doesn't help, the issue is still there.
Rebooting the gateways helps for a short while (hours), but then the issue is back.
There are some other errors on the gateways, but these don't correlate to the connection attempts (event 210, source terminalservices-gateway: "Http transport: IN channel could not find a corresponding OUT channel" with no other details).
RDP clients are various ... W8.1, W10, Mac...
error 0x207
Hello,
I’m using Windows Server Standard 2019 1809 with Remote Desktop Services deployed and for about a week all users can’t connect to server. I found out in Event Viewer (Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational), that problem is caused by Remote FX, so I’ve tried to disable it. Unfortunately disabling Remote FX in registry and group policy doesn’t make any changes.
What should I do, to resolve this problem?
i have a very functional RDS environment. 1 vm running gateway, broker, and licence. Two vm's running session host servers. Both the session host servers have NVIDIA Tesla cards directly attached. I'm trying to shadow the users by right clicking on the connections from server manger. It displays the RDS client like it's going to connect but it never does. It does prompt the user if i request it. If i try it again right away it prompts an error that a shadow session has already begun.
I've edited the local group policy of the session host server to allow shadowing, and I've check the user permissions in AD to allow remote control.
IT guy
Hello colleagues
When we are doing such config (enable multiple sessions per user):
Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Connections
Restrict Remote Desktop Services users to a single Remote Desktop Services session Disabled
We are not able to reconnect to any disconnected session that was running previously.
It seems that it was mentioned here for Inside build, but we have same...
Any solutions for this problem?
Regards,
Greetings,
I'm looking to migrate an old RDS infrastructure to a more modern one. For this project we would like to dissociate notebook clients from the Internal AD and use Azure AD for them. I'm running in an issue with what seems to be the credential delegation part of the RDP connection. I am being prompted the user password when launching the application. If I type in type password the application launch just fine.
I have followed these guidelines and defined "TERMSRV/*" in my delegation policy for diag purpose:
https://docs.microsoft.com/en-us/archive/blogs/mrsnrub/remote-desktop-services-websso
My AAD Joined Windows 10 session is able to access protected Shares from my local AD without having to do anything.
The same RDS setup accessed with an AD Joined Win10 (same version, image from Azure) works properly, the credential delegation works on this setup, the password is not being requested. I have also forced the use of the RDS Gateway so that the AD client would use the same path as the AAD one.
This threads hints that it should have worked. Note that I'm not looking for the full SSO experience, just not having to enter the password when launching different applications.
https://social.technet.microsoft.com/Forums/en-US/710eca14-e2f3-45e4-a6c8-734915f83b7b/rdweb-sso-experience-with-azure-ad-join-clients?forum=winserverTSI'm basically looking for pointers on where to look at, is there any traces that can be enabled that would give a reason to why the credential are not being pushed. Am I trying to do something that should not work?
Thanks for your input,
Dominic