remoteapp the remote computer could not be found

Granted, current versions of the Remote Desktop Client combined with TLS makes those types of attacks much more difficult, but there are still risks to be wary of. And given that, often customers are typing in domain admin credentials…which means you could have just given an attacker using a Man-in-the-Middle (MTM) attack the keys to the kingdom. Sure, it can be perceived as a hassle sometimes, but dog gone it…don’t just click through it without reading what it’s trying to tell you in the first place! Why not you ask? Well for one thing, using sniffing tools attackers can successfully extrapolate every single key stroke you type in to an RDP session, including login credentials.

Microsoft wants you to be warned if there’s a potential risk of a compromise.

Let’s be clear on one thing: The warning messages / pop-ups that end users see connecting via RDP are a GOOD THING. However, to enable a solution where the user can connect to the apps or desktops that you have published for them from ANY device and from ANYWHERE, then you eventually need to deploy certificates. This is the underlying authentication that takes place on a domain without the requirement of certificates. The Kerberos authentication protocol provides a mechanism for authentication - and mutual authentication - between a client and a server, or between one server and another server. Kerberos plays a huge role in server authentication so feel free to take advantage of it. Unless there are security requirements that they must meet, most organizations don’t deploy certificates for systems where they are simply enabling RDP to allow remote connections for administration, or to a client OS like Windows 10. I’m also going to assume that whoever is reading this knows a bit of PKI terminology. To get started, I’m going to break this topic up into several parts. HA! If only it was that easy! You people reading this right now wouldn’t be here if it were that easy, right? There’s also a lot of misguiding information out there on the internet… Being a PKI guy myself, I thought I’d chime in a bit to help the community. If you’ve come across this in your environment, don’t fret…as it’s a good security practice to have secure RDP sessions.

I am writing this blog post to shed some light on the question of “How come we keep getting prompted warning messages about certificates when we connect to machines via RDP?” A couple of examples you might see when running the Remote Desktop Connection Client (mstsc.exe)… Quick shout out to my buds SR PFE Don Geddes (RDGURU), and PFE Jacob Lavender who provided some additional insight on this article! Here in the fall, in the Ozark Mountains area the colors of the trees are just amazing! But hey, I’m sure wherever you are it’s nice there too. Hello everyone! Tim Beasley, Platforms PFE here again from the gorgeous state of Missouri. First published on TechNet on Dec 18, 2017

Remoteapp the remote computer could not be found