02-13-2018 06:27 AM
Hello,
I received a notice from a user in our Enterprise. She is connecting to a meeting and the following is displayed when the presenter tries to share her screen. Look familiar to anyone? What should I be looking at to resolve?
Thanks!
Joe
02-13-2018 06:44 AM
02-13-2018 07:37 AM
Operating system
02-13-2018 03:07 PM
02-19-2018 02:52 PM
Anyone figure this out?! This is killing us.
It appears to only happen in a peer to peer scenario, or at least mostly. Tried several different versions of S4B. We're actively seeing the client trying to share content respond with a reset packet. So something on the client is actively doing this.
Thanks!!!
02-20-2018 06:45 PM
02-21-2018 07:58 AM
02-21-2018 08:06 AM
Solution02-21-2018 08:07 AM
02-21-2018 08:57 AM
02-21-2018 10:34 AM
02-21-2018 12:07 PM
02-21-2018 12:15 PM
05-02-2019 05:45 AM
We struggled with this for quite some time. We opened at least two tickets for this with MS, and we always were give the keys referenced in this thread. It turns out that a new ticket with MS revealed that we need to add more keys to disable VBSS in conferences. The keys we had been given disabled VBSS in P2P conversations, the new keys disable VBSS in conferences:
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Lync]
"EnableConferenceScreenSharingOverVideo"=dword:00000000
Additionally, if you use the 32-bit version of Skype for Business 2016 on a 64-bit operating system, add the following subkey:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\16.0\Lync]
"EnableConferenceScreenSharingOverVideo"=dword:00000000
Deploying these keys and hoping that this is the end of this. Although I am trying to get the MSI codebase fixed to be able to use VBSS reliably rather than having to hack the registry to revert to RDP (not holding breath).