ChromeOS devices not showing up in Hexnode after enrolmentSolved

Hi, thanks for reaching out to Hexnode Connect.

This issue has recently surfaced for a few admins due to changes in Google Workspace integration.

Google has added a few new authorization scopes that need to be configured when integrating Workspace with Hexnode, especially if you want to sync ChromeOS devices. You might want to revisit the integration setup to ensure the latest scopes are added.

https://www.hexnode.com/mobile-device-management/help/how-to-integrate-g-suite-with-hexnode

Once that’s done, all your ChromeOS devices listed under Google Workspace should sync automatically with Hexnode.

Best regards,
George
Hexnode UEM

Got it, thanks. I guess our team missed out on checking out the changes in the workspace integration doc. After updating those, I can see some progress, but a few devices still aren’t enrolling. Any idea what this could be related to?

Hello again,

ChromeOS devices require a Chrome Enterprise license to be managed through Workspace and UEM platforms like Hexnode. Each device you want to manage must have one enterprise license assigned.

In addition, Hexnode also manages licensing on a per-device basis, so you’ll need to ensure you have enough Hexnode device licenses available as well.

To ensure new ChromeOS devices sync seamlessly with Hexnode, verify that each device has a Google enterprise license assigned in the Admin Console and that you have sufficient device slots available in your Hexnode portal.

Once both are aligned, new devices should sync seamlessly into Hexnode.

Best regards,
George
Hexnode UEM

That clears things up, thanks. I guess we have to have a keen eye on the prerequisites. I’ve now got the devices enrolled and synced. One more thing though, I was testing out ChromeOS Kiosk policies via Hexnode, but they don’t seem to take effect on the devices. Did we miss something again?

Hello,

We understand your problem with kiosk policies not being effective on ChromeOS devices. ChromeOS Kiosk Mode requires a separate Kiosk license in addition to the standard enterprise license. Even if your devices already have enterprise licenses, the kiosk configuration won’t apply unless you’ve purchased and assigned the Kiosk license type for those specific devices.

Once the proper license is assigned through Google Workspace, Hexnode’s Kiosk policies will apply as expected.

Once your licensing is set up correctly, Hexnode’s ChromeOS management should work smoothly across both enterprise and kiosk deployments.

You can always check out our documentation for detailed guidance on ChromeOS setup and integration if needed.

• https://www.hexnode.com/mobile-device-management/help/how-to-integrate-g-suite-with-hexnode
• https://www.hexnode.com/mobile-device-management/help/enroll-chromeos-devices-in-hexnode-uem/
• https://www.hexnode.com/mobile-device-management/help/single-app-kiosk-mode-chromeos/
• https://www.hexnode.com/mobile-device-management/help/multi-app-kiosk-mode-chromeos/
• https://www.hexnode.com/mobile-device-management/help/kiosk-settings-on-chromeos/

I hope this resolves your issue. Please feel free to contact us if you need any further assistance; we’re happy to help.

Best regards,
George
Hexnode UEM

Ah, that explains it perfectly. I was testing kiosk mode with regular enterprise licenses. I’ll get the proper ones assigned. Appreciate the detailed explanation, George, that helped a lot!