Recursos para Profesionales de TI >
Página principal de foros
>
Live Mesh
>
Live Remote Desktop vs Built-in RDP
Live Remote Desktop vs Built-in RDP
- Aside from tunneling over HTTPS, what are the functional differences between using Live Mesh Remote Desktop over Vista Business/Enterprise/Ultimate's built-in RDP?
With the built-in RDP and multi-user switching, any user can login to their desktop even if they weren't already logged in. Does Live Mesh RDP work the same way? Does the user have to be logged in? What if there are mutliple logged in users?
If there are multiple logged in users and someone tries to connect remotely via Mesh, will it prompt the person at the console that someone else is trying to connect (The way built-in RDP does)?
What about drive/printer/audio redirection?
I'm just looking to see what the benefits are if port-issues are not a problem (3389 working just fine, using dyndns, etc).
Thanks!
----
Update:
Upon some further investigation, RDP seems more secure than Live Remote Desktop - here's why: with RDP, the full window session gets redirected to the RDP output device and the desktop can't see it. With Live Remote Desktop, you see a copy of what the desktop session sees -- meaning that you have to both remember to "blank out" the screen as well as having the potential to connect to another user's session. RDP doesn't have that problem.
I really do like the idea of Live Remote Desktop, but I dislike the implementation. It seems that Terminal Server Gateway accomplishes part of the problem (tunneling over HTTPS) while maintining full session isolation. I think it'd be better if Mesh's Remote Desktop were based on a slimmed down version of TS Gateway and used the existing RDP features of the platform (if available). Mesh could facilitate the connection establishment the same way as it does now, by creating the outbound connection to the cloud. Keep doing that, but have the session based on TS Gateway and RDP...
Thanks again and I look forward to more insight / discussion on this.
Regards,
Oren- EditadoOren Novotny domingo, 01 de junio de 2008 20:11updated
- Tipo cambiadoBen [Live Mesh] lunes, 09 de junio de 2008 19:45Open Community Discussion
Todas las respuestas
- One other difference that you'll note. With Live Mesh remote desktop, you get a a scaled desktop by default. It doesn't change the remote desktop's screen resolution.
Another one that I love is that I have access to be able to put a remote PC to sleep or shut it down. With RDP, I can't put it to sleep and need to invoke taskmgr to shut the PC down.
-steve
Microsoft MVP Windows Live / Windows Live OneCare Forum Moderator - yes i agree with Steve totally! having those abilities is nice but yes on the other hand Oren is hitting a vital issue i also see in this... we need to bump up security!!
- While I am not sure you can put a computer into sleep mode, you can use SHUTDOWN to reboot or power down a computer without using task manager. That's what I use when I am RDPing into a computer.
- Isn't part of the issue that a lot of organizations firewalls will block the RDP ports? This will greatly reduce the chances of successfully using remoting over WAN. Maybe if the software first tried to make a connection via RDP then after timeout it went to HTTPS. This would give best of both worlds. I also notice that if I am connecting to a machine on my LAN via mesh desktop sharing it seems that the traffic goes out over the internet then comes back rather than negotiating a LAN connection. Maybe this is impossible for the cloud to know but it would be easy enough for the mesh services on the local machines to use something to see each other like Windows Rally or Apple's Bonjour, etc. Then the best connections could get negotiated for syncing.
- Hi all,
Great thread! I wanted to comment on a few things in regards to the above, be open about how Live Mesh Remote Desktop works, and why we designed it the way we did.
1) "Blacking out the screen"
We are working on turning this feature on by default. Our XP implementation has a few “bugs” that could render a machine unusable in rare corner cases. Thus, we don’t turn it on by default for the tech preview. We are actively working on this for a future release.
2) Using OS based RDP
We wanted to make the functionality available to all of our clients, so we couldn't rely on the OS RDP client/server. JerseyJ also makes another good point that RDP ports are blocked by default, so we needed a mechanism to traverse firewalls.
To answer a couple other questions:
"With the built-in RDP and multi-user switching, any user can login to their desktop even if they weren't already logged in. Does Live Mesh RDP work the same way? Does the user have to be logged in? What if there are mutliple logged in users? "
[tmanion] With the Live Mesh Remote Desktop enhancements installed, yes, you can log into any account on the machine, if you know the password.
If there are multiple logged in users and someone tries to connect remotely via Mesh, will it prompt the person at the console that someone else is trying to connect (The way built-in RDP does)?
[tmanion] Yep, we have connection arbitration.
What about drive/printer/audio redirection?
[tmanion] Great features. We are looking at those for a future release.
I hope this helps. Thanks for trying out Live Mesh!
Todd
This posting is provided "AS IS" with no warranties, and confers no rights. - Thanks for the additional information and insight, Todd. As I noted, the initial implementation is already serving a purpose for me with the Sleep capability. I can leave a PC on, connect to it later via Live Mesh Remote, then put it to sleep when I'm done. Of course, being able to wake it up again remotely would then be way cool.
-steve
Microsoft MVP Windows Live / Windows Live OneCare Forum Moderator - Notinkeys said:
While I am not sure you can put a computer into sleep mode, you can use SHUTDOWN to reboot or power down a computer without using task manager. That's what I use when I am RDPing into a computer.
That works, too. It was easy for me to remember how to invoke task manager remotely and select shut down or reboot as needed.
-steve
Microsoft MVP Windows Live / Windows Live OneCare Forum Moderator
