Forum Discussion
Skype Room Systems v2 - first impressions
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.
When looking trough the settings I found that one registry key got reset:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TabletTip\1.7\EnableDesktopModeAutoInvoke
When resetting this to the same value as configured in the scripts in the Skype Room System Deployment Kit and then restarting the device the touch screen keyboard started to work again.
Set-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\TabletTip\1.7 -Name EnableDesktopModeAutoInvoke -Value 1 -Type DWord
Hope this might help anyone who got the same issue as me.
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!
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 ?
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 :)
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-system-center-2012-service-pack-1-migration-and-deployment-series-part-16-of-19/
Any luck with that?
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?
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/ba-p/94093
- Hello Pavel,
We face a annoying issue with windows creator udpate with 2 screens, second screen sharing is zoomed in and show part of the source HDMI and half of the secondary view screen, it's really weird and looks related to the improvement made for this creator version. Any idea about this bug fix lilke the virtual keyboard reg fix ?
It's bit stressful to not apply the windows updates as we don't the impact on the SRS application...
