Skype Room Systems v2 220.127.116.11 update was released to the Store on December 14th.
SRSv2 updates are released to 10% of devices with availability gradually increasing to 100% after a few days.
December 19th Status Update: 18.104.22.168 now available to 100% of devices.
22.214.171.124 Release Notes
- Display content on both Front of Room displays on dual screen systems.
- Theming and Front of Room UI improvements
An MSI version of this update is being prepared. This blog will be updated once it comes available.
Display content on dual screens??
Does this mean mirroring the same content across, or spreading participants across the screens?
It looks like the new version is offering Mirror Cast as a wireless connection option. Is there a way to remove/disable this from the SRS? (We already have a wireless connectivity option and I want to reduce confusion).
Has this introduced Miracast? That would be massive!
Does anyone have any information on the setup or configuration required to "Add this room to a meeting with your personal devices
I don't understand why things such as new features such as Miracast aren't included in the release notes?
Really great to see that "Display content on both Front of Room displays on dual screen systems" has finally been introduced as a feature with Skype Room Systems. Many of our users have been waiting for this for a long time. Good work!
This update provide a main screen UI improvement that is very good !Unfortunately, it does not fix the LED ring issue on HP Eliste slice G2, it does not illuminate anymore in green/red during the calls.I do not understand the purpose of "Add this room to a meeting with your personal devices" message, the room is not discoverable with "windows+k" (so I guess that Miracast is not enabled). What is the feature hidden behind ?Thanks,
This new feature is dependent on functionality that is not yet in the current Teams desktop/mobile client software. Once that is available then both halves of this new capability will allow it to function. Essentially, the Teams client on a personal device (like my Surface Pro) can detect that a Skype Room System is in close-proximity (when I carry my tablet into the meeting room). If I join the meeting from my device it'll trigger the SRS to join the same meeting, even without that meeting residing on the SRS's own calendar.
I like the idea of the new proximity-based join feature. Once we're ready for it, our users will love it.
Right now, we're a Skype for Business on-prem only shop, and this addition to the FoR UI has caused a great deal of confusion. Our users are expecting that they can use Miracast/AirPlay/some-other-protocol-that-they-made-up/etc to use the room system. Bluetooth beaconing is turned off, and the SRSv2 is set to Skype for Business Only mode. In this case, I expected the "Add this room to a meeting with your personal devices" verbiage to not show on the FoR display. Are we able to remove this message until we're ready?
"Add this room to a meeting with your personal devices"
Is this SRS Version ready for deployment on the latest Surface Pro 6? It's not listed yet as supported HW under:
Looks as the Pro 2017 Modell is not available anymore via our current Vendor :\
don't mess up my srs ms!!!! :)
As I understand:
a quick summary:
this feature is not yet operational since Teams is not fully compatible and Skype will never be compatible.
the text on the display saying: "Add this room to a meeting with your personal devices" can not be removed.
Hello, @IanBryant. Would you be able to post a photo of the wireless support that you describe above? I ask because Miracast support was *not* part of the 126.96.36.199 update release. However, as @Jeff Schertz points out above, we will be supporting a feature called "Bring Your Own Meeting" which enables Teams mobile clients to listen for a Bluetooth beaconing signal from the SRS device. Prior to the end of the year, this functionality had not yet been rolled out for general mobile client release, but it might be available to early adopter (TAP) customers if you are part of the TAP ring.
I'm attaching a photo of the BYOM experience as seen on my laptop here internally at the Microsoft office. As you can see, before joining a meeting, I'm notified that there is an SRS device nearby to use for the meeting that I'm about to join.
Hope this helps.
Hi everyone, to answer some of your questions:- @Bunce44, dual content display means SRS now has the ability to duplicate content connected via HDMI ingest to both screes in a dual front of room screen setup / room.
- @MattEllis @IanBryant, others, we have not enables MiraCast in SRS. We have enabled proximity based meeting join, using BT beacons for proximity. This is fully production ready on the SRS side; there is a BT beacon config setting in the SRS admin settings UX. The client side of this feature will be available in Microsoft Teams only (not SfB). Teams desktop has this feature enabled today in pre-release rings, and this should be going to GA shortly, followed by the same capabilities on Teams mobile.
- we added the new front of room text on SRS to highlight the new capabilities, but we screwed up in making the text static, and appear even when it was not applicable. We will be doing a "bug fix" in our Jan release to get rid of the text if: 1) BT beacon is turned off on SRS in settings and/or 2) Teams meetings are disabled on SRS. - @Torsten Siegmund we have not yet completed our certification testing on SP6; that is still in process. The SP5 / 2017 model should continue to be available for multiple months until SP6 is fully certified (which should hopefully happen soon). If you're having challenges getting systems with SP5 please reach out to me and/or @David Groom with the reseller and disti names / info?
- @Chris82 can you please let us know more details on the Lenovo Hub 500 fan noise issue? Are you hearing this only when projecting content to two Front of Room displays? Nothing should have changed otherwise for CPU usage and therefore fan load. So if the fan just started to become louder with a single FoR display there may be a HW issue.
Hope this helps, keep the feedback coming!
@David Groom - Thank you for the details - I was mistaken suggesting Mirrorcast - it was a mistaken assumption based on how the wireless display connectivity message on screen was interpreted.
@Ilya Bukshteyn - thank you as well for the details of the "patch/bug fix" option to take the notification off screen.
@Ilya BukshteynThe fan is only loud when projecting content to two Front of Room displays. If I switch to only one display, the fan noise is reduced. So, I would love to see an option to use two displays, but share content to only one of them.
@Chris82 do you hear a similarly loud fan noise from the Lenovo in the dual display room when in a meeting with video on one display and content on the other? I ask as dual content should use less CPU than video + content. I also use a Lenovo with dual displays in my project room and we have not observed this noise, but we will investigate further including your ask for a switch to disable dual content (I'm actually away from the office so can't check right now if we already have this in settings).
@Chris82 (and others as FYI) when you are doing local projection (not in a meeting) on a dual front of room system, you can touch the gear icon at the bottom right of the console to see an option to disable dual screen content.
I just updated from Windows 10 1703/app ver 188.8.131.52 to 1803/app 184.108.40.206, and I'm getting the error "You'll need a new program for this app skype-mrx:". I also tried running the recovery tool script from the current deployment toolkit. Any suggestions?
With the newest Build i got again an update notification in user mode. See the attached message. I'm wondering, where i can set the schedule for installing updates, i have never set anything for the srs either via GPO or manually. I would like to set it to a time space in the evening.
3 pm is a bad time to install updates....
Go to Windows Updates > Change Active Hours ... i have all of my SRS units active from 7am to 11pm
In our SRS installation we want to edit the SkypeSettings.xml under Localstate so that it always sets the right Audio Device.
But in our case we are using HP Slice G2 with Bang & Olufsen device and because of XML can't understand "&" we are not able to set it correctly.
Does anybody now how to set this with some escape character or something else?
Thanks for reply!
Could you please provide any update about the availability of the MSI?
In addition which is the best way to manage Logitech SmartDock device? Do you have a simple way to manage remotely?
SCCM or Intune?
@David Groom wrote:Skype Room Systems v2 220.127.116.11 update was released to the Store on December 14th. SRSv2 updates are released to 10% of devices with availability gradually increasing to 100% after a few days. December 19th Status Update: 18.104.22.168 now available to 100% of devices. 22.214.171.124 Release Notes- Display content on both Front of Room displays on dual screen systems.- Theming and Front of Room UI improvements An MSI version of this update is being prepared. This blog will be updated once it comes available.
@Andrea PALAZZI The Logitech SmartDock is a dock for a Surface Pro compute device, which in turn is a Windows 10 PC device. In this application WIndows 10 is simply locked down to a "kiosk mode" and our room systems application.Therefore you can manage this as you would any other Windows 10 PC, with SCCM, OMS, group policy, remote powershell, etc. We do have some documentation / best practices published for SCCM here:https://docs.microsoft.com/en-us/skypeforbusiness/deploy/deploy-clients/room-systems-scale We do have full cloud based management, based on Intune enrollment, coming a bit later this year as part of the Microsoft Teams admin portal. This would of course be only for room systems which you / the admin enable for Microsoft Teams.
Hope that helps!
@Ilya Bukshteynany update on the January fix for the text on the FOH display?
Hi @Jamesau, we have the fix checked in but are just working on a few other items (password rotation and TLS 1.2 support for example) for an app release. That may (will likely) take the release into Feb. Sorry about the delay, but hopefully the additional features will make the slight wait worthwhile.
when is the MSI going to be available?
@David Groom, when is our next MSI release to @Phil Bowden's question above?
@Phil Bowden - An MSI version of 126.96.36.199 will automatically be downloaded when you run the CreateSRSMedia script here.
@Phil Bowden the SRS Deployment Kit download link can be found in the CreateSRSMedia script Dave referenced above. It's currently pointing to the 188.8.131.52 package : https://go.microsoft.com/fwlink/?linkid=851168
Also, some readers of this blog have asked when to expect Modern Authentication support - current plan is to make Modern Auth available via an update sometime in the first half of 2019.
The meeting room worked fine on skype ver 184.108.40.206 and was updated to 220.127.116.11: January 3 They have had meetings after the update that has worked fine with some small problems like audio settings being reset.
But now that they are trying to host skype meeting, they appear in the plan on the surface and you get 1 second with the skype logo and the choice to join the meeting then disappears . If you press the meeting / booking we get a text bobble that says this is not a skype meeting. I have looked over the settings on the srs / skype room system and everything looks right. Seen if there has been any new update to the surfacen. It was a firmware update I have tried as well as gone into skype prog and tried to run windows repair on it. Is this something you have heard of/have had issues with?
The costumer have a surface pro 5 with win10 enterprise with build ver 1803
@Ricoh_Employe1172 sounds like you are seeing Skype for Business meetings scheduled with the room system appear on the console briefly, but then the SfB logo goes away and there is no longer an option to join because the room system thinks the meeting is not an online / SfB meeting?
None of the known updates should have caused this. We have only seen this when there is an issue with the meeting invite itself, such as SfB coordinates being cut and paste or otherwise corrupted. Another issue might be if the room system can't sign into SfB, in which case you should see a warning on the console about that.
I would suggest starting a support incident for us on this.
strange on this update . There's a few times that the call will not go thru . The user press join and the call will just loop back in home page and we can't connect. The only solution is to reboot the device . I will try to reinstall the OS on this and see how it goes.
@rodelmurex is that joining SfB meetings or Teams or both? We have not seen reports of this so if it persists please do log an incident with our support.
Release notes page shows TLS 1.2 support on this version, is that true?
@Nick DiFeo yes out client now supports TLS 1.2. If you're using SfB Server, there's a dependency on a new CU for server side support.
Today I ran the media creation script but the only MSI on the usb drive after was the Surface Drivers? The appx package was on there, but when running dism to inject it it did not update the version. Is there a minimum OS build needed? We are running all of our systems on 1709. I am having nothing but issues updating the Skype room app. We had to disable the store updates because the app kept on updating in the middle of meetings or becoming stuck at the two blue boxes on boot up. This is on all of our devices.
We are really frustrated at how convoluted such a simple task like updating an app can be with these units.
Hi, @Jonathan Orton. Did you download the latest ps1 script version available here? We updated the script over the weekend so a new version is available. Also, we're running on v1803 of Windows 10 now.
Thanks for your response @David Groom! I really appreciate it. I did find the .msi in the SCCM deployment article:https://docs.microsoft.com/en-us/skypeforbusiness/deploy/deploy-clients/room-systems-scale
I think going forward our org will just re-image the devices to update them. That seems like the easiest way (once I get the task sequence all ironed out)On a side note: we switched from a Lifesize solution to SRS units, and our end-users love the simplicity of the interface and the integration onto other MS products.For your developers: Please add the version number to the main interface, it is a pain have to enter admin creds to see the version the unit is on. Another great feature would be a update feature that can be run from the settings, something similar to how Chrome and FF update, go to Help>About> and click update, and have this feature have the ability to update even if the MS Store updates are disabled. As I mentioned in my previous post the MS Store updates interfere with scheduled meetings, and also hang the app on startup. Not what you want your CEO to experience when he has an important global meeting scheduled. Another thing our users have commented on is during a meeting the PIP (picture in picture) that displays the users room cam seems unnaturally small, and hard for user with sight impairments to tell if their camera is at the right zoom, and pointing at the right angel.
@Jonathan Orton Thanks for the kind words on the user feedback!We already know the feedback on the PIP and the version # and have roadmap items planned for H1CY19 to address this. We also have cloud-based device management in Microsoft Teams (in the cloud admin portal for Teams) and we are enabling that for MTR devices also in H1, including ability to control / trigger app updates. Thank you for the continued feedback!
@Chun Ming Yue MTR = Microsoft Teams Rooms = new (announced last week) name for SRS v2. There is no such thing as "Teams Room Systems" :) Yes we will be extending our cloud Teams device management to also work for MTR in H1 of this CY. As I've already said above, we will be addressing the front of room text in our next app release, targeted for this month.
The scheduled task "\Microsoft\Windows\WindowsUpdate\Automatic App Update" got moved in Win 10 1803, where is it now?
"Microsoft\Skype\NightlyReboot" just runs the automatic update task but it's not there.
@David Groom can you help with @Nick DiFeo 's question?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.