Since the introduction of VBSS in the article Video Based Screen Sharing (VBSS) for Skype for Business last year Microsoft has released several changes to the platform to further leverage this technology. The meeting experience is built around a larger and more immersive display of video and shared content. Screen sharing from the Mac uses Video-based Screen Sharing (VbSS), which is faster and more reliable than Remote Desktop Protocol (RDP) used by SMA. The app has also been optimized to work well with macOS 10.14 (Mojave), including Dark Mode.When you click to join a meeting on a Mac, you will see this screen in your browser:"How would you like to join your meeting?" web page when joining a Skype for Business meetingSelecting Download and install Skype for Business will download the SfB desktop installer (recently reduced in size from 47 MB to 35 MB):Web page for downloading the SfB app installerClick the download to install the app. Users who do not have administrator permissions on their Mac should choose the Install for me only option on the Destination Select page of the installer.When Skype for Business opens, you have the option to sign in (if the meeting is from your own organization or an organization that is federated with yours) or to join a guest.Join as a Guest screen in Skype for BusinessWe are excited to bring these improvements to our Mac users, and we look forward to your continued feedback on Skype for Business!This entry was posted in Republished Content by Syndicated News. This mode of sharing performs better, supports higher frame rates, and the setup time is faster than RDP (our original approach to sharing).In the event that these same clients were participating in a multi-party conference then the Skype for Business Front End Server’s Application Sharing Multipoint Control Unit (ASMCU) would be driving the media control for sharing content between all parties. As covered in the previous article when this new capability was released in 2015 it was only available for peer-to-peer Desktop Sharing sessions between to 16.x version Windows clients. Conferencing SupportFirst and foremost Microsoft has delivered, in two separate stages, the ability for Skype for Business 2016 Windows clients to leverage VBSS in conferences now.
![]() Vbss For Skype For Business Install Skype ForIf any older client versions were to join the meeting then the ASMCU will immediately step-down to using RDP, just as peer sessions were already reverting to RDP in the event that the receiving party would attempt to take remote control of the session.It is important to understand that the ASMCU does not create a multiple codec stream scenario like the AVMCU can do with X-H264UC encoded video. This means that any conference hosted by a Skype for Business Online user and attended by only Skype for Business 2106 Windows clients can leverage VBSS for sharing their desktops. Early in 2016 Microsoft quietly added VBSS support to the ASMCU components in their Skype for Business Online platform. Online MeetingsSince posting that original article though this has changed. On-Premises MeetingsAs of this week with the release of the June 2016 Skype for Business Server 2015 Cumulative Update (a.k.a. Thus the inclusion of any client in the meeting which does not support VBSS (which is literally every Lync/SfB client available except for the 2016 Windows desktop client) will trigger the ASMCU to request the client that is sending content to only use RDP, otherwise referred to as a “lowest-common-denominator” experience. This is a “highest-common denominator” experience which continues to provide the SVC video streams to all other meeting participants which support that video codec, yet also allows a legacy client which only supports RTV to still see the active speaker’s video.The ASMCU does not function this way as only a single Desktop Sharing stream is provided by the sending client, it cannot simultaneously encode an SVC stream and and RDP stream. It does seem plausible that, with an understanding of VIS, one might think that X-H264UC could now be utilized to somehow provide desktop sharing across the VIS server, but how in the world could a Mediation Server leverage VBSS? The answer is that these various components are simply updated to be aware of VBSS as a media session so that they function properly, and no different than before, when VBSS is active in a call or conference. So does the Mediation Server update article. For example the Video Interop Service knowledge base article states that this cumulative update introduces VBSS. With the application of these server updates the ASMCU and all related components are now VBSS-aware and the functionality is identical to what is explained above, although it can be turned off if desired.Upon closer inspection of the various June update articles there exists one interesting item that may seem a bit confusing at first glance: some of seemingly unrelated server components are referencing VBSS updates. ![]() ![]() 1018 Click-to-Run version.)" Enable ConferenceScreenSharingOverVideo"=dword:00000000The TechNet documentation is currently a bit vague here as while these parameters are included, the actual implementation of them is vague and confusing. (Some of the testing performed for this article was using the. While not specifically stated in the Microsoft documentation, assume that the June update for the Skype for Business 2016 client is also needed in order to support this new setting. It does not matter if the ASMCU still prefers to use VBSS by default though as if any or all connected clients have this disabled then they will not attempt to use it and instead force the use of RDP as the only remaining option.With the addition of VBSS support in conferences there is now another new registry value made available to the client. Using either the Registry Editor (or an Active Directory Group Policy configuration) set either of these registry values to control the applicable client(s) based on their platform (32 or 64 bit)." Enable P2PScreenSharingOverVideo"=dword:00000000Keep in mind that disabling this feature will mean that if the affected client joins a conference were VBSS is available then the ASMCU will be forced to revert to the lowest-common-denominator scenario and fallback to using RDP for all attendees. Download video from youtube and vevo for macServer-Side ConfigurationAnother approach is to control the behavior directly from within Skype for Business Sever. Given the amount of other incorrect information currently in that document it is difficult to state why it might not be supported. Yet testing showed that the expected behavior is seen when only one of the two modes are disabled. Note that EnableVideoBasedSharing parameter should be enabled by default after the successful installation of CU3. In the Skype for Business Server Management Shell use the Get-CsMediaConfiguration cmdlet to verify the current configuration. These settings are only available for on-premises deployments as Online tenants clearly could not be given control of a multitenant-impacting feature such as this in the various ASMCUs across the cloud.The first server-side option applies only to conferences by turning off VBSS at the ASMCU level.
0 Comments
Leave a Reply. |
AuthorCindy ArchivesCategories |