Forum Discussion

Vincent Sok's avatar
Vincent Sok
Copper Contributor
Jul 31, 2017

Single Sign On Issues with 1703 Creators Update Surface Hub

Hi All,    First Post here on the forums   We haven't had the greatest start with the Surface Hubs we purchased we had. Hopinh to turn things around :)    We have 4 Surface Hubs   3 x 84"  1...
Gabriel Sampson's avatar
Gabriel Sampson
Copper Contributor
Jan 16, 2018

I'm having the same issue with a 55" Surface hub.  Any known resolution yet?

  • MAX NOBLE's avatar
    MAX NOBLE
    Copper Contributor
    Jan 25, 2018

    Hi All

     

    I have been working with Microsoft for the Past 6 Months on this issue

     

    It looks like RS1 SSD's that are patched to RS2 with updates are not taking correctly

     

    The way I have got it to work is to do the following -

     

    Install a RS2 SSD and download updates, since this has been done it is now working

     

    I am currently having to clone the RS2 SSD

     

    I have had to format the RS1 SSD from the Surface Hub

    Then the Clone of the RS2 SSD onto the RS1 SSD

     

    Takes around 30 minutes to Clone the SSD and around 2 Hours to install all the updates

     

    You will lose all configuration on the Hub and have to do the OOBE

     

    So far I have 15 hubs to complete this on so I will be busy for the next few months

     

    It has allowed me to now Single Sign On and provide functionality to our Users

     

    I would recommend speaking to Microsoft and requesting a RS2 SSD and enjoy the Fun of reconfiguration

     

    At least it is not as bad as Cloud Recovery Options

     

    :)

     

     

    • Jesper West's avatar
      Jesper West
      Brass Contributor
      Feb 06, 2018
      Really? Seems like MS needs to ship a 1709 with this fixed asap...
      • Daniel Hudson's avatar
        Daniel Hudson
        Iron Contributor
        Feb 06, 2018

        Microsoft are not shipping 1709 for Surface Hub.

         

        Jeffrey Allen mentioned it here and I have since been able to corroborate this both at the recent Tech Summit and elsewhere. Microsoft are instead looking to release features from 1709 and beyond in with the regular cumulative updates to 1703. It's less risky and allows them finer control over the content reaching Surface Hub.

         

        No point risking features and fixes on big build updates that won't really give much to the Surface Hub experience.

         

        While I can't give much info, it does look like a fix is in development for this specific bug, but currently no ETA on deployment except for 'soon'.

         

        If it's a show stopper, get in touch with MS support and get a new RS2 SSD for your Surface Hub that won't have the same issue.

Resources