You can launch Chrome Remote Desktop directly from ControlUp to remotely control your ChromeOS devices. This feature lets your help desk provide seamless support to ChromeOS users without switching tools.
Note that because this feature uses ChromeOS Remote Desktop instead of ControlUp’s native Remote Control solution, the features described in our Remote Control and Shadow article don't apply.
Prerequisites
ChromeOS devices must have the browser extension installed and be connected to your ControlUp environment.
You must have set up the Google Cloud connector.
Your Google Workspace account (not a service account) must have Chrome Remote Desktop enabled.
Your Google Workspace account (not a service account) must have permission to grant ControlUp the following access to your Google environment:
View and manage your ChromeOS devices' metadata (
https://www.googleapis.com/auth/admin.directory.device.chromeos)See info about users on your domain (
https://www.googleapis.com/auth/admin.directory.user.readonly)
Only shared sessions are supported.
Your ControlUp account must have the permission Allow Remote Control.
How to start a Remote Control session
Go to a ChromeOS device in app.controlup.com and select the Remote Control action.
In the prompt, sign in with your Google account and grant ControlUp access to your Google environment. This authentication is necessary to get the Chrome Remote Desktop URL for your Google environment.
When the ChromeOS remote desktop interface opens, sign in again to authenticate to Chrome Remote Desktop. You can now remotely control the device.
Note
You must use the same Google account for both sign-ins (step 2 and 3 above).
Reauthenticating with your Google account
When you sign in to your Google account and start Chrome Remote Desktop, your credentials are remembered so that you don't have to reauthenticate to start another remote session.
You have to reauthenticate to your Google account in either of the following situations:
Your Google account login has expired due to the reauthentication policy configured in the Google Admin Console. For example, if your accounts are configured to require reauthentication after 1 hour, then you must sign in to your Google account to start Chrome Remote Desktop if you haven't signed in within the last hour.
More than 24 has passed since you granted ControlUp access to your Google environment (step 2 in the procedure above). This access must be granted every 24 hours.
Troubleshooting
If you sign in to your Google account to start Chrome Remote Desktop and then switch Google accounts in your browser, you receive an error when you try to start Chrome Remote Desktop again. To fix this issue, make sure you are signed into the Google account you used to start the first session.
When you sign in to your Google account to start Chrome Remote Desktop, your Google account is tied to your ControlUp account for 24 hours. If you want to use that Google account for Chrome Remote Desktop on another ControlUp account, you must wait 24 hours.