SRSv2 update 22.214.171.124 has been release to the Store since August 27th Redmond time.
126.96.36.199 Release Notes
One of my Logitech Smartdocks does update what do I need to check to get it to update.
@David Groom wrote:SRSv2 update 188.8.131.52 has been release to the Store since August 27th Redmond time. As with all updates, we start by making the update available to 10% of customer devices. We then continue by throttling up to 100% in the following days. 184.108.40.206 Release Notes "Report a Problem" feature improvements in Teams mode (equivalent of "Give Feedback" in Skype for Business mode)Enable ability to fallback from Teams to Skype for Business mode for SIP callsAccessibility improvements (Narrator, Magnifier)Automatically restart app when required after XML provisioning changes have been appliedMiscellaneous fixes
SRSv2 update 220.127.116.11 has been release to the Store since August 27th Redmond time. As with all updates, we start by making the update available to 10% of customer devices. We then continue by throttling up to 100% in the following days.
@Hi @David Groom, when will deployment toolkit be updated (https://go.microsoft.com/fwlink/?linkid=851168)?
@Pavel Aivazov I expect that the msi will be available next month (September).
When will SRS support TLS v1.2?
We're proceeding in our migration to TLS v1.2 but, according to https://blogs.technet.microsoft.com/nexthop/2018/04/18/disabling-tls-1-01-1-in-skype-for-business-se..., SRS is not yet supported (check back often)
@Brian Longworth +1, @David Groom, what's plan for TLS 1.2 support?
@David Groom We use SCCM to deploy our SRS images. The current SRSv2 deployment kit documented at this location still reflects a 18.104.22.168 version. The 4.x.x.x version has significant differences and I have not been able to locate the SRSv2 deployment kit for the 4.x.x.x version. Can you give us an update on when the SRSv2 deployment kit will be updated?
@David Groomwe deployed a new device and unfortunately we must use the 3.1.115 Build, but now this device won't update to a newer one? Any change to force the update to a least 22.214.171.124?
Hi @David Groom,
Thank you for the release notes on the update.
As the deadline for the TLS 1.1 switch off is coming soon we are getting tech savy clients asking us if their investment in the SRSv2 room systems are going to work with just TLS 1.2.
There is lots of documentation in the net that says they are under review but nothing confirming it will work.
I am advising clients that it will be working under TLS 1.2 as the underlying Windows 10 operating system supports TLS 1.2 out of the box. As the application is an UWP application running on top of I assume a .NET framework which should also support TLS 1.2.
Am I correct to offer this advice or is there going to be an issue with the SRSv2 products.
@David Groom its already , 126.96.36.199 . Whats with this update by the way?
@rodelmurex We released 188.8.131.52 on August 31st to address a regression introduced by 184.108.40.206 on Crestron SR devices. This regression disabled the ability to launch the Crestron application which would normally be accessible by pressing the app button. The regression is resolved once the 220.127.116.11 update is applied and SRSv2 app restarted.
out of topic question.
Did you guy's change your wallpaper? i want to do it but anyone can post a guide .
@rodelmurex - Did you see this article about setting themes?
Just out of curiosity, do you too experience a grainy picture when sharing an external source (e.g. Notebook) over Skype Room System?
We just did a rollout of a few dozen devices and this is how it looks like when connected to our Polycom MSR device, compared to the same content over RDP.
I know it's probably not the right place to ask this, but I'm somewhat desperate.
I can reproduce it with a all external devices (Mac's over HDMI, Windows 10 1709 over DisplayPort).
If someone would have a hint for a solution, I would be very greatful.
Best regards and thanks,
Hi @Emanuel Malacarne, I have 400+ Lenovo and Logitech Smartdocs installed and have never seen this issue. I think it is Polycom specific. I would check if they have dock firmware updates.
Thanks for the reply.
In that case, I'm confident that it's isolated to Polycom. I'll reach out to them.
Once I find a solution, I'll still upload it here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.