Jan 26 2017 03:33 AM
So we just installed a Skype Room Systems v2 (Logitech Group) in our largest conference room. Here are our first impressions when it comes to the software. We have Exchange 2016 on-premise and SfB Online in O365.
Then there are some minor Logitech hardware first impressions but that's not related to Microsoft.
Aug 03 2017 12:41 AM
@David Phillips wrote:"Windows 10 Enterprise Creators Update (build 1703) is not supported for Skype Room Systems v2 image creation."
Hope that changes soon...
Yes. In the meanwhile - turn OFF automatic updates or your on-screen-keyboard will stop working.
Aug 03 2017 07:09 AM
Aug 09 2017 07:35 AM
Just wanted to share the issues we faced in our organisation as this could be useful for others:
1. It is not possible to capture the image with SRS application. We need that in order to deploy the image via SCCM. If you follow the instructions in this KB - https://technet.microsoft.com/en-us/library/mt790558.aspx you will be able to install Win 10 and SRS application, but you won't be able to capture that image - resulting image will not have SRS application. We have support ticket opened for that since the end of June and no progress so far
2. The only option to get SRS application updates is Windows Store. There is no standalone msi package. The package in this KB - https://technet.microsoft.com/en-us/library/mt790558.aspx is not a SRS application - it is a set of files for image deployment actually. Again if you want to deploy new SRS application via SCCM you can't do that.
3. Microsoft Premier Support has no idea what is Skype Room System. Every time you open a ticket you will have to explain that this is Surface Pro device and that Microsoft develops SRS software for it. Then you ticket will go back and forth between different Microsoft team as (again!) they have no idea what SRS is.
4. Microsoft just announced that Surface Pro 4 is not available, while Surface Pro 5 will become available in the end of September only. If you want to purchase SRS now you can't do that!
Aug 09 2017 07:47 AM
SRS app 3.0.8.0 was released recently - https://techcommunity.microsoft.com/t5/Skype-for-Business-Blog/Skype-Room-Systems-v2-3-0-8-0-Update/...
Aug 09 2017 08:15 AM
Aug 09 2017 08:25 AM
Hi Christophe,
we have not faced that issue as we didn't apply Creator's update. I suggest that you turn off automatic updates and deploy security updates only to SRS.
Aug 09 2017 09:08 AM
Hi Pavel,
What happens when you try to install the Skype Room System app using ConfigMgr?
The installation file is located in the folder \$oem$\$1\Rigel\x64\Ship\AppPackages\SkypeRoomSystem after you have extracted the MSI from https://go.microsoft.com/fwlink/?linkid=851168
Then you should be able to do something like Exercise 1 in this guide, https://blogs.technet.microsoft.com/keithmayer/2013/02/25/step-by-step-deploying-windows-8-apps-with...
Any luck with that?
Aug 10 2017 12:15 AM
Hi Erik,
The install from that folder \$oem$\$1\Rigel\x64\Ship\AppPackages\SkypeRoomSystem didn't work. Did you try to install it? Was it successful?
I am also wondering if anyone else tried to capture SRS image for further distribution within a large enterprise?
Aug 10 2017 02:57 AM
Hello Roman,
I fully agreed about the need to have a package and a more integrated entreprise solution. I would like the Windows updates without having impact on the SRS2 application and the MSI package available to redeploy anytime instead of a hving to go to the MS store app to get the latest version.
For a masse deployment of 600 rooms you can't afford to restage even 20% of your SRS2 if you get a wrong windows update or a need to update to the latest version due to a bug of federated contacts.
I really appreciate the schedule of updates for the support of the SRS2 but this needs to be stabilized, communication about the roadmap, and support .
Aug 10 2017 03:06 AM
Hello Pavel,
Surface Pro new generation could be very interesting with the fanless mode, i noticed the SRS2 was really using the fan during a call. We didn't invest in one yet.
Did you try to get the boot on PXE with the USB image and automate the last steps of the installation ?
Aug 10 2017 04:24 AM
Hello Christophe!
So far, we tried OSD with PXE and Stand-Alone media.
What exactly you mean wen you say about last steps automation?
Actually, we're working with Pavel together on this project.
So far we made many attempts to make SRS "somehow" ready for enterprise deployment through SCCM, but no luck yet.
Please find a few highlights below:
1) We captured reference Image with SRS application already installed. After deployment OS from this Image, the OS itself, CM Client, Domain Join and Windows activation are working smoothly, but SRS application just disappears from the Image. We still have source files in FS at C:\Rigel.
2) We tried to use these source files to restore the app.
We ran InstallSkype.ps1 script - no luck.
We tried with full installation by Config.cmd script - no luck.
After system restart we still see there is no SRS application. I guess this is because the installation scripts identifies that SRS is already installed (may be according to reg keys or files/folders in FS).
3) We cannot plan normal product lifecycle with SCCM (without Windows Store). Unfortunately, there is no MSI/EXE available when MS updates app in Windows Store.
4) When I observed SRS source scripts, I couls see that installation is aimed mostly for local account "Skype". I really like how this local account works for end user. (You only have SRS Interface and nothing more. No credential prompt, no possibility to do something wrong.)
Ideally would be nice to have installer which prompts for account name and install/configure SRS in the same way as for Skype.
Our next step - deploy clean Win10 on a Surface and try to install SRS manually with scripts, but this not ideal solution. We would not like to make reverse-engineering each time where there is an update :)
Aug 10 2017 06:55 AM
we got today update 3.10.0 but not aware of improvements inside.
And still we have some issue with the sharing second screen
Aug 10 2017 10:44 AM
Aug 13 2017 01:45 PM
Sep 08 2017 07:16 PM
hi Ivar,
was all you did literally just set the "Dual Monitor Mode" from OFF to ON? and the not-displaying-on-screen issue was resolved? 'cuz i've tried that but it still doesn't work. :(
But as you can see, the SRS is very much recognizing the 2nd monitor, as it's got windows background pushed to it. Grrr...
Thanks a ton in advance,
-chuck
Sep 09 2017 01:03 AM - edited Sep 09 2017 02:45 AM
Just deployed our first SRS pilot installations in meeting rooms using Logitech kit.
I was naïve enough to use the unattended installation from TechNet article 790558 without modifications for this pilot and learned the hard way that auto-update is enabled in this setup, so an upgrade to version 1703 eventually happened.
After this I have received a report from a user who experience a "partial picture" when using the HDMI input, and the behaviour seems to be very much like Christophes example.
I presume CU is still "not supported" for SRS so I will revert to 1607 on one of the units to cross-check this.
I production we plan to monitor with OMS and manage the deployment through Intune, so we can defer future feature updates until they are approved.