02-12-2019 05:27 AM
We have a Lenovo ThinkSmart Hub 500 which is completely rebooting when in a multi party SfB call. This happens when the third or fourth party joins the call. There is no content being shared from the Lenovo. Rejoining the call with five parties already in the call causes it to reboot again.
Any suggestions to troubleshoot?
02-15-2019 12:08 AM
Welcome and sorry for the late response. I discussed your situation with a colleague and if you haven't already the suggestion is to reimage the device. Recovery media is available through Lenovo Support or you can following the following process to create your own recovery / installation media.
English Community Leader
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star below their post awarding them Kudos
Please don't ask me questions by Personal Message; questions belong in the forums.
02-15-2019 07:43 AM
Just tried the Microsoft process and it requires me to have Windows 10 IOT Media and licenses which I don't have.
Will go back to Lenovo support about recovery media.
05-29-2019 04:19 AM
We are also having this issue on all our Lenovo units (We have 5 currently). We have tried reimaging them and updating the drivers, but they all randomly reboot on multipoint SfB meetings... Did you get anywhere with a fix for this ?
06-18-2019 06:51 AM
We have 3 ThinkSmart Hub devices in three different office locations and will restart intermittently. We will only have 5 people connected via Skype for Business and from the 3 hubs and they restart randomly.
07-07-2019 10:45 AM
Anything further on this issue? We just deployed 19 of these in our corporate office and when having multi-point meetings, they will reboot upon the 4th meeting attendee join. I would say a reimage is not a good solution if the image will be the same. Is there an update or driver issue that is causing this?
07-07-2019 11:18 PM
This registry fix (found on another post) fixed it for us :-