Remote desktop application is unrelated to WCF, because it uses its own protocol, RDP:
http://en.wikipedia.org/wiki/Remote_Desktop_Protocol[
^],
http://en.wikipedia.org/wiki/Remote_Desktop_Services[
^].
You can find good samples of the client on CodeProject:
Remote Desktop using C#.NET[
^],
Palantir - Remote Desktop Manager[
^] (this one, being not perfectly complete, is my favorite: in the past, when Microsoft client failed to cope with some situation, this product saved me).
Of course, you need to go this way only if you want to use available Remote Desktop service on remote computers. This makes a whole lot of sense, because the service, in contrast to client application, may seriously depend on the version of the OS. Nevertheless, if you really decidedly want to work with WCF, chances are, you would need to develop your own, alternative service. If you decide to do so, it could be the
Windows Service:
http://en.wikipedia.org/wiki/Windows_service[
^],
http://msdn.microsoft.com/en-us/library/zt39148a.aspx[
^].
In this approach, the problem will be the access to a desktop local to the service. As to WCF, you can use it as self-hosted by the Windows Service application:
http://msdn.microsoft.com/en-us/library/ee939340.aspx[
^].
I would strongly recommend you not to go in this difficult way, where the future of your product hardly can be secure. I would advise to keep to RDP and client part of the software.
—SA