5

Awesome. I had one client with issues and couldn't figure out the solution. Tried AV, updates, etc. create a DWORD-32 key RDGClientTransport with value 1 at HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client Finally resolved the issue.


4

If you use Network Level Authentication in conjunction with RDP (which you should because it's the more secure option,) then you cannot connect if your password is expired. This means that you cannot connect in order to change your password because you cannot connect with an expired password. This is considered by design because there is no such feature in ...


2

After reading much documentation found out what I had done wrong. I had broken everything by manually adding the new Cert to IIS myself on the RDWeb server. No idea why this broke everything. The correct method apparently is to just add the Certificate to the Deployment Configuration via Server Manager (to each of RDWeb, Gateway, Broker etc) and this auto-...


1

I found the place where I made the mistake in Server Manager/Remote Desktop Services/Overview/Tasks Edit Deployment. The outside FQDN goes in the Server Name field.


1

RDP is pretty lighweigh, I recommand other thing for your router as it hit 100% CPU time. Rdp User found it drop, but Iam sure it affect you on other services Following our comment I would suggest; Try to save on CPU cycle for your appliance. Normal port forward is not usally something that will put a high load on your appliance, as such please check ...


1

It turns out the certificate wasn't fully installed. The RDPublishedName is set to remote.mydomain.com and I exported the certificate from IIS and made sure it was installed on the RD Broker/Licenser/Gateway. All is working fine now.


1

All processing (including that of the graphics card) is done on the host computer. The power from the client computer doesn't matter as long as it has strength enough to run an RDP program. That said, RDP strips down graphics to permit a fast response over the network. Depending on what kind of software you want to run remotely it could be useful to have ...


1

Sure. Everything, including this kind of monitoring, is possible for almighty sysadmins, but: It would be unethical. Work computers can be used both for personal and professionally confidential tasks. Monitoring such could be illegal. We have actual work to do. No time for spying employees. We don't have any interest in what kind of porn turns users on, as ...


1

Posting this just in case anyone runs into this issue with a terminal services setup in AWS behind an Elastic Load Balancer. Our resolution was to disable SSL termination on the ELB, so instead of having HTTPS -> HTTPS on the load balancer, we set it up to TCP -> TCP on 443. That way it is doing SSL offloading instead of SSL termination. We also setup SSL ...


1

Even though I still have a mismatch between public and private hostnames, I got RemoteApp working again via instructions here: http://www.concurrency.com/blog/w/remote-desktop-can%E2%80%99t-find-the-computer-through-rdw


Only top voted, non community-wiki answers of a minimum length are eligible