Share Microsoft Whiteboard Missing on Surface Hub 2s

[lyndon_s87]

Hi all,

Bit of an annoying one here. We have deployed a whole lot of Surface Hub 2s devices which are running the Microsoft Teams Rooms for Surface Hub built-in app (Windows 10 Teams Edition with 20H2 update) and when in a Teams meeting, we click "Share Content" and we can share the entire screen or a window, but the option to share Microsoft Whiteboard is not there.

I have confirmed the Meeting Policy has allow whiteboard sharing, whiteboard is on globally for the tenant and is assigned to the Room Resource account (as logging into Teams account on the desktop app is fine).

Is there any settings on the Surface Hubs, InTune or Teams that would stop this? Or is it a feature that is missing in the Teams Rooms for Surface Hub app?

[#2]

It's true sharing MS whiteboard into a teams meeting is not available from Surface Hub. I believe it is a missing feature after the MTR update for Hubs

[#3]

@lyndon_s87 
I have also noticed this deploying several new SurfaceHubs. 
Previous deployments and testing early this year the whiteboard feature was showing in the share tray. You could live collaborate on a whiteboard with teams participants (in your org). It appears to seem like the whiteboard app isn't using the device account/is not signed into an account in the org and there for cannot use whiteboard in teams meetings.

[#4]

So, we have been talking with Microsoft Support around this and as it turns out, there is an issue with the Surface Hub device accounts and OneDrive for Business that they are in the process of fixing.

"A recent change intended to utilize OneDrive for Business as a storage resource for Microsoft Whiteboard exposed a code issue where a check is performed on Surface Hub devices to confirm accounts have a OneDrive for Business license. The check fails if resource accounts associated with the Surface Hub devices don’t have a OneDrive for Business license, which prevents users of the associated Surface Hub devices from starting a whiteboard."

[#5]

Thank you lyndon_s87 for the update. On a different note since you have deployed many hubs are you registering them to Intune using a DEM account or manually enrolling them one by one. Just wanted to understand your experience and lessons learned if you are doing the bulk enrollment

[#6]

So, we've been deploying them using a provisioning package we've created in Windows Configuration Designer (WCD). Essentially from there, we're using it to create the Provisioning Package file (.ppkg) that we load onto a USB and when we first power the new devices on, we insert the USB and it enrols the device in Intune (and in our case we also deploy root cert chains, and WiFi config too). After that point, we add the Room Resource/Device Account, give it the friendly name and device name.

This link below is handy to help with creating the package.

Create provisioning packages - Surface Hub | Microsoft Docs

[#7]

@lyndon_s87 

Looks like that the issue has been fixed.

Although seems working just for new files and not the old ones.

Anyone else has the same issue?