SOLVED

SharePoint 2016 (on-premise) on Surface Hub

%3CLINGO-SUB%20id%3D%22lingo-sub-183097%22%20slang%3D%22en-US%22%3ESharePoint%202016%20(on-premise)%20on%20Surface%20Hub%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183097%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20looking%20at%20purchasing%20a%20few%20Surface%20Hubs%20for%20our%20new%20office%20and%20recently%20visited%20a%20vendor%20who%20had%20some%20demo%20units.%20During%20the%20demo%20we%20logged%20into%20the%20unit%20using%20a%20corporate%20account%20and%20were%20able%20to%20access%20content%20in%20OneDrive%20for%20Business%20as%20well%20as%20SharePoint%20Online%2C%20however%20we%20could%20not%20access%20content%20in%20SharePoint%202016%20(on-premise)%20where%20we%20still%20hold%20plenty%20of%20business%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20setup%20is%20hybrid%20O365%2Fon-prem%20for%20most%20things%20and%20we%20have%20ADFS%20%26amp%3B%20WAP%202016%20deployed.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20wish%20I%20had%20taken%20a%20screenshot%20of%20the%20error%20-%20but%20I%20forgot.%20It%20was%20something%20related%20to%20authentication.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20suppose%20I%20wanted%20to%20know%2C%20is%20it%20possible%20to%20access%20SharePoint%20on-prem%20data%20using%20the%20Surface%20Hubs%20or%20is%20it%20literally%20cloud%20only%3F%20Googling%20doesn't%20give%20a%20clear%20answer.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-198449%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202016%20(on-premise)%20on%20Surface%20Hub%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-198449%22%20slang%3D%22en-US%22%3EThanks%20Dan%2C%20yes%20already%20have%20one%20raised%20and%20awaiting%20a%20response.%3CBR%20%2F%3EI%20suppose%20it's%20still%20early%20days%20in%20the%20grand%20scheme%20of%20the%20Surface%20Hub%20ecosystem...%20googling%20for%20%22Surface%20Hub%20SharePoint%202016%22%20returns%20this%20thread%20now%20as%20a%20nearly-top%20result%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-198446%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202016%20(on-premise)%20on%20Surface%20Hub%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-198446%22%20slang%3D%22en-US%22%3EHi%20George%3CBR%20%2F%3E%3CBR%20%2F%3EWhile%20I'm%20sure%20there's%20clever%20enough%20people%20around%20here%20to%20help%20with%20this%20kind%20of%20issue%2C%20I%20would%20highly%20recommend%20instead%20that%20you%20raise%20a%20support%20ticket%20with%20Microsoft%20to%20look%20into%20this%20further.%20They%20can%20then%20confirm%20if%20it's%20a%20known%20issue%2C%20if%20they%20have%20a%20solution%2C%20or%20obtain%20logs%20from%20your%20Surface%20Hub%20to%20look%20into%20the%20behaviour%20further.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-gb%2Fhelp%2F4037644%2Fsurface-contact-surface-warranty-and-software-support%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-gb%2Fhelp%2F4037644%2Fsurface-contact-surface-warranty-and-software-support%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%3CBR%20%2F%3EDan%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-198444%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202016%20(on-premise)%20on%20Surface%20Hub%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-198444%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20we%20now%20have%20the%20demo%20unit%20(55%22)%20and%20fully%20patched.%3C%2FP%3E%3CP%3EUnfortunately%20we%20still%20can't%20access%20SharePoint%202016%20documents.%20The%20hub%20prompts%20for%20user%2Fpass%20with%20a%20Windows%20authentication%20dialogue%20but%20then%20it%20immediately%20fails%20with%20an%20authentication%20error%3A%26nbsp%3B%3CSPAN%3E%22Can't%20open%20file.%20%3CFILENAME%3E%20may%20be%20locked%2C%20in%20use%2C%20or%20you%20don't%20have%20sufficient%20permissions%22%3C%2FFILENAME%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20at%20the%20IIS%20logs%20on%20the%20SP%20server%2C%20we%20can%20just%20see%20401%20errors.%20It%20isn't%20even%20being%20passed%20a%20username.%20E.g.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2018-05-29%2011%3A19%3A41%20172.16.255.170%20OPTIONS%20%2Fclients%2FClient1%2FProjects%2FFolder%2F%20-%20443%20-%20192.168.10.157%20Microsoft%2BOffice%2F16.0%2B(Microsoft%2BOffice%2BWord%2B16.0.9330%3B%2BPro)%20-%20401%200%200%2031%3C%2FP%3E%3CP%3E2018-05-29%2011%3A19%3A41%20172.16.255.170%20HEAD%20%3CSPAN%3E%2Fclients%2FClient1%2FProjects%2FFolder%2FDocument%3C%2FSPAN%3E.docx%20-%20443%20-%20192.168.10.157%20Microsoft%2BOffice%2BWord%2B2014%20-%20401%200%200%2031%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20got%20any%20clever%20ideas%3F%20The%20Hub%20is%20domain%20joined%20but%20that%20shouldn't%20make%20a%20difference%20either%20way%20(my%20understanding%20is%20the%20Hub%20doesn't%20actually%20do%20anything%20for%20normal%20authentication%20with%20AD%2C%20only%20for%20administration)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-183206%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202016%20(on-premise)%20on%20Surface%20Hub%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183206%22%20slang%3D%22en-US%22%3EYep%20the%20demo%20unit%20was%20external%20to%20the%20network.%20I%20think%20that's%20a%20sensible%20explanation%20so%20we'll%20go%20for%20that%20for%20now!%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%2C%3CBR%20%2F%3EGeorge%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-183170%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202016%20(on-premise)%20on%20Surface%20Hub%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183170%22%20slang%3D%22en-US%22%3EHi%20George%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20you%20first%20complete%20the%20OOBE%20(Out-of-box%20Experience)%20you%20will%20be%20given%20the%20option%20of%20joining%20the%20Surface%20Hub%20to%20your%20domain%20(either%20AD%20on-prem%20or%20Azure%20AD).%20When%20connected%2C%20you%20should%20then%20be%20able%20to%20access%20your%20on-prem%20resources%2C%20such%20as%20SharePoint.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20have%20legacy%20SharePoint%202010%20still%20and%20can%20access%20find%20from%20Surface%20Hub%20(although%20we're%20prompted%20for%20authentication%20from%20a%20user%20account%2C%20unless%20the%20user%20is%20signed%20into%20the%20Surface%20Hub%20at%20the%20time).%3CBR%20%2F%3E%3CBR%20%2F%3ELong%20story%20short%2C%20you%20likely%20had%20issues%20as%20the%20demo%20unit%2C%20I'm%20guessing%2C%20wasn't%20inside%20your%20domain%20at%20the%20time.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%3CBR%20%2F%3ED%3C%2FLINGO-BODY%3E
New Contributor

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 were able to access content in OneDrive for Business as well as SharePoint Online, however we could not access content in SharePoint 2016 (on-premise) where we still hold plenty of business data.

 

Our setup is hybrid O365/on-prem for most things and we have ADFS & WAP 2016 deployed. 

 

I wish I had taken a screenshot of the error - but I forgot. It was something related to authentication.

 

I suppose I wanted to know, is it possible to access SharePoint on-prem data using the Surface Hubs or is it literally cloud only? Googling doesn't give a clear answer. 

 

Thanks,

5 Replies
best response confirmed by George Hewitt (New Contributor)
Solution
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
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

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)

Hi George

While I'm sure there's clever enough people around here to help with this kind of issue, I would highly recommend instead that you raise a support ticket with Microsoft to look into this further. They can then confirm if it's a known issue, if they have a solution, or obtain logs from your Surface Hub to look into the behaviour further.

https://support.microsoft.com/en-gb/help/4037644/surface-contact-surface-warranty-and-software-suppo...

Thanks
Dan
Thanks Dan, yes already have one raised and awaiting a response.
I suppose it's still early days in the grand scheme of the Surface Hub ecosystem... googling for "Surface Hub SharePoint 2016" returns this thread now as a nearly-top result :)