Forum Discussion

MarcVDH's avatar
MarcVDH
Iron Contributor
Jan 22, 2021

All our Surface Hubs stopped communicating with Azure Log Analytics

Hello, All our Surface Hubs have stopped communicating with the Log Analytics workspace and we don't find why. We have Surface Hubs, Surface Hubs 2S, same problem. All are configured through Intun...
cezarcretu's avatar
cezarcretu
Icon for Microsoft rankMicrosoft

Hello MarcVDH ,

 

Yes, this is a known issue with Log Analytics and unfortunately we can't share anything more with you other than we're looking into it. We also can't share an ETA for a fix as it would be a guess at this point, which others would interpret it as a promise. I can assure you that we are working with the Azure Log Analytics team to resolve this as fast as possible. We're on it, it just takes time so thank you for your patience!

 

As to WSUS, yes, the 20H2 update is only available through Windows Update, Windows Update for Business and BMR. This was announced here: Surface Hub Windows 10 Team 2020 Update available October 27 - Microsoft Tech Community.  

 

Best regards,

Cezar

MarcVDH's avatar
MarcVDH
Iron Contributor
Mar 04, 2021
Hello Cezar,
Thank you for your answer.
We have a meeting about that problem with Microsoft on monday.

When we started the implementation of the SH in our company (a long time ago) we were told by MS that we could use WSUS for everything because we wanted more control about the deployment of the updates so we didn't looked at the other options.
Now in your article, i agree, it says Windows Update and not WSUS, but WSUS is only a tool using Windows Update so it wasn"t very clear that the update wouldn't come to WSUS. That's why I asked at the end of the article.
In the known issue of the update, now we can see 'If using WSUS, migrate to Windows Update for Business.'.
So ok, we will migrate to WUfb. We are trying with one machine at the moment and the result are not good. The machine is connected for more than one day (I can see the last check-in time changing from time to time) but the last scan time stays desperately on 'not scanned yet'.
I have seen on the forum that the machine should check every 22 hours and that there is no way to remotely force a scan.

I think Microsoft should at least change the date for the end of support of the 1703 version.

Regards
Marc

  • cezarcretu's avatar
    cezarcretu
    Icon for Microsoft rankMicrosoft
    Mar 04, 2021

    Hello MarcVDH 

     

    WSUS still works with Surface Hub, except this update and probably a few more to come. My understanding is that WSUS doesn't work with manifests which is required by the 20H2 update.

     

    If you're trying to update a Surface Hub V1, please make sure you enable Full Telemetry first. This is required for the update to be detected.

     

    If you still have issues, please open a case so we can look into this

     

    Thank you,

    Cezar

    • MarcVDH's avatar
      MarcVDH
      Iron Contributor
      Mar 04, 2021
      Hello Cezar,
      We have deployed a configuration profile for configuring the telemetry like indicated in the doc but when deployed, the device status for the CP indicates that the status is 'Not Applicable' for all of our machines.
      I am waiting till Monday, then we will wee how it goes.

      Thanks
      Marc
      • Thomas Forsmark Sørensen's avatar
        Thomas Forsmark Sørensen
        Copper Contributor
        Apr 13, 2021

        MarcVDH 

         

        Do you know if this issue has been resolved?
        I have an issue where a Surface Hub that is not sending data to Log Analytics.

        Thomas

Resources