Aug 01 2017 07:25 AM - edited Aug 01 2017 07:27 AM
Hello,
We are using Skype Rooms System v2 with Logitech SmartDock.
This week the OS on Surface tablet was updated to version 1703 and after that we are experiencing a strange problem with the interface. Whenever we try to invite someone to a meeting the display keyboard does not appear. You can clearly see that the taps on the display are recognized and in the other menus where you can type something the keyboard appears. It was working properly before the update. As a temporary work-around we have attached a USB keybaord.
Does anyone else who use this system have the same problem after the update and sollution for it ?
The SRSv2 software is running version 3.0.6.0 on Win10 version 1703.
Aug 01 2017 10:59 AM
We have the exact same problem. Logitech Smartdock, working before the update to 1703. The on screen keyboard does not appear anywhere in the app, whether to invite other participants or in the settings screens. Exiting to the OS allows the keyboard to work with no problems. The SRSv2 software is running version 3.0.6.0 on Win10 version 1703 for us as well.
We haven't had a solution yet and are debating doing a reset to see if that will resolve the issue.
Aug 01 2017 01:34 PM
Aug 02 2017 11:43 AM
So we found the solution for our system. It seems that there is a setting for this which must have changed when the OS went from 1607 to 1703. We plugged in an external keyboard to test and then thought about manually launching the on-screen keyboard while being in the app and the on-screen keyboard came up and worked. After some searching we found this article:
https://www.windowscentral.com/auto-display-touch-keyboard-windows-10-desktop-mode
which directed us to the appropriate setting which was off when we checked it. We toggled the last option from off to on and all works now as it did before.
Aug 02 2017 11:47 AM
We had reviewed that same article and I'd say the text is confusing. I read that as 1607 is not supported for the image creation. Here is the exact text from the article:
Failure to create your console image according to these instructions will likely result in unexpected behavior. Windows 10 Enterprise Creators Update (build 1703) is not supported for Skype Room Systems v2 image creation.
In this new Windows 10 world we live in it's difficult to turn updates off. We bought this system pre-configured from the vendor which means we did not create the image and therefore have little to no control over updates without other advanced configuration connecting it to WSUS or other management systems. Microsoft should figure out that if they want to force updates every six months that they need to deal with these potential compatibility issues or allow exceptions.
Aug 03 2017 12:17 AM
@michael.dibenedetto wrote:
In this new Windows 10 world we live in it's difficult to turn updates off. We bought this system pre-configured from the vendor which means we did not create the image and therefore have little to no control over updates without other advanced configuration connecting it to WSUS or other management systems. Microsoft should figure out that if they want to force updates every six months that they need to deal with these potential compatibility issues or allow exceptions.
I totally agree. We are currently testing out 10 SRS-units in our company. Our plan is to install them in all our branch offices. If we can't trust the appliance to function properly after regular software updates, I fear we have to reconsider this solution. This is a major issue that Microsoft has to address if this product is going to live in the future. We can't have a situation where we need to send out our IT staff to manually fix these things.
Does Microsoft monitor these discussions?
Aug 03 2017 12:36 AM
SolutionAug 03 2017 03:33 AM
Apr 26 2018 08:58 AM
I've followed steps from Michael and Chi without success. I still do not get the KB to come up when attempting to invite a participant to a new meeting.
Oct 11 2018 04:59 PM
Same problem here on a new HP Elite Slice.
The DWORD already existed, and toggling the switch did nothing.
So... I need a keyboard with the dock now?
Feb 28 2020 08:52 AM
Anyone else still having this issue in 1903/1909? I'm having intermittent issues where it sometimes takes 2-10 reboots to get the KB to show up. @Joshua Parrish
Aug 03 2017 12:36 AM
Solution