When Windows offers a built-in RDP client, why would anyone want to use anything else for desktop sharing and remote support? Windows Remote Desktop Connection (RDC) is easy to use, reliable, free, and already there. But there are several features the built-in client lacks that third-party clients provide. The following are just a few of the features not supported by the built-in RDP client.
Windows RDC is preemptive when you're connecting to desktop operating systems, which means an RDC session will disconnect, or preempt, any current local or remote session. A non-preemptive RDP client, on the other hand, prevents this. Once you are connected to a remote system with a non-preemptive client, no other sessions are allowed until the current one is finished.
Local and domain policies can limit what users can remotely access a computer, but they can't impose limitations beyond requiring the appropriate permissions. For example, what if you wanted to provide access to an executive's system only when they're logged on and only with their permission? With a third-party RDP client you can configure settings for scenarios like this, and some even support server-generated invitations for added control.
Windows RDC works great when all you have to do is connect to other Windows computers with RDP enabled, but what if you need to remotely control Linux or Mac systems? VNC viewers are great in this regard because they support all three platforms.
With Windows RDC, once you're connected, you're connected. That's it. But with other RDP clients, you can enjoy additional in-session features like live chat (do not read netsend ), screen capturing, smart sizing, and local keyboard/mouse restrictions.