Home
Microsoft

Skype Room Systems v2 3.0.12.0 Update

Skype Room Systems v2 Build 3.0.12.0 has been available from the Microsoft Store since late last week.  Build 3.0.12.0 allows IT Pros to build Windows 10 RS2-based images for the new Surface Pro. The standalone MSI is linked for download from the "Prepare the installation image" article on Technet here.

 

This update also addresses some cropping issues observed during outgoing screen scharing.

48 Comments
Contributor

Any information on what is new with the release. I did install it today but can't see any visible difference, is it only bugfixes ?
Also worth mentioning the change of Anniversary / Creators update supportability. As far as I can tell 3.0.12.0 is only supported with Creators update?

Support for Creators Update and Surface Pro in the dock (beyond current Surface Pro 4 support). The 64-bit version of Windows 10 Enterprise Anniversary edition (English language, version 1607) is no longer supported as of Skype Room Systems v2 release 3.0.12.0.  See the latest Skype Room Systems v2 requirements article here: https://technet.microsoft.com/en-us/library/mt790552.aspx

Contributor

I upgraded the Store app and then upgraded Windows to 1703 and now my Surface/Smart Dock is broken. When I power on I get:

 

skype-mrx://

invalid value for registry

 

nothing loads, I can even open the start menu - have to hold down the power button

Occasional Contributor

Can't tell when my unit updated, but it is now on 3.0.12. I have been doing daily reboots every morning, so I guess tomorrow morning will show if this did the trick or not. So far a reboot in the morning (with TV turned on) keeps the system working fine. If I do not do that reboot, it will not work in the mornings as previously discussed. Gosh, such a great system and such a stupid software bug. Can't be that hard to fix as it worked in version 2.

Microsoft

@Trent Queen - Did you manually update the app?  Or did it automatically update?

Occasional Contributor

It auto-updated. Did not have a chance to check event logs to see when it happened.

Microsoft
@Christoph Puetz Display doesn't work after turning back on, is a known issue and we are investigating it for a fix.
Occasional Contributor

@Kiran Kodali Thank you for acknolwedgement and the hard work on this. It is appreciated. If you need a tester - please reach out to me. More than happy to help. 

Contributor

@David Groom - I logged in to the Admin account to go and update the app it showed "updated moments ago" and the version matched.

Occasional Contributor

I also have the issue with not starting the app after it has updated. I run an old install image with a 1.x version of the app and an older Win 10 version. I know i should update but it has been working so far and it used to simply update overnight without issues. Now when i install the old app and update Win and App then i get the error:

 

skype-mrx://

invalid value for registry

 

Anyone who found a fix for this?

Regular Visitor

@Fredrik Åsvik and @Trent Queen Hey try the following.

from Skype run cmd as administrator, and run start skype-mrx: and restart the computer

Contributor

I can't access cmd from the Skype account, as I said it locks up and I can't do anything.

Occasional Contributor

Trent, you can access cmd from the Skype account by right clicking the start button. You need a mouse connected. 

 

However, nothing happens when i run that command. Found it in another forum and already tested that. Didnt do anything. 

 

What i did now was to rebuild my USB device which i use for the install with the new drivers and creators update and then everything seems to work. I believe it has to do with this statement from the Technet article:

 

"Windows 10 Enterprise Anniversary Update (Version 1607) is no longer supported for Skype Room Systems v2 image creation."

 

 

 

Completly off-topic but should i be able to use this community with IE, for me that doesnt work at all...

Contributor

According to the last requirements you need a TV supporting CEC

https://technet.microsoft.com/en-us/library/mt790552.aspx

A consumer TV used as a front of room display needs to support/enable the Consumer Electronics Control (CEC) feature of HDMI so that it can switch automatically to an active video source from standby mode. This feature is not supported on all TVs.

Occasional Contributor

These are high-end TVs, so that this is not the problem - especially as it worked fine before the upgrade to version 3.

New Contributor

@Christoph Puetz, @Trent Queen Do you have still problem with SRSv2 stability? My system is working correctly for 3 days in row and I am surprised.

Occasional Contributor

v2 was never a problem. The upgrade to v3 made it go bad and we do not have a way back to v2.

New Contributor

Our system is SRSv2 release 3.0.10.0 (update 3). I didnt hear about SRSv3.

Contributor

@Kiran Kodali Is it only 3.0.12.0 version affected by this? I would really appreciate a public "known issues" list. That would spare customers lots of time. 

Microsoft

@Markus Johansson Team is working on updates that will resolve these skype-mrx issues. We will let you know soon.

Contributor

@Kiran Kodali Thanks good to know, but I was more referring to issues with the loss of external monitors. Is there an known issue for the SP4 to extend its display? 

Regular Visitor

Just another input.  We have Logitech SmartDock and it updated to 1703 and v 3.0.12.  Getting the

skype-mrx://

Invalid value for registry

 

However; if I disable the auto logon, login as myself (domain admin) to the system, and run start skype-mrx: it opens the screen and let me start entering config info.  This makes it look like some permissions issue.   I have made the local account (.\Skype) a local administrator but still have the same invalid registry error.

 

Any ideas?  I know @Kiran Kodali  said MS is working on a fix...

 

 

.

 

 

 

 

Regular Visitor

My organization just received 5 smart docks from logitech 2 weeks ago. I went through the initial setup and decided to not join these to our domain, at least for now. I setup a local account and updated Windows 10 to the creators update...build 1703. It came pre installed with the Skype for Business(Skype Room System V3.0.12.0). Because I set it up this way I did not see the issue you are all seeing. If I sign on using the pre built "Skype" user account I get that same error everyone else does "skype-mrx:// Invalid value for registry".

 

When I login to the local user I created I can run Skype room system just fine, I tested it with remote locations, it views our directory just fine. The issue I have is it shows a warning "Cannot fetch calendar", thus it does not show the meetings it has been invited to. In my outlook on my laptop I can send out the meeting invites and I receive a reply saying the room accepted the meeting. They just don't show in the skype room system default menu/interface. Other than that everything works well, I can call out, invite people to a new meeting just fine.

 

Does anyone else have that "Cannot fetch calendar" issue? @Steve Burk Since you can login using your admin acount and run Skype do you see this issue?

Regular Visitor

I have not seen the cannot fetch calendar issue.  Just waiting on a fix for the registry before I try anything else.

Senior Member

@Marco Vindell

 

I have the same issue, I have skype on prem and exchange in o365, tried everything suggested, Did you find anything that worked?

New Contributor

We have seen occational skype-mrx:// problems after installing 1703.

I solved that by connecting a mouse and keyboard to the Logitech Dock. Then right-click on Start (lower left corner). And then start cmd as Admin.

Then I start Regedit and change the Autologin key from 1 to 0 (HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon AdminAutoLogon = (dword) 0).

Then "Shutdown -r" to reboot the system. When the system is rebooted I can login as .\Admin and the launch the Skype app.

When I get the error as Admin I can launch the Store app and reinstall the Skype app from there. Once reinstalled I can start it as Admin.

Then revert the Registry key and login as .\Skype and the Skype-App is working again.

Regular Visitor

@Philip Brindley No,  I still have the same issue. We have exerything in the cloud, nothing on premises. What is weird is I try a room account that was created before my company moved to the cloud and that account works! My user account also works, they fetch the calendar just fine. Then I login to one of the newly created(created about a month ago) room accounts and I get that error again. I opened up a support ticket with Microsoft's skype for business team, they are on day 3 of troubleshooting this and they seem to be stumped. I just got off the phone with them, they were remoted in to my tablet and saw the issue first hand. The location where the log files should be doesn't exist so he is going to his superiors with the case. I compared the old room account with one of the new ones, they have the exact same product licneses and mail/skype for business attributes. I hope their next level engineers can help.

 

I will let you know if they or I find a solution, please update me if you do as well!

Senior Member

@Marco Vindell 

I will of course let you know if I find anything out!  I provisioned all of mine in the cloud, even though i have hybrid, as im trying to decomission the on prem. Ive tried lots of diff configs, srsv1 thru to 3 , win10 , win10 creators, any combination i can think off and still get that error. My logs also dont seem to exist so im the same boat as you with that.

I read something about migrating the room box back to on prem, then up into the cloud again. ill try it tomorrow i think. i've finished for today :D

Regular Visitor

I am also getting the same error as everyone else does "skype-mrx:// Invalid value for registry"... Still looking for resolution

Contributor

@Kienan Leung hello try the following working fine for me all the time.

1. Press and hold  the windows flag until menu appears (done from Skype account login failure session)

2. Choose "run cmd as administrator"

3. from cmd type "start skype-mrx:" + enter

4. SRS UWP app will launch

5. Restart the SRS from the application

6. Auto login with skype account will auto launch SRS UWP app

 

good luck

 

Frequent Visitor

Hi 

Our company recently migrated to Skype for Business - Cloud PBX and we wanted to install Skype Room System to one of our Surface Pro 3, i5, 4GB ram.  I have followed the instructions to deploy from https://technet.microsoft.com/en-us/library/mt790558.aspx#Prepare the installation image and used the following codes for the AutoUnattend.xml

 

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <servicing>
        <package action="configure">
            <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="10.0.15063.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" />
            <selection name="Client-DeviceLockdown" state="true" />
            <selection name="Client-EmbeddedLogon" state="true" />
            <selection name="Client-EmbeddedBootExp" state="true" />
            <selection name="Client-EmbeddedShellLauncher" state="true" />
            <selection name="Client-KeyboardFilter" state="true" />
            <selection name="Internet-Explorer-Optional-amd64" state="false" />
            <selection name="MediaPlayback" state="false" />
            <selection name="WindowsMediaPlayer" state="false" />
            <selection name="Xps-Foundation-Xps-Viewer" state="false" />
            <selection name="WorkFolders-Client" state="false" />
            <selection name="SMB1Protocol" state="false" />
            <selection name="SearchEngine-Client-Package" state="false" />
            <selection name="Printing-Foundation-Features" state="false" />
            <selection name="FaxServicesClientPackage" state="false" />
            <selection name="Printing-Foundation-InternetPrinting-Client" state="false" />
            <selection name="Printing-XPSServices-Features" state="false" />
            <selection name="Printing-PrintToPDFServices-Features" state="false" />
            <selection name="Microsoft-Hyper-V-Hypervisor" state="true" />
            <selection name="Microsoft-Hyper-V-All" state="true" />
            <selection name="Microsoft-Hyper-V" state="true" />
        </package>
    </servicing>
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <UserData>
                <!-- OEMs uncomment this section -->
                <ProductKey>
                    <WillShowUI>OnError</WillShowUI>
                    <Key>NJMFF-TXKRR-VG2JY-KMV92-FX8WP</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
            </UserData>
            <DiskConfiguration>
                <Disk wcm:action="add">
                    <CreatePartitions>
                        <CreatePartition wcm:action="add">
                            <Order>1</Order>
                            <Size>300</Size>
                            <Type>EFI</Type>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>2</Order>
                            <Extend>true</Extend>
                            <Type>Primary</Type>
                        </CreatePartition>
                    </CreatePartitions>
                    <DiskID>0</DiskID>
                    <WillWipeDisk>true</WillWipeDisk>
                </Disk>
                <WillShowUI>OnError</WillShowUI>
            </DiskConfiguration>
            <ImageInstall>
                <OSImage>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>2</PartitionID>
                    </InstallTo>
                    <WillShowUI>OnError</WillShowUI>
                </OSImage>
            </ImageInstall>
            <UseConfigurationSet>true</UseConfigurationSet>
        </component>
        <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SetupUILanguage>
                <UILanguage>en-US</UILanguage>
            </SetupUILanguage>
            <UILanguage>en-US</UILanguage>
        </component>
    </settings>
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DriverPaths>
                <PathAndCredentials wcm:keyValue="8822ed14" wcm:action="add">
                    <Path>%configsetroot%\AutoUnattend_Files\DistShare\Out-of-Box Drivers</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Embedded-BootExp" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DisableBootMenu>1</DisableBootMenu>
            <DisplayDisabled>1</DisplayDisabled>
        </component>
        <component name="Microsoft-Windows-powercpl" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <PreferredPlan>8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c</PreferredPlan>
        </component>
    </settings>
    <settings pass="auditSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <AutoLogon>
                <Enabled>true</Enabled>
                <Username>Admin</Username>
                <Password>
                    <Value>cwBmAGIAUABhAHMAcwB3AG8AcgBkAA==</Value>
                    <PlainText>false</PlainText>
                </Password>
            </AutoLogon>
            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>cwBmAGIAUABhAHMAcwB3AG8AcgBkAA==</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Name>Admin</Name>
                        <Group>Administrators</Group>
                        <DisplayName>Administrator</DisplayName>
                        <Description>Administrator</Description>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
        </component>
    </settings>
    <settings pass="auditUser">
        <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>net user Skype &quot;&quot; /add /expires:never /passwordchg:no /passwordreq:no</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>net localgroup Users Skype /add</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>3</Order>
                    <!-- Select only ONE Path section below for use. -->
                    <!-- Ensure it is uncommented, and that all the Path sections you are not using are commented out. -->
                    <!-- Stage to allow the capture of a reference image -->
                    <Path>%SystemRoot%\System32\Sysprep\Sysprep.exe /generalize /oobe /shutdown /unattend:%SystemDrive%\Rigel\x64\Scripts\Provisioning\audit.xml</Path>
                    <!-- Create a single unit to go live (default) -->
                    <!--<Path>%SystemRoot%\System32\Sysprep\Sysprep.exe /generalize /oobe /reboot /unattend:%SystemDrive%\Rigel\x64\Scripts\Provisioning\audit.xml</Path> -->
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OOBE>
                <HideEULAPage>false</HideEULAPage>
            </OOBE>
        </component>
        <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <Reseal>
                <Mode>Audit</Mode>
                <ForceShutdownNow>false</ForceShutdownNow>
            </Reseal>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:h:/install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

 

However the installation does not proceed and I and prompting me that there is image to proceed.  I am not sure if I am doing something wrong or SRS is not supported for Surface Pro 3.  I would really appreciate if someone would be able to help.


David Groom wrote:

Skype Room Systems v2 Build 3.0.12.0 has been available from the Microsoft Store since late last week.  Build 3.0.12.0 allows IT Pros to build Windows 10 RS2-based images for the new Surface Pro. The standalone MSI is linked for download from the "Prepare the installation image" article on Technet here.

 

This update also addresses some cropping issues observed during outgoing screen scharing.


 

Hello, Sandro,

 

You will need a Surface Pro 4 or newer to get the SRSv2 solution to work.

 

Here is the latest on SRSv2 requirements:

https://technet.microsoft.com/en-us/library/mt790552.aspx

Senior Member

@Marco Vindell

 

for a brief moment today it worked, it managed to get the calander, then went back to cannot fetch, I'm sure this is an office365 problem, i think the ms backend is so unreliable that it cannot connect in a reasonable amount of time, If i open the account in owa and click on the calender it takes a full 30secs to open up, this morning when the SRS could get the info that same process was happening in a few seconds. I've ran the system on our network and on an isolated network/internet line to remove all possibilities of congestion, even used a 4g dongle and the behaviour was the same, the 30mins of it working, it worked on all setups, and now its broken on all! :(

 

Have you had any joy yet from your open ticket? im waiting for someone to get back to me on mine atm

Regular Visitor

@Philip Brindley I was away on PTO on Friday and just back in the office today. They requested the accounts that this is happening on for me on Friday and I supplied it to them. No word back yet but I will request a call back for this afternoon. One thing I know for sure is that the surface pro requires you to be on your internal network. Initilaly I had them connected to a guest network but after speaking to my colleagues they suggested connecting them to our corporate internal network. It didn't change anything on the new room accounts that cannot fetch, but it did affect the old acounts that do work. With the old accounts on a guest network it could not fetch the calendar, when on our internal wireless it worked just fine. It's weird because we are 100% in the cloud now, but it still needs our internal DNS servers and connection to AD I guess?

 

We have 5 new room accounts, the old room account that is working in another site is listed as "Synched with Active Directory"(in the O365 admin center), because it was created pre-move to O365. While all new accounts are listed as "In cloud", so I created a new user account and specified the email address in our internal AD to test. After forcing a dirsync and waiting like 5 minutes it showed in O365 admin center that it was "Synched with Active Directory". Unfortunately this had no effect on the fetching of the calendar. This was done last Thursday.

 

update: It seems they are escalating my case to a higher level.

Frequent Visitor
Hi Nicholas Dambrosio Thank you for your reply and the information. I am now trying to install the SRS V2 on our Surface Pro 4, i5, 4GB memory using the same USB disk which I have prepared before. However I am still getting the error "No images available" and could not proceed with the installation. Is there any other instructions where i can follow to create the windows image? Thanks
Senior Member

@Marco Vindell  I got mine working, my final working config was to create the user account in the cloud, not in active directory. Why this works seems to be that the incloud account is not subject to two factor authentication like my domain accounts.  The one brief moment where it worked with an AD generated account is probably down to when i logged into the srs under the room account and accessed OWA, then fired up the app. This fullfilled our 2FA requirements. Running it as the \skype account and using the room creds in the app just doesnt clear 2FA.

 

Maybe you have 2 form auth in place as well?

Frequent Visitor

@Marco Vindell, I was able to completely install the SRSv2 on SP4 and can i confirm with you that the setup configuration will not push through not unless there is no dock? 

Microsoft

@Sandro Saberon The SP4 must be assembled in a certified SRS v2 dock in order for the SRS v2 application to launch successfully.  Certified docks and other hardware can be found here.  

Regular Visitor

@Philip Brindley The 5 room accounts I mentioned were all created in the cloud to start with. I only made an AD account for one of those accounts while I was troubleshooting. Can you please state your entire setup like mine below:

 

Logitech smartdock system using MS Surface Pro 4

Windows 10 with latest updates including build 1703 "creators update"

SRS v3.0.12.0

Accounts created in the cloud

Login to the surface pro using a locally created user account(my account matches the name of the room)

connected to internal network

 

I checked and they are not subject to two factor auth. I also even logged into O365 on the surface pro and then launched skype and same thing...cannot fetch calendar.

Senior Member

@Marco Vindell

 

Logitech smart dock system , Surface pro 4

windows 1703 + latest updates SRS v3.0.12.0 , installer image made from that, as per 

https://technet.microsoft.com/en-us/library/mt790558.aspx#Prepare the installation image

 

The user account was created in the cloud, not in AD. E2 plan assigned and the commands ran to convert to a room.

Login to the pro using the baked in Skype account.

Certificates installed or machine added to the domain (both of these configs worked for me, i opted to domain join it)

Login to the cloud exchange account using skyperoom@********.onmicrosoft.com , skype login skyperoom@mydomain.com

Connected to internal network/external network, both configs worked for me.

 

Hope that helps

Regular Visitor

@Philip Brindley

Thanks but that doesn't help me... I didn't make an installer image because my surface pro came with 3.0.12.0 already, I just updated windows to 1703 myself before doing anything in SRS. Our plan is E1 which I know E1 works because we have an older room account that works on E1, plus that older account works on my smart dock too. Just these new accounts don't work. I even logged in using the built in skype local account as well to test. Same issue. We use O365 so we don't need to install any certificates, machine is not on the domain but like I said that won't matter as I have verified older room accounts fetch the calendar just fine. Also user accounts logged into SRS fetch just fine too. I don't understand why these new room accounts made back in August won't fetch the calendar, they look identical to the old room account that works. Same product licenses, I ran thorugh all the powershell commands as well. MS support has ignored me this entire week which is frustrating, they said they elevated the case to a higher engineer but he never claled me and they aren't responding to my emails.

 

Login to the cloud exchange account using skyperoom@********.onmicrosoft.com  <-- what do you mean by that? you mean login to O365 as the account? I did that already.

 

I wonder if I should just try that whole build an image thing just to do it...

Senior Member

@Marco Vindell

 

what i mean is that i dont use my federated domain in the exchange credentials login in the SRS app. I use the onmicrosoft.com domain,

like user@mydomain.onmicrosoft.com and not user@mydomain.com.  I am using .onmicrosoft as the UPN for the exchange side of things, mydomain.com as the UPN for the skype side of things.  I do this to bypass 2FA , the exchange user is not synced from my on premise AD at all.

 

 

Regular Visitor

Hey, we solved it last week and it had to do with autodiscover. Since we don't have anything on premises anymore but a hybrid server with no mailboxes or anything we just deleted the internal A record for autodiscover and that did it. Had to use fiddler on one of the systems to view the errors and they referenced autodiscover.

Microsoft

JFYI... We released a reset script just now that you can use to resolve issues like the "skype-mrx://" notifications seen on Surface Pro 4 based SRS v2 devices after upgrading to Windows 10 Creators Update (Version 1703).  Go here for more information.

Senior Member

@Marco Vindell

 

great to know you got it sorted, for us it was not dns, we had the same issue outside of the network as well as internal, ours was 2fa

Occasional Visitor

 @Sandro Saberon , How did you manage to install. I am on the same page and struggling with the error no images are availble.

Frequent Visitor

@Gismon Thomas, please try to create the ISO using the Media Creation Tool through the Surface Pro 4 machine.  Use that ISO to create the USB to format the Surface (https://technet.microsoft.com/en-us/library/mt790558.aspx).  It is also safe to have a back up of the Surface in case you need to revert back.  Skype Room System will only work with Surface Pro 4 and Logitech smart dock system as the installation will not proceed without it.  

Occasional Visitor

Thanks Sandro Saberon . For me the error was related to the image version. Thanks for your advise.