We use Google Workspace at work and Chrome. For remote support, we use Chrome Remote Desktop. It’s fine when it works, but half of the computers that I’ve authenticated and configured for remote connection go offline and don’t come back up until I re-authenticate them through the Chrome Remote Desktop interface. I use the option to set up via SSH and typically can reconnect them by authorizing them as a new computer by connecting to the local computers using Powershell and running the connection script. I usually add to the name field and then add the -pin option so I don’t have to set this up in the command line (Powershell).
I.E. & "${Env:PROGRAMFILES(X86)}\Google\Chrome Remote Desktop\CurrentVersion\remoting_start_host.exe" --code="4/0Ab_nOt_ThE_aCtUal_cOdE_u08o7AAjRnyXikFuKKPzeO6515JasfYS2BK74VWyI_trzGnA" --redirect-url="https://remotedesktop.google.com/_/oauthredirect" --name=$Env:COMPUTERNAME" (Username)" -pin=123456

The problem that I have is that they tend to fall off line after some time (days, weeks, etc.). It’s not a huge problem when they are local, but when they are at a remote site or at home, this becomes a pain as I can’t run Powershell. I either have to remote connect to their computer in some other way which often doesn’t have admin access. This defeats the purpose of using it for remote administration.

While writing this, I tested a device by connecting via Powershell that was reporting offline and ran start-service chromoting and it works great if local.

Is there a way to reconnect them without reauthorizing them when they are remote or just restarting the service? Powershell isn’t going to work unless it’s local.

2 Spice ups

I don’t have an answer to your question per-se, but what came to mind was using a RMM to give you 24/7 remote access to run scripts…but if you did that you might as well use the RMM’s RDP tool anyway. Action1 will give you RDP and scripting for 200 endpoints for free.

But I wanted to reply to your post because I’ve been considering using Chrome Remote Desktop for a handful of Chrome OS devices and was intrigued by your assertion that devices regularly, randomly fall offline permanently until you reauthenticate on-device somehow?

I found a device yesterday that had recently fallen offline when I was writing that post. I decided to try finding the service and restarting it and it worked. So for local devices, assuming a similar scenario, I can just restart the service. I don’t imagine that Chrome OS will have the same issue since they run a type of Linux and have different conditions regarding the service.

I’ll check out Action1. Thank you!

Especially for remote setups where you don’t have a secondary access path, that sounds like a huge pain. I didn’t realize the chromoting service could flake out like that either. Curious if it’s tied to system updates or login state changes?

I would also suggest looking into an RMM with great remote access software like Pulseway. The always-on agent makes it easy to restart services, run scripts, or just check in on systems, even if other tools lose their connection.

@joebridgeman That Action1 tool is nice… Real nice. I think that will do the trick and some. Thank you!

I didn’t start this thread to get or share ads, I just wanted to share my tips for modifying the name and adding the pin to the CRD Authorization script and see if anyone else had dealt with them falling offline. But yeah! :grin: