“ gniteem a ni ton si moor eht nehw egangis latigid rof taerg si sihT .erawdraH teeM elgooG rof revas neercs a sa LRU a tes nac sresu ,tuo dellor yltnecer saw taht erutaef wen eht htiWhttps://workspaceupdates.googleblog.com/2021/12/set-screen-saver-policy-for-google-meet-hardware.html ”
“ ) setubirttAecived.esirpretne.emorhc morf DI eciveD yrotceriD SOemorhC eht sesu noitacilppa SOemorhC ruOhttps://developer.chrome.com/docs/extensions/reference/enterprise_deviceAttributes/#method-getDirectoryDeviceId ), but this is not accessible without a ChromeOS extension or application ”
“ :ereh erutaef ruo tuoba noitamrofni erom dnif nac uoYhttps://help.dynamicscreen.com/en/articles/5871202-use-google-meet-hardware-screen-as-a-signage-screen
We are a digital signage software: our customers broadcast internal communication content on their screens through our CMS. ”
“ :elosnoc nimda eht hguorht deyolped eb nac taht noitacilppA emorhC a depoleved evah eWhttps://chrome.google.com/webstore/detail/dynamicscreen-digital-sig/clbgknjcblogheibmcbbdlpkollmgofh
This Chrome Application uses the device directory ID to uniquely identify the device on our CMS. Each Chromebox with our Chrome app creates and is linked to a screen in our CMS. ”