Forum Discussion

Copper Contributor

Apr 16, 2018

Solved

SharePoint 2016 (on-premise) on Surface Hub

Hi, We are looking at purchasing a few Surface Hubs for our new office and recently visited a vendor who had some demo units. During the demo we logged into the unit using a corporate account and...

Daniel Hudson
Apr 16, 2018
Hi George

When you first complete the OOBE (Out-of-box Experience) you will be given the option of joining the Surface Hub to your domain (either AD on-prem or Azure AD). When connected, you should then be able to access your on-prem resources, such as SharePoint.

We have legacy SharePoint 2010 still and can access find from Surface Hub (although we're prompted for authentication from a user account, unless the user is signed into the Surface Hub at the time).

Long story short, you likely had issues as the demo unit, I'm guessing, wasn't inside your domain at the time.

Thanks
D

George Hewitt

Copper Contributor

Apr 16, 2018

Yep the demo unit was external to the network. I think that's a sensible explanation so we'll go for that for now!

Thanks,
George

George Hewitt

Copper Contributor

May 29, 2018

So we now have the demo unit (55") and fully patched.

Unfortunately we still can't access SharePoint 2016 documents. The hub prompts for user/pass with a Windows authentication dialogue but then it immediately fails with an authentication error: "Can't open file. <Filename> may be locked, in use, or you don't have sufficient permissions"

Looking at the IIS logs on the SP server, we can just see 401 errors. It isn't even being passed a username. E.g.

2018-05-29 11:19:41 172.16.255.170 OPTIONS /clients/Client1/Projects/Folder/ - 443 - 192.168.10.157 Microsoft+Office/16.0+(Microsoft+Office+Word+16.0.9330;+Pro) - 401 0 0 31

2018-05-29 11:19:41 172.16.255.170 HEAD /clients/Client1/Projects/Folder/Document.docx - 443 - 192.168.10.157 Microsoft+Office+Word+2014 - 401 0 0 31

Anyone got any clever ideas? The Hub is domain joined but that shouldn't make a difference either way (my understanding is the Hub doesn't actually do anything for normal authentication with AD, only for administration)