Display ID not found on multiple endpoints

  • 1
  • Problem
  • Updated 4 years ago
  • Solved
This morning (1/29/15) we found that 14 of our 15 displays (ChromeOS 38.0.2125.119 and RisePlayerPackagedApp 1.24.25) had lost their Display IDs.  I don't see how this could be due to anything we did on our end, so I'm curious to know if this is system wide, specific to a Chrome platform update, player update, etc.  Any suggestions on how to reduce the chance of this happening again would also be appreciated as our displays are geographically dispersed.  I assume on the Chrome platform, the only way to rectify is to manually re-enter the ID on each display.  These units are managed (Google Apps) and in kiosk mode.  If there's a way re-associate remotely, I'd also love to hear about that.
Photo of Larry Askew

Larry Askew

  • 182 Points 100 badge 2x thumb

Posted 4 years ago

  • 1
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Larry,

We haven't seen this locally on any of our uptime displays, and haven't heard any reports of this from other users. It's a very odd circumstance and hard to come to a conclusion on. Could your device management account have had something changed?

The only way to re-associate display IDs is by directly connecting a mouse and keyboard to the chromebox and manually typing the ID.
Photo of Larry Askew

Larry Askew

  • 182 Points 100 badge 2x thumb
Knowing it wasn't widespread, that's where we'll focus.  Thanks for the prompt response.