Mar 10 2018 02:10 AM - edited Mar 10 2018 02:13 AM
I've also x-post this to the Intune 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):
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?
Mar 27 2018 01:10 AM
Yes I'm definitely seeing something similar on the hubs I've enrolled in intunes.
They are getting quality updates but not feature updates.
How do you see the extended version of the Surface Hub? build 15063.xxxx
Mar 27 2018 03:04 AM
Hi Mik
Attached is just a small snip of the 35+ Surface Hubs we have enrolled with Intune. As you can see, some aren't reporting anything, some are incorrectly reporting compliance status, and one is still showing it's on the January CU (15063.909) rather than the March CU (15063.966) when I know it has it installed. Also, as you can see, they've all checked in within the last 10 hours.
I'm now seeing most of them receiving a Default Device Compliance Policy which I haven't created/set, suggesting something is up with these in Intune in a big way right now...
D
Apr 26 2018 02:48 AM
@Daniel HudsonDo you have an update on this issue with Microsoft Support?
Looks like we are experiencingthe same issue.
Looking forward to hear from you.
Apr 27 2018 01:11 PM
SolutionApr 27 2018 01:11 PM
Solution