Chrome Remote Desktop goes mobile
chrome.blogspot.com
chrome.blogspot.com
I did notice that the resolution was downgraded on the MBP and I had to manually restore it to the best setting via System Preferences after the connection. Other than that, it worked fine.
1. Install Chrome extension
2. Open the "App" in Chrome and enable remote desktop on computer and set pin
3. Install Android app, open it, then choose desktop from list and connect
[1] https://play.google.com/store/apps/details?id=com.microsoft....
[2] https://play.google.com/store/apps/details?id=com.citrix.Rec...
Plus, the machine I'm remoting talks up to Google, so I don't have to configure any firewall rules to allow incoming connections.
Plus it was authored by Google, so I trust it significantly more.
Already works for Remote Assistance for Windows, Mac, and Linux. And I have expectations it will work for remote control for all those platforms, soon, too.
Oh, and I can have the Chrome Remote Desktop client on any PC that has Chrome. I've found that several of the "remote desktop apps available for Android" ONLY have an Android client.
But for Windows, I use the built in remote desktop feature/server and the client is pre-installed on every Windows machine. I'm at work remoting into my home machine right now. But I can also use any number of different Linux, Android, or iOS clients to connect to it. It does require two seconds to setup port forwarding and I use a dynamic DNS service.
The performance of an RDP-based solution is going to be much better than this. But if you're remoting into OS X or Linux then there is no advantage.
It is unfortunate that close to no attention is paid to this element.
Maybe that's gotten better over time, but it used to suck bad.
more convenient, maybe. but more secure? give me a break.
https://code.google.com/p/chromium/wiki/ChromotingBuildInstr...
And I'm arguing with someone who prefers Microsoft Remote Desktop.
You're right that I'm using a 3rd Party to establish my connection, so there is that.
One gotcha to watch out for is that your unattended desktop has to actually be awake and running. If it goes into power saving mode you can't access it. It also seems to take CRD a long time (often hours) to realise that a sleeping system is no longer sleeping.
This makes me wonder how much more work Linux desktop support would have been?
It mainly seems to me that Google really just doesn't care about the Linux desktop even though reports are half the employees using Goobuntu. Another example is Google Drive not being available for Linux.
Of course then Dropbox mess up the multi-account thing badly even with the recent changes.
AFAIK the app contains binary code for each supported platform, so it's really more like Chrome-as-app-store than anything else.
Well, unless you consider your computer Google-owned, this is using a third-party (Google) app and handing over to them credentials to your machine.
However, trusting a third party for connection initiation is the only option unless one has a computer that's globally addressable and accessible from the Internet.
Still, as (IIRC) Chrome Remote Desktop does not provide end-to-end authentication (i.e. peers don't visibly - in a manner acknowledgeable by the end-user - authenticate that they're genuinely securely communicating to each other without third party inbetween), so it's probably less secure, if compared to a VPN-to-home service.
Is there something else to this? That page is pretty sparse on details.
The Chrome extension for viewing lets you invite someone to access your desktop. The viewers and desktops can be any combination of Linux, Windows or Mac.
Unlike skype, viewers can interact with the desktop.