Forum Discussion
Scheduled meetings on Surface Hub (1703 Creators Update)
MicrosoftHello rohgin,
Retrieving your meetings and files only works with Office 365 for the reason I mentioned, you're trying to connect to a service which doesn't support this feature.
However, this doesn't limit you from joining Teams/Skype meetings organized by users outside of your domain. You can set the device to accept external meetings using the ProcessExternalMeetingMessages parameter in the Set-CalendarProcessing cmdlet. You can also forward the meeting invite to the Surface Hub if this was not done by your partner.
Would that work for you? If not, please open a support case and we can explore all the possibilities to configure the device to work as it best makes sense for your business.
Thank you,
Cezar
Yeah well, we tried the invite by external party once.
They could hear us, but they couldn't see us, while the camera was definitely working. As we could see ourselves.
Restarting the Hub didn't work. They just saw the image with the 2 letters of our hub name.
So currently we are creating the meetings to be sure everything works.
I tried forwarding, but it seems the original meeting created by the other party doesn't get the update that an user/device has been added, so there's no join button available on the Surface Hub.
- cezarcretu
Hello rohgin,
The video issue definitely needs to be investigated, I suggest opening a ticket with the Teams team (you can do it from the Office 365 portal).
The join button issue for forwarded meetings might be due to Windows Defender Safe Links. The Surface Hub will scan meeting invites for the Teams URL so if that is hidden, it won't show the meeting join button. Can you check how these look on the device account calendar? You can use OWA to check it.
I strongly encourage you to open a support ticket so we can resolve the issues and be happy with your Surface Hub
Thank you,
Cezar
I just tested the forwarding, it actually works when I send a meeting request from my on-premise user to one of our 365 accounts, next I forwarded the meeting request to the Surface Hub from the 365 user, and now it's actually showing the "Join" button.
But a friend of mine from a different organisation did send me an invite, and the original invite didn't have a join button, neither on the surface hub or my personal account where he did send the invitation to, so it's already missing on the original invitation. I was able to use the "Join Meeting" link in the body of the calendar item, but since the surface hub isn't able to open the actual item, It's depending on the join button. Most external invitations we receive do have the Join button, but it seems that sometimes from some companies it doesn't. So normally it doesn't matter when I'm able to use the link, but since the Surface Hub is depending on the button, I can't trust to tell my users to use this method while sometimes the button is not visible on the invitation. That's just not a workable solution.
So currently I'm testing it, the guy from Microsoft did send me an invite and the join button was visible, it seems it has something to do with the time settings. so probably when the join button isn't available, it's because the person who made the invitation, didn't have the correct time settings.
Update, that wasn't the problem, I'm thinking it has something to do with OAUTH not implemented, they have a hybrid environment, I think they haven't configured OAUTH, since he told me they didn't have the calendar button on Teams yet.
- cezarcretu
Hello rohgin,
The meeting URL shouldn't change based on the OAUTH settings of the inviter. As I said, the Surface Hub will scan all incoming meetings and if it finds a Teams URL it will show the Join button.
Current investigations show that the issue might be with the Outlook client when forwarding external meetings to the Surface Hub. Can you try to forward the same meeting using OWA instead?
Or better yet, login with your credential in "My meetings and files" and try to join the call from there instead (no forward to the Hub)
Thank you,
Cezar