Forum Discussion
Skype Room System V2 device will not auto login to Skype for Business
- Make sure the autologin is signing into the "Skype" user account.
The autolaunch behavior is triggered in:
HKU\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Run "SkypeRoomSystemLaunch" where it will have a long command that ultimately protocol launch skype-mrx://
This issue started happening to us after running the Creators Update. We are getting an error of skype-mrx:// invalid value for registry when using the Skype account, but it works just fine under the Administrator account. They are not domain joined machines and so far the only way we've been able to resolve is to revert back to the pre-Creators Update version. I hesitate to run the update again in the event that it breaks again as we need these units operational. Has anyone else seen this issue? Does anyone have any ideas on what the cause may be? Thank you!
Have you found a resolution to this yet? We have many of these, this is the first to give me this skype-mrx:// error.
Hi Joshua,
This is how I solved the Invalid Registry option problem.
First the problem only occured on my Skype Room System after the creators update. This is the registry key in question:
cmd /q /c if exist "%SystemDrive%\Rigel\x64\Scripts\Provisioning\launch.ps1" (powershell -WindowStyle Hidden -ExecutionPolicy Unrestricted %SystemDrive%\Rigel\x64\Scripts\Provisioning\launch.ps1) else (start skype-mrx://)
I believe there is a typo in this line and it should actually say start "skype-mrx:"
To fix this I connected a keyboard and mouse to the Logitech Smart Dock (the usb port on the Surface Pro should be fine as well) right clicked on the Windows button and ran Command Prompt as Administrator. The Administrator password is sfb. From command prompt I typed start "skype-mrx:". The command ran and now even after rebooting the problem is solved. I did not edit the registry key. I am typing this from memory as I did not expect this to fix the problem so I was fairly surprized when it did. I hope this helps!
- Tyler
- That fixed it for me after applying the Creators Update. Thank you!
