Home
%3CLINGO-SUB%20id%3D%22lingo-sub-177960%22%20slang%3D%22en-US%22%3ESkype%20Room%20Systems%20v2%20Troubleshooting%20Tips%20for%20Devices%20Automatically%20Upgraded%20to%20Win10%20Version%201709%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177960%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20of%20this%20writing%2C%20the%20Skype%20team%20has%20not%20yet%20lifted%20the%20Windows%2010%20Version%201709%20upgrade%20block%20on%20Skype%20Room%20Systems%20v2%20devices.%26nbsp%3B%20However%2C%20some%20customers%20have%20reported%20that%20they%20have%20nonetheless%20received%20the%20upgrade.%26nbsp%3B%20If%20your%20Skype%20Room%20Systems%20v2%20device%20is%20upgraded%20to%20Windows%20version%201709%20and%20you%20are%20experiencing%20device%20issues%2C%20please%20try%20performing%20the%20following%20device%20reset%20procedure%20to%20remediate%20the%20problem%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EConfirm%20Windows%20Version%20by%20running%20the%20command%20winver.exe.%26nbsp%3B%20The%20script%20used%20below%20will%20not%20run%20on%20builds%20earlier%20than%20Version%201709.%3C%2FLI%3E%0A%3CLI%3ELog%20in%20as%20admin.%26nbsp%3B%20Download%20the%20latest%20SRS%20v2%20installation%20package%20--%20%3CA%20href%3D%22https%3A%2F%2Fna01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fgo.microsoft.com%252Ffwlink%252F%253Flinkid%253D851168%26amp%3Bdata%3D04%257C01%257C%257C785e2533c3ee467ab4ea08d5967531d2%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636580352434526129%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%253D%253D%257C-1%26amp%3Bsdata%3Dp8kMoQ5vgFsvGmfHSxunDsz6VlbzTnPW%252B8umETR0OGs%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EUnpack%20contents%20of%20the%20installation%20package%20and%20copy%20to%20Skype%20Room%20System%20v2%20device.%3C%2FLI%3E%0A%3CLI%3ELaunch%20powershell%20as%20admin%3C%2FLI%3E%0A%3CLI%3EChange%20to%20the%20directory%20that%20contains%20the%20ResetTool%20script.%3C%2FLI%3E%0A%3CLI%3ERun%20the%20following%20command%20in%20PowerShell%3A%20%22powershell.exe%20-executionpolicy%20unrestricted%20.%5CResetTool.ps1%22%20and%20follow%20the%20instructions%20in%20the%20cmd%20window%20to%20reset%20the%20device.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%20%3CSTRONG%3ENOTE%3C%2FSTRONG%3E%3A%20This%20action%20will%20migrate%20your%20SRS%20v2%20device%20to%20the%20new%20provisioning%20and%20install%20SRS%20v2%20application%20Build%203.1.100.0.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20script%20will%20prompt%20you%20to%20run%20Windows%20Reset%20when%20complete.%20Run%20Windows%20Reset%20from%20the%20Settings%20%26gt%3B%20Update%20%26amp%3B%20Security%20%26gt%3B%20Recovery%20%26gt%3B%20Reset%20this%20PC.%26nbsp%3B%20Be%20sure%20to%20choose%20the%20%22Remove%20everything%22%20option.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3CSTRONG%3ENOTE%3C%2FSTRONG%3E%3A%20Some%20SRS%20v2%20devices%2C%20such%20as%20the%20Lenovo%20Hub500%2C%20ship%20with%20Windows%2010%20Version%201709%20included%20in%20the%20baseline%20image.%26nbsp%3B%20In%20these%20cases%2C%20running%20the%20script%20is%20likely%20unnecessary.%26nbsp%3B%20The%20instructions%20above%20apply%20to%20devices%20baselined%20on%20Windows%2010%20Version%201703.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-177960%22%20slang%3D%22en-US%22%3E%3CP%3EEncountering%20issues%20after%20your%20SRS%20v2%20device%20has%20been%20automatically%20upgraded%20to%20Windows%2010%20Version%201709%3F%26nbsp%3B%20Run%20this%20downloadable%20script%20to%20address%20issues%20that%20you%20may%20be%20experiencing.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-177960%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeployment%20%26amp%3B%20Operations%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDevices%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EQuality%20%26amp%3B%20Reliability%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESkype%20for%20Business%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-212813%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20Systems%20v2%20Troubleshooting%20Tips%20for%20Devices%20Automatically%20Upgraded%20to%20Win10%20Version%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-212813%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F30420%22%20target%3D%22_blank%22%3E%40Jed%20Ellerby%3C%2FA%3E%26nbsp%3B%20Yeah%2C%20it's%20confusing.%20As%20far%20as%20I%20know%20it%20hasn't%20been%20approved%20yet.%20The%20%22fixing%20issues%22%20message%20is%20what%20the%20block%20has%20always%20looked%20like%20for%20me.%201709%20is%20required%20for%20people%20who%20create%20their%20own%20image%20with%20the%20deployment%20toolkit.%20There%20were%20also%20people%20who%20were%20stuck%20on%201607%20and%20had%20no%20way%20to%20update%20to%201703%2C%20so%20they%20were%20told%20to%20update%20to%201709%20and%20use%20the%20recovery%20tool%20script.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-212390%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20Systems%20v2%20Troubleshooting%20Tips%20for%20Devices%20Automatically%20Upgraded%20to%20Win10%20Version%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-212390%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20looks%20to%20me%20like%201709%20me%20was%20certified%20a%20little%20while%20ago%2C%20as%203.1.104%20refers%20to%20fixing%20issues%20for%201709.%20What's%20not%20clear%20to%20me%20is%20when%201709%20is%20expected%20to%20be%20applied%20to%20an%20SRS%20(using%20Windows%20Update)%20and%20also%20whether%20it%20will%20be%20successful%20or%20not.%20There%20are%20too%20many%20different%20threads%20referencing%201709%20issues%20to%20really%20know%20the%20status.%20We%20have%20SRS%20in%20a%20mixture%20of%20%221703%2F1709%20deployed%2F1709%20tying%20to%20deploy%20states%22%20so%20it%20would%20be%20good%20to%20know%20if%20it%20is%20expected%20to%20deploy%20without%20issue%20now%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-211872%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20Systems%20v2%20Troubleshooting%20Tips%20for%20Devices%20Automatically%20Upgraded%20to%20Win10%20Version%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-211872%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54558%22%20target%3D%22_blank%22%3E%40David%20Groom%3C%2FA%3Ehas%20the%20status%20on%20this%20changed%20recently%20as%20our%20lab%20SRS%20has%20upgraded%20successfully%20to%201709%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181397%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20Systems%20v2%20Troubleshooting%20Tips%20for%20Devices%20Automatically%20Upgraded%20to%20Win10%20Version%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181397%22%20slang%3D%22en-US%22%3E%3CP%3ERan%20the%20update.%26nbsp%3B%20Worked%20fine.%26nbsp%3B%20My%20question%20is%20why%20did%20my%201703%20SRS%20device%20update%20to%201709%20when%20I've%20read%20articles%20that%20it%20shouldn't%3F%26nbsp%3B%20Why%20can't%20MS%20Update%20detect%20a%20SRS%20device%2C%20download%20this%20SRS%20software%20update%2C%20and%20install%20it%20before%20it%20updates%20to%201709%2C%20thereby%20preventing%20the%20downtime%3F%26nbsp%3B%20(edit%3A%20After%20running%20the%20script%20and%20resetting%20the%20device%2C%20the%20downtime%20is%20about%2032%20min.%20not%20including%20set%20up%20of%20the%20device%20after%20reset)%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-179256%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20Systems%20v2%20Troubleshooting%20Tips%20for%20Devices%20Automatically%20Upgraded%20to%20Win10%20Version%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179256%22%20slang%3D%22en-US%22%3E%3CP%3ESince%201803%20is%20due%20out%20this%20month%2C%20don't%20you%20think%20that%20there%20should%20be%20an%20actual%20plan%20to%20support%20Skype%20Rooms%20on%201709%3F%26nbsp%3B%20I%20mean%2C%20is%20this%20product%20even%20in%20Microsoft's%20supported%20strategy%3F%26nbsp%3B%20It%20doesn't%20seem%20like%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178972%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20Systems%20v2%20Troubleshooting%20Tips%20for%20Devices%20Automatically%20Upgraded%20to%20Win10%20Version%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178972%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20done%20this%20today%2C%20but%20it's%20a%20major%20pain%20in%20the%20a**.%20I'm%20not%20sure%20if%20reinstalling%20the%20device%20is%20faster%2C%20than%20doing%20the%20whole%20procedure%20with%20resetting%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178087%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20Systems%20v2%20Troubleshooting%20Tips%20for%20Devices%20Automatically%20Upgraded%20to%20Win10%20Version%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178087%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20will%20try%20this%20out%20on%20Tuesday..%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

As of this writing, the Skype team has not yet lifted the Windows 10 Version 1709 upgrade block on Skype Room Systems v2 devices.  However, some customers have reported that they have nonetheless received the upgrade.  If your Skype Room Systems v2 device is upgraded to Windows version 1709 and you are experiencing device issues, please try performing the following device reset procedure to remediate the problem:

 

  • Confirm Windows Version by running the command winver.exe.  The script used below will not run on builds earlier than Version 1709.
  • Log in as admin.  Download the latest SRS v2 installation package -- here
  • Unpack contents of the installation package and copy to Skype Room System v2 device.
  • Launch powershell as admin
  • Change to the directory that contains the ResetTool script.
  • Run the following command in PowerShell: "powershell.exe -executionpolicy unrestricted .\ResetTool.ps1" and follow the instructions in the cmd window to reset the device.

             NOTE: This action will migrate your SRS v2 device to the new provisioning and install SRS v2 application Build 3.1.100.0.

 

  • The script will prompt you to run Windows Reset when complete. Run Windows Reset from the Settings > Update & Security > Recovery > Reset this PC.  Be sure to choose the "Remove everything" option.

            NOTE: Some SRS v2 devices, such as the Lenovo Hub500, ship with Windows 10 Version 1709 included in the baseline image.  In these cases, running the script is likely unnecessary.  The instructions above apply to devices baselined on Windows 10 Version 1703.

7 Comments
Frequent Contributor

We will try this out on Tuesday..

Frequent Contributor

Have done this today, but it's a major pain in the a**. I'm not sure if reinstalling the device is faster, than doing the whole procedure with resetting etc.

Occasional Visitor

Since 1803 is due out this month, don't you think that there should be an actual plan to support Skype Rooms on 1709?  I mean, is this product even in Microsoft's supported strategy?  It doesn't seem like it.

Regular Visitor

Ran the update.  Worked fine.  My question is why did my 1703 SRS device update to 1709 when I've read articles that it shouldn't?  Why can't MS Update detect a SRS device, download this SRS software update, and install it before it updates to 1709, thereby preventing the downtime?  (edit: After running the script and resetting the device, the downtime is about 32 min. not including set up of the device after reset) 

Occasional Contributor

@David Groomhas the status on this changed recently as our lab SRS has upgraded successfully to 1709? 

Occasional Contributor

It looks to me like 1709 me was certified a little while ago, as 3.1.104 refers to fixing issues for 1709. What's not clear to me is when 1709 is expected to be applied to an SRS (using Windows Update) and also whether it will be successful or not. There are too many different threads referencing 1709 issues to really know the status. We have SRS in a mixture of "1703/1709 deployed/1709 tying to deploy states" so it would be good to know if it is expected to deploy without issue now?

New Contributor

@Jed Ellerby  Yeah, it's confusing. As far as I know it hasn't been approved yet. The "fixing issues" message is what the block has always looked like for me. 1709 is required for people who create their own image with the deployment toolkit. There were also people who were stuck on 1607 and had no way to update to 1703, so they were told to update to 1709 and use the recovery tool script.