Home
Microsoft

Skype Room Systems v2 3.1.112.0 Update

SRSv2 3.1.112.0 has been available as an automatic update to all devices since June 5th.

 

3.1.112.0 Release Notes are as follows:

  • Fix to address console responsiveness issues observed on Surface Pro 2017-based SRSv2 devices connected to two front-of-room displays and video ingest.  More background detail here.
  • Automated check to ensure that system is running latest provisioning version.

The SRS team is working to make a downloadable MSI version of this update available soon.  Stay tuned for more information.

23 Comments
Frequent Visitor

Will this fix the issue with the on-screen keyboard not showing?

Microsoft

@William Perry The provisioning check might address the issue if you were on an older version.  Please let me know your experience after the update is applied.

Occasional Visitor

Hi David,

 

Is this build has support for RS4?

If yes, where is the link to download the SRSDeploymentKit?

 

Thanks.

Microsoft

@Nathan Ngo - We continue to have a block on RS3 and RS4.

 

We plan to post a link to the msi download.  Please monitor this blog for status update.

Frequent Visitor

Hi David

 

Does this version support assigning QoS policies using Powershell on the device. I did some testing point to point and it seems that the SRS is using port ranges in the 5XXX range and the Skype for Business is using the normal ranges of 50XXX. I canot find any documentation for this version or any others around the port usage of the SRS. Do you have a document outlining this so we can assist people with defining policies for QoS and placing in the correct categories. (voice, video, content, file sharing etc.).

 

Here is an example: It matches on the app but I am not sure  what ranges it uses. Does not appear to behave like the Skype for business client.

 

New-NetQosPolicy -Name “Skype Room System” -AppPathNameMatchCondition Microsoft.SkypeRoomSystem.exe -IPProtocol Both -IPSrcPortStart 1024 -IPSrcPortEnd 65535 -DSCPValue 46

 

 

Frequent Visitor

Hi David

 

Do you know if SRS v2 supports VBSS? I saw a post regarding Microsoft SRS not supporting VBSS. But maybe that was V1? I'm interested as the Polycom Group Series support VBSS as well as the SFB 2016 clients so if it does not and you have a mixed environment, then the clients will never get the benefit of VBSS sharing while in a multi party conference. I assume it will be a mute point with MS Teams Client as that's Rest Http?

Microsoft

@Andrew Fullagar Yes, SRS v2 supports VBSS.  As you point out, SRS v1 is the version that does not support VBSS.

Occasional Visitor

I have just installed a SRS demo/POC room and am having issues with the front of room displays not going to sleep when the Surface/SRS does.

 

System info:

- Logitech Smartdock (running the latest dock firmware) with New Surface Pro (5) running the latest v2 3.1.112.0

- Logitech Meetup Cam

- 2 x Sony KD-55X7000e (these have HDMI CEC)

 

I have tested the TV's with a Polycom Trio visual+ setup that we have which is also using CEC control and the TV's turn off and on just fine. I have also tested the HDMI cables and they work on the Polycom system. I have also tried another cheap TV that we are using with our Polycom setup and that does not work with the SRS. I think that I have eliminated all external factors and believe that the issue resides with either the SRS software or the Logitech smartdock.

 

Is anyone else seeing this issue?

Senior Member

I have many Skype Room Systems this morning unable to run the Skype Room Systems app...getting this error message. As you can see they are all on 3.1.112.0.

 

image.png

Occasional Visitor

We are receiving same error as @Nick DiFeo@David Groom any work around or fix for this issue

Senior Member

@Nagarjun Reddy SattyMy workaround for today is logging into the Admin account and running the SRS app from there.

Occasional Visitor

Thanks @Nick DiFeo uninstalled KB that was installed yesterday. It's working now 

Microsoft

@Nagarjun Reddy Satty Which KB number did you need to uninstall to address the issue?

Microsoft

@Nagarjun Reddy Satty Also, please confirm which OS version (1703 or 1709) you're using in addition to Make and Model details of the system you on which you observed the error notification.

Microsoft

@Nick DiFeo Would you also be able to confirm which OS version (1703 or 1709) you're using as well as Make and Model details of your system?

Senior Member

@David Groom  The affected devices are Logitech SmartDocks with a Surface Pro 4 and 1709 installed

Microsoft

Anyone blog readers seeing Nick's error above on the Surface Pro 2017 (not Surface 4)?

Occasional Visitor

@David Groom Logitech Smart Docks with a Surface Pro 4 and 1709(16299.461) installed, KB4284819 uninstalled

Senior Member

Today more SmartDocks were impacted by this issue, some of them are on 1703 this time and received update KB4284874.

Occasional Visitor

Where can one find the current MSI?  I am not able to locate it.

 

Thank you,

Adam

Frequent Visitor
Our units have upgraded to a new version of the SRS app, 3.1.113.0, but I don't see a post announcing this version. Are there any new features or fixes we should be aware of?
Microsoft

@Brayden Hull 3.1.113.0 was released on June 13th.  No new features or fixes in this update.  3.1.113.0 implement changes related to SRSv2 handling of Windows Updates to the system.  No actions required by the IT Pro.

Frequent Visitor

FYI to anybody using OMS or similar tools with Event Log monitoring, you may see new undocumented event IDs due to the change that David mentioned above. They come from a script introduced in 113 called "ApplyWindowsUpdatePolicy.ps1" which runs on logon. Event ID 1009 is informational, 1010 is a warning and 1011 is an error.

 

You'll see 1009 everytime this script runs, either "Found Existing Registry::HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings" or "Did not find existing Registry::HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings. Creating a new one." The actual Windows Update options being changed are the branch readiness level, it is set to CBB and defer feature updates is set.

 

Ideally this page should be updated https://docs.microsoft.com/en-us/skypeforbusiness/manage/skype-room-systems-v2/oms