Forum Discussion
All our Surface Hubs stopped communicating with Azure Log Analytics
ToddMethven thanks for your answer.
I had opened a case on 25/01. The answer I got is 'it's a known issue, we are working on it. No ETA, sorry'
We had exactly the same problem. I passed 1h to try understand how works logs in analytics...
And I have the same idea with firewall problems but not test.
I thought I was going to look on the community to see if anyone had this kind of problem and this is the first post.
I just see this because I didn't need to go on logs before this last days since we have some problems with Miracast.
Monday I had install the new OS for surface hub on a surface hub 2 but I don't see it on logs so the new OS don't seems to resolve this problem.
I open a case to surface hub.
Good luck because for us it is still the same. Support from MS is non-existent, the only communication we receive is 'nothing new'.
And now you have the new Surface Hub Windows 10 Team 2020 Update, still nowhere to be found in WSUS (for both v1 or v2).
The current OS is out of support in 12 days.
We have enrolled a machine in WUfB to see if there we would be able to update the machine...nothing... more than one day later... the status of the machine is 'not scanned yet' and we have no possibility to force a scan for updates.
So what is the solution ? send technicians all over the country with a USB key to do the install ?
These devices are driving us nuts.- cezarcretu
Microsoft
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
- 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
