Using a remote presentation (via ID/Claim ID) ?

  • 1
  • Question
  • Updated 2 years ago
  • Answered
  • (Edited)
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members.


I have been given a Chrome Box and monitor to use Rise Vision on. To show an global/external presentation.

I have also been given an ID code, which should link to a presentation?  But how do I get this presentation to show on my monitor?

Where should this ID code actually go?  

In the "Add Display"?  or the "Display ID" " or Claim ID" ?  

Really having trouble setting this up, and I have followed a few links but sadly they have all been dead links.

Any help, information, tips, guides, would be greatly appreciated. Thanks in advance!
Photo of Tom


  • 70 Points

Posted 2 years ago

  • 1
Photo of Darius -

Darius -, Champion

  • 26,850 Points 20k badge 2x thumb
Tom, Chrome OS is not supported by Rise Vision anymore. Giving that you can find and install the Rise Vision Player App (I am not sure if it still is available through the Chrome App Store), you also gonna need to set your player to Kiosk mode (if you want RV to start at your players bootup). On the very first Rise Vision App run it is gonna ask you to enter Displays ID number.
Photo of Darius -

Darius -, Champion

  • 26,850 Points 20k badge 2x thumb
Here is some info from my old notes to help you out:

Chrome OS Optimization Guide

We support Rise Player on Chrome OS that is running the latest version of Chrome on the Stable Channel.

Configure Single App Kiosk Mode for Unmanaged Devices

Before configuring your device for Kiosk Mode, you’ll need to recover your Chromebox to it’s default factory settings. See the instructions located at Google’s help page, under the section “Wipe a Chromebox”.

  1. At the login screen press Control+Alt+K on your keyboard
  2. An Automatic Kiosk Mode windows will appear, select Enable
  3. Log in to your Chrome OS device
  4. Open Chrome and navigate to chrome://extensions
  5. Select the Developer mode checkbox
  6. Select Manage kiosk applications
  7. In Add kiosk application field, enter the Application ID mfpgpdablffhbfofnhlpgmokokbahooi
  8. Click Add
  9. Highlight the Kiosk App and select auto launch
  10. Select Done and restart
  11. After restart, select Confirm to accept the Auto-launch permission

Configure Single App Kiosk Mode for Managed Devices

For Managed Devices, we recommend creating an Organizational Unit for your Digital Signage Players with the settings configured per the steps below. Settings not shown can be left as default.

1.    Set Power Management to Do not allow device to sleep/shut down when on sign in screen

2.    Set Sign-in Screen to Never show user names and photos

3.    Configure Kiosk Apps by adding the Rise Player Application

o    Click Manage Kiosk Applications

o    Select Chrome Web Store

o    Search for Rise Player

4.    Configure Kiosk Settings for the following

o    Set Public Session Kiosk for Do not allow Public Session Kiosk

o    Configure Rise Player as the Auto-Launch Kiosk App

5.    Set Auto Update to Allow auto-updates

6.    Set Restrict Google Chrome version to at most to one or two versions behind the current version

7.    Set Randomly scatter auto-updates over to None

8.    Set Auto reboot after updates to Disallow auto-reboots

9.    Set Release Channel to Move to Stable Channel

Enroll Your Chromebox

1.    Power on your Chromebox

2.    Follow the on-screen instructions to connect to a wireless network

3.    At the login screen press Control+Alt+E on your keyboard

o    NOTE: If an enrollment prompt does not appear, please wipe your Chromebox

4.    Type in the enrollment email and password associated with your Google account

Select Enroll device
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb

The only thing wrong with your steps above is the Application ID. It should be  ilcmohdkjfcfekfmpdppgoaaemgdmhaa which is listed on this page:

As Darius states, ChromeOS is no longer a supported OS, but the steps above should get you up and running.

I hope that helps Tom!