Sep 05 2018 11:52 PM
Sep 05 2018 11:52 PM
According to the Surface Hub Update History, the August 2018 cumulative update brings support for Microsoft Teams meetings on Surface Hub.
I should note that I haven't yet tried this on a release build, so I don't know yet if the instructions for the Insider Preview build are the same, or if this even works fully (as there are no instructions yet in the admin guide).
For those wanting to try, you will need to install the Microsoft Teams for Surface Hub (Preview) app from the Microsoft Store, and you'll also need to configure 2 SurfaceHub CSP settings (either via MDM or provisioning package):
Set to integer, values below:
0 - Skype for Business is the preferred app on the Surface Hub's Start Screen, however you can still join Microsoft Teams meetings.
1 - Microsoft Teams is the preferred app on the Surface Hub's Start Screen, however you can still join Skype for Business meetings.
2 - Microsoft Teams is the exclusive app on the Surface Hub's Start screen and Skype for Business is disabled
Set to string. Value must be Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Team
If anyone gives this a go, let us know below how you get on!
Sep 06 2018 12:56 AMSolution
Yes, we have the Microsoft Teams app available for all Surface Hubs running with Windows 10 Team Edition 1703.15063.1292. To make sure you're there, check you have KB4343889 installed on your Surface Hubs.
The instructions @Daniel Hudson mentioned will work for this version, by either using MDM or the pre-configured PPKG files.
Make sure you choose the functionality mode that works best for you :)
Sep 11 2018 12:17 AM
I've been looking forward to do this for so long, as it really is a major dependency for us to move forward with the whole journey from SfB to Teams within our company. Unfortunately after deploying the app and the config it seems the app tile is available but it will just basically load whiteboard 2016 and a big black bar where the MS teams UX should be. It says on the top of the section that is Microsoft Teams, but the rest is solid black.
I had chosen mode 1, to still currently planned SfB meetings from the device? Should the Hub user account have a Ms Teams license associated with it, or just its current skype for business plan 2 license? Or Any other changes that have to be made on the user account that is being for the Hub?
Sep 11 2018 02:24 AM
You must have a Microsoft Teams license assigned to the user to be able to connect Surface Hub Teams client.
Otherwise, as you mentioned, you'll get a black stripe where the Teams UX should be.
Without the license:
With the license:
Sep 11 2018 03:25 AM
Sep 11 2018 04:00 AM - edited Sep 11 2018 11:47 AM
The Microsoft Teams licensing will cover the Skype for Business connectivity features as well.
Sep 20 2018 10:54 AM
Sep 20 2018 11:16 AM - edited Sep 20 2018 11:17 AM
I've never had an issue with installing provisioning packages. Can you give us some screenshots of how you've set up the provisioning package in ICD?
Sep 24 2018 07:34 AM
I downloaded the provisioning packages from the site above. Then I tried installing it on the Surface Hub. I keep getting an error message.
Oct 18 2018 07:44 AM - edited Oct 18 2018 07:46 AM
We are having the same issue with the Surface Hub. The Team Client remains black like in Yoav Barzilay screenshot.
We followed this instruction and installed the TeamsRTMMode0.ppkg via USB.
The Surface User, which is also used for Skype for Business, was assigned the following license: Office 365 A3 Only the Microsoft Teams license.
Unfortunately, without any success. Do you have any idea?
Oct 18 2018 08:06 AM
For the sake of the test, can you please assign the TeamsRTMMode1.ppkg file and see if the client signs in?
Oct 18 2018 08:24 AM
thank you very much for your quick response!
Unfortunately we have the same issue. :(
Here additional photos:
Oct 19 2018 12:13 PM
Also maybe for the sake of testing switch skype for business plan 2 (and exchange 2 potentially) from your E3 License.
It Could be SFB 2 is still a general requirement. I have this one still switched on, on my license that is assigned the user account along with ms teams
Oct 22 2018 05:14 AM - edited Oct 22 2018 05:16 AM
The same problem :(
Now I have also opened a ticket at MS
Nov 06 2018 10:05 AM
Just installed, pretty nice. Some weirdness, though - when the room leaves and rejoins a meeting, I can only see the room in the meeting, however others can see / hear the room. Also moving the mouse around causes the control buttons (mute, hangup, etc) to flash on and off. Hopefully that gets fixed.
Nov 28 2018 07:59 AM
I am having somewhat of a problem getting Teams working on our Surface Hub.
If I invite the Surface Hub to a Teams meeting, it doesn't recognize it as such. When I join the meeting it behaves as when there isn't any Skype meeting applied, which is correct, since it is a Teams meeting.
I have tried loading TeamsRTMMode1.ppkg via USB with the following result:
Can someone help?
Dec 04 2018 02:57 AM
Testing on one of our Hubs in mode 0 via Store for Business and Intune.
Works very nicely.
Only things I have noticed (currently) not working here.
- There's no chat option on the Hub (it does exist in Skype on the Hub)
- There's no use of the dynamic camera on the Hub. You can choose Left or Right in the settings but not Auto
- There's no way to initiate or see meeting notes. Usually it's the organizer who books the room and as such does not have his/her own laptop with them so I can see this becoming an annoyance for our user base. I do understand technically since the Hub is not the organizer and has no OneNote functionality built in but I am thinking end user here :)
- When in Mode 0 and you leave the teams meeting, the sidebar turn into the Skype interface which can be confusing to end users. Easiest way to re-join is to tap 'See scheduled meetings' and you can easily rejoin the meeting from there.
Still have to test Mode 1 in the coming days. Mode 2 will not be for the immediate future :)
Dec 05 2018 09:52 AM
Feb 06 2019 11:27 AM
Feb 06 2019 12:25 PM
Hi @John Guy
Not yet, but I strongly recommend that you open a support ticket so we can have a better understanding of the impact and raise the priority.