Surface Hub managed by Intune & Licensing via EMS
We have a few Surface Hubs in our organization which I'd like to add to intune. Obviously these devices should not be associated with a specific user, so I started looking into the Device Enrollment Manager (DEM) feature as a way to join the devices w/o tying them to a user. Reading the doc on DEM (https://docs.microsoft.com/en-us/intune-classic/deploy-use/enroll-corporate-owned-devices-with-the-device-enrollment-manager-in-microsoft-intune) leaves me with the impression that each device enrolled using a DEM requires it's own intune license. We get intune as part of EMS, which is licensed per user, not per device. Do we need to buy additional per-device intune licenses for each surface hub? Or, am I on the wrong track altogether? Is there a better way to enroll the Hubs in intune w/o a user association?Surface Hub not updating in Microsoft Intune
I've also x-post this to the Surface Hub community too here, but thought I'd also post here. Is anyone using Microsoft Intune to manage their Surface Hubs, and have any of you had any issues since the February 2018 CU was deployed (15063.909)? I enrolled my test Surface Hub while it was on the January CU (15063.850) and it was working fine. Configurations were being delivered and hardware inventory was being polled and retrieved from the device. Then the February CU came out and was installed. Now my test Surface Hub isn't updating anything. I've installed the March CU that came out yesterday (15063.936) and it's still not sending anything new back or installing new/changed configurations. However, the Surface Hub says that it's checked in fine, and Intune is updating the last check-in time correctly. The first batch of Surface Hubs that I since enrolled (15 of the 35 we have) are all showing the same signs too (mixture of Feb and March CU installed): Hardware inventory not being retrieved Application inventory not being retrieved Configurations not being deployed Compliance not being evaluated I have an open case with Premier Support and we're looking into it, but I was wondering if anyone else has seen this behaviour since the Feb CU came out?
