Forum Discussion
Surface Hub Reverts to Skype Mode
Hi,
Same issue here. We have 30 Surface Hub 2s and randomly, some Surface Hubs revert back to Skype. Sometimes we can fix it by just rebooting the device, sometimes not. Our Surface Hubs are all managed in Intune, On premise AD joined, Teams preferred mode and connected to the network by Wifi WPA2 enterprise. We are running these hubs since few month and we never had this issue before around the 28th september.
I can see this in the event viewer :
Activation of application Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams failed with error: -2147009284 See the Microsoft-Windows-TWinUI/Operational log for additional information.
and in the TWinUI/Operational log :
Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams for the Windows.Launch contract failed with The deployment operation failed because the specified application needs to be registered first..
Activation for Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams failed. Error code: The operation completed successfully.. Activation phase: -2147009265
Best regards,
Cyrille
- halbpOct 09, 2020Brass Contributor
Cyrille_D we had another one do this, and going into Apps Teams was greyed out, and clicking on it said it had to be reset (which did nothing). We just uninstalled it and reinstalled and that fixed it. This happened in the CEO's office, so to say he was unimpressed that the one thing the Hub is supposed to do well (Teams) didn't work is an understatement.
Considering how much these things cost, they should be far more reliable.
- Cyrille_DOct 09, 2020Copper ContributorSure, I have a ticket opened at Microsoft (premier support) since few days regarding this issue and still waiting for a feedback...
- yoabarOct 09, 2020
Microsoft
This behavior can be observed when Teams is trying to connect to Office 365 but unable to do so. You'll usually see this when the device wakes up from sleep if getting back on the network is slower than the Teams app attempt to sign in.
To work around this behavior, you can switch to Teams Mode 2, or update to the Windows 10 Team 2020 Update where this behavior doesn't exist.