Forum Discussion
All our Surface Hubs stopped communicating with Azure Log Analytics
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
MicrosoftHello 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
- The Surfaces have now been sending data to Log Analytics for a while now, but for some reason the DeviceConnectSession is empty.
It is like the surfaces are not sending data about wired and wireless projections anymore, or they get lost somewhere in Log Analytics.
Anyone else that can confirm that they are not receiving any DeviceConnectSession data in Log Analytics from the Surfaces?
Regards
Thomas - Hi,
It is also working here for a few weeks now.
Regards
Marc - Thomas we can confirm also data is now free flowing. However miracast data no longer appears to work. We have been asked to create a case with the log analytics team to possibly update the parameters that it requires to get this info. Does yours work or have you solved this already?
- Hi,
I can confirm that after installing the latest update to the Surface HUB, everything started to work and data is now arriving in Log Analytics.
I hope that you all experience the same.
Best Regards
Thomas Same issue here, same network, nothing from our Surface Hub 2s running 20H2. We have a device on the Insider program and we are receiving data in DeviceHeartbeat, DeviceEtw and DeviceSkypeHeartbeat.
- Just to update this to everyone as Cezar mentioned we are trying to work with the support engineers on this. We had mixed results.
85" Hub 2S with Insider Preview did enroll and is now seen and we can get a heartbeat from it. This unit also happens to be AAD joined and Intune enrolled
50.5" unit with standard unit, local admin only, not intune enrolled, standard production build and while agent loaded on hub side the Azure side cannot see it.
They are both on the same network. We will see what feedback we get on this. - cezarcretu
Hello everyone,
Allow me to shed some light on this issue as I know how important this is.
The engineering team has focused a lot of effort & resources here to deliver a fix as fast as possible. The fix was tested internally and shown to work successfully. Unfortunately, in production we have seen mixed results. Several customers reported this is working, whereas others could only see heartbeats working but with no data being retrieved.
Therefore, we need a bit more time and patience until we investigate the issue further. Kindly work with your support engineers and provide new logs as this would help resolving the issue faster. A screenshot of your Azure Analytics Surface Hub dashboard would also be useful. Please don't post the screenshots here, it should be sent securely to your support engineer.
Best regards,
Cezar
In the answer we got on our support case they wrote that a fix will be deployed in the Azure Tenant. According to them the fix should have been deployed now.
- Hello,
I had the same answer yesterday but nothing so I ask if we need to do something and they answer me that it should be resolve by a fix yesterday or today.
Nothing yet.
I don't know if the fix is an update on surface hub or in azure. So I don't know what we need to wait.
I will check again this afternoon. Hello,
I have received a mail from the Support Engineer about that yes.
But unfortunately, it is still not working, at least for us.
I have still no heartbeat from any of our SH in the workspace.
Marc
