New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 832314 link

Starred by 9 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature



Sign in to add a comment

Unattended Chrome Remote Desktop for Enterprise Enrolled Chrome OS Devices in Kiosk/Logged in User Modes

Project Member Reported by c...@chromium.org, Apr 12 2018

Issue description

Description:
Feature Request to provide complete remote desktop (live video feed, remote mouse, and remote keyboard inputs) for enterprise enrolled single-app kiosks and logged in user mode.

Use case:

Interactive Kiosks -- Customer wants full remote capability to view and provide support to enterprise enrolled Chrome devices.

Signage -- For displays that are thousands of miles away or high in the sky 100+ ft, ability to remote view video feed and provide remote key inputs e.g. mouse/keyboard for troubleshooting.

Logged-in User Mode -- Customers want full remote control of a users session to provide tiered support.  

Motivation:
Current/existing solutions have built-in remote desktop capabilities.  Customers have suggested that devices they enroll, manage, and deploy are under their own supervision and custody.  They should have the right to enabling/disabling full remote desktop capability which does NOT require any USER acknowledgement or interaction.

Existing workarounds:
Chrome Remote Desktop:  https://support.google.com/chromebook/answer/1649523?hl=en

What isn't working:

-Inability to start remote sessions automatically, requires user to generate access code
-No Remote Desktop capabilities for Single App Kiosk Mode
-Remote Screen Capture is limited especially for scenarios whereby issues occur during video playback, remote screen capture is unable to fully capture/replicate the issue.
 
Cc: denizz@chromium.org
Discussing these requirements and broader CRD plans / strategy for Enterprise with the PM and Eng lead for CRD. Will update this thread further once we have more clarity on roadmap and resourcing.
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Cc: msnoxell@chromium.org
Owner: aghuie@chromium.org

Sign in to add a comment